0035 - sc Quality: JUnit Tests
Large parts of functionality in the MIXED code base are not covered by JUnit tests. As such, we cannot ensure the correct functioning of these modules as development continues.
We need to ensure that every part of the system that is part of the essential functionality of MIXED is covered by both a positive and a negative (set of) test(s).
For the purpose of this acceptance test, 'essential functionality' includes:
- every line of code that is executed during:
- the validation of a file format,
- the conversion of a file format to SDFP,
- the conversion of an SDFP file to another format,
- the activation, deactivation, installation or removal of a converter plug-in.
This also includes those parts of the user interface or API that invoke these pieces of functionality.
Non-essential functionality need not be covered by JUnit tests at this time. Trivial methods, such as simple getters and setters can also be excluded.
The deliverables of this story should be:
- test-coverage of all non-essential code,
- a test-suite that can execute every single test-case,
- integration of the test-suite into the build process, so that a new build will always trigger the execution of the JUnit tests,
- a short statement on the total test-coverage percentage before and after the implementation of this story.
The presence of JUnit tests will be randomly sampled by the customer during the acceptance-test
meeting preceding the planning game.
The test-suite developed as part of the stress-test story must not be part of this JUnit test-suite.
The story will be accepted by the customer when all deliverables have been met.
Submitted by erwin on Wed, 2008-02-20 09:26.