write module tests for existing core modules about cwtactics

[ctomni231]

Okay, currently we have the following modules:

• gamecontroller
• input
• JSlix
• loop_manager
• performance
• screen
• starter
• state
• statemachine
• test
• tween

We have tests only for two of the modules so far:

• statemachine
• test

How extensive do we want these tests to be:

• Should we have tests on functions that require external files, and where would those test external files be stored?
• Should we just test the essentials, or is this a robust ‘test everything’ suite?
• Is tests important enough to invoke a ‘no test, no pull request’ policy?
• Should we allow tests only to be available on debug builds, and leave them off release builds?

Let me know what you think.

[Tapsi]

Focus on decoupled modules with logic heavy tasks.

For now I think these ones need tests:

• gamecontroller
• input (=> multi key handling)
• screen (=> screen change mechanic)
• statemachine
• tween