Versions Compared

Old Version 11

changes.mady.by.user Milosz Tylenda

Saved on

compared with

New Version 12

changes.mady.by.user Michael Dick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adding some thoughts on testcase conventions..

...

Note: You may also use Eclipse to create a patch (Team -> Create Patch...), but this may require committers to modify the patch to match their project layout (workspace per branch or all branches in one workspace) and some committers may not be using Eclipse/Subclipse.

TestCases

When we make a change it's generally a good idea to include a jUnit testcase which demonstrates the desired behavior. Changes that only affect a specific database or only operate in a certain environment (ie DB2 on Z/OS, or only when used with SunOne) are exceptions to the rule.

The testcase should be self validating via jUnit asserts. Writing messages to system.err or system.out is discouraged - they lead to the impression that some manual interpretation of the results must be done. Messages like these are useful when developing the tests or when diagnosing problems but should not be committed.