forked from craftyjs/Crafty
-
Notifications
You must be signed in to change notification settings - Fork 1
Automatic tests
ahilles107 edited this page Jan 10, 2012
·
2 revisions
Two types of test should be run on all commits - Performance tests and feature tests
This kind of test should consist of one simple task such as create an entity on the stage and make it move back and forth. The performance score for this test will then be the number of times this task can be executed in a single game without dropping the framerate below 60 FPS.
This is akin to the existing unit tests and the purpose is to ensure that commits don't break existing functionality.
Statistics should be saved so we can graph the development.
If a commit causes a performance test to drop significantly or a feature test to fail an email should be sent to the commiter.
We could use one of these frameworks:
- http://code.google.com/p/js-test-driver/
- https://github.com/jquery/testswarm/
- http://pivotal.github.com/jasmine/ - great bdd tests framework