up previous next contents index
Next: Integrating JUnit into JBuilder Up: Working Backwards with JUnit Previous: An example   Contents   Index

Other notes

  1. JUnit test methods stop at the first failure in an assertion; other test methods will be run, but no further assert tests will be run in the current method.

  2. Naming conventions - Our current testing philosophy is to create test classes with the same name as the class that you want to test, with an "_" preceding the class name.

  3. Also, the test classes are put in the same directory/package as the class that is being tested.

  4. Design Philosophy: Design to Test. Design code for the problem at hand, but also include in the design the ability to test your code.

  5. Set up templates for your testing - it makes it much easier.


up previous next contents index
Next: Integrating JUnit into JBuilder Up: Working Backwards with JUnit Previous: An example   Contents   Index