Suggestions and options for representing this work product:
Suggestion: Automated code unit The most appropriate technique
for running these tests is to use code that tests the implementation element
scenarios and that you can run regularly as you update the system during development. When
code is the sole form of the tests, ensure that the code is self-documenting.
The code should document the specifications of the conditions you are testing
and the setup or clean-up that is required for the test to run properly.
Option: Manual instructions In some cases, you can use manual
instructions. For example, when testing a user interface, a developer might
follow a script, explaining the implementation element. In this case, it is
still valuable to create a test harness that goes straight to the user interface.
That way, the developer can follow the script without having to follow a complicated
set of instructions to find a particular screen or page. Option:
Embedded code You can use certain technologies (such as Java™
5 Test Annotation) to embed tests in the implementation. In these cases, there
will be a logical work product, but it will be assimilated into
the code that you are testing. When you use this option, ensure that the code
is self-documenting. |