Test Plan Template
The XYZ Test verifies (insert short description of what is being tested)
See (insert links to User Manual, Specification docs, Jira tickets, etc.) for more information on this functionality.
XYZ Test Plans
NOTE: Test plans should be reviewed with each release and modified as needed to accommodate changes in functionality that may impact the plan.
Pre-Test A: Description
If data needs to be staged or other dependencies in place, this should be described in the pre-test section. This section should be formatted with Action Steps and Verification items as follows (same as Test format)
Action: Description of Action
Do this first
Do this second
Verify expected behavior:
List any records to check in a bulleted list here.
Test 1: Description
This test consists of (insert short description of what the test involves in plain English. Even if this seems redundant, this provides the test with simple context before they start the tasks).
Action: Description of Action
(If context is needed to describe were the user should resume testing, this can be noted here in parentheses)
Do this first
Do this second
Bold face any button text as follows: Click on the Save button. Underline text to be entered as follows: Populate the Object Name Uncontrolled field with A Pretty Hat. Place in quotes values selected from term lists or drop-down menus as follows: Select “all records”.
Verify expected behavior:
List anything that should be verified in a bulleted list.
If behavior does not exhibit as expected, the tester should create a Jira ticket.
It is possible to insert a verify box in the middle of a test when needed and resume numbering from the action after the box with a second verify box at the end of the plan.
Test 2: Description
Tests should be in H3 font, and should be separated by dividers.
Action: Description of Action
(If context is needed to describe were the user should resume testing, this can be noted here in parentheses)
Do this first
Do this second