9 Validation testing
In this course, you need to validate that your team’s requirements are met. While your team may not be perfect and bugs may slip through the cracks, validation testing is one way to show that you put honest effort into satisfying the goals of your project. You want to show your instructor that you thought about and tested each requirement.
For each requirement, you should create one or more test cases to demonstrate that you satisfied the requirements. As an exercise, select a requirement and create validation test cases to demonstrate that the requirement was satisfied.
Common pitfall: Test steps should be repeatable. For instance, if you have a test case that says to add items to a shopping cart and click to check out, the expected results may vary based on the items that were added. It may be difficult to repeat the test case. You may redesign the test case to tell the tester to add specific items such as “Item 3033 Purple Shirt” (priced at $29.99) and “Item 3087 Green Shirt” (priced at $29.99) to the shopping cart and then click to checkout. This test case is repeatable. If the test case fails, your test steps with extra details make it easier to repeat and debug the problem.
Test No: |
Traces to Req. No: |
Test Steps: |
Expected Results: |
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
Use the following template to practice writing validation test cases with your team. You’ll leave the last column blank for now since you are only creating test cases, but not running them. When you create a full version of validation tests for your team, you’ll similarly write the test cases and leave the last two columns empty. Once your project is complete, you will then run the test cases and document the results in the last two columns. Add more rows as needed.
Test No: |
Traces to Req. No: |
Test Steps: |
Expected Results: |
Pass or Fail: |
Comments: |
1 |
|
|
|
|
|
2 |
|
|
|
|
|
3 |
|
|
|
|
|
4 |
|
|
|
|
|
5 |
|
|
|
|
|
6 |
|
|
|
|
|
7 |
|
|
|
|
|
8 |
|
|
|
|
|
9 |
|
|
|
|
|
10 |
|
|
|
|
|