testguidelines.doc 1 of 1
Guidelines for Test Case Writing
Assume your audience for the test case has never worked on HRSA system.
The test case objective should be brief, but clear.
Every time you click, it is a step that should be documented.
Where cursor placement is important, make sure the step instructs the tester to click on the correct area of the window
Make use of bullets or dashes to distinguish specific and separate actions in a step.
When there are nested vertical scrolls, try to be explicit on which scroll bar is being using in the step.
Refer to the GUI legend, toolbar buttons and or GUI glossary documents below when describing objects in HRSA.
Do not use the same term to mean two of more different things
Where possible, use test data that can be reused in the next regression testing.
Where possible, use the undo feature to delete the test case that was just tested