unittests/README.txt
author hamidouk
Fri, 18 Nov 2011 14:33:24 +0100
branchtweet-widget
changeset 276 8a5a34ff1202
parent 58 f92e6c4baae9
permissions -rw-r--r--
WIP - do not use in production ! refactoring the code to have a finite state machine (http://en.wikipedia.org/wiki/Finite_state_machine)
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
58
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     1
Layout of the unittests directory
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     2
==================================
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     3
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     4
We've got a directory for tests - unittests/tests. Add your tests there. There should be only one file per functionality area tested (i.e - all the
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     5
tests about JSONSerializer should be in jsonserializer.js). Your tests should be wrapped in a function named "test_$filename$" where $filename$ is the
f92e6c4baae9 Renamed LAYOUT.txt and added sinon.js for mockups.
hamidouk
parents:
diff changeset
     6
name of your file. Don't forget to define a module for your tests and to add a reference to your file in index.html