We need client testing framework that is more thoroughly integrated with the /app code itself. Here's the gist of the plan:
Create a /test/* view which takes the rest of the path and looks up the /app module in that path and runs those tests with the standard Jasmine test runner. /test simply runs all tests in /app (all modules that end with .spec).
Set up brunch to include these spec files in app.js for development builds, but not for production builds.
Add .spec files with Jasmine tests to /app itself, often paired with the class or module it tests (so there would be Camera.spec.coffee right next to Camera.coffee). Some existing tests can be grabbed from /test.
Build common systems for replacing various resource grabbing systems with Jasmine spies, such as Backbone, PreloadJS and Firebase.
Integrate with the Developer Tools Window, if available (so for any instance of a class, click a button to open a test window for its class).
These steps are in increasing importance. Just doing the first one so tests can be written for and viewed with the development server will go a long way toward covering the app with unit tests and better descriptions of how things work.
The text was updated successfully, but these errors were encountered: