During the software development process it's good to know how well tested your requirements are and if recent changes have caused previously complete requirements to stop functioning properly. This is precisely what the "Requirement Test History and Overview Report" can tell us. The graph below shows the number of requirements that have been tested for each build. This report is available in the MSF for CMMI template.
However, getting the report to actually work is not straight forward hence this post. Here is how to get it working:
1. Create some requirement work items
2. Create some software and a build script to build it
3. Run some local tests and associate the local test with the build you tested. For example you might deploy a build to a Test server. Then run a manual test that instructs you to go out to the test server web site and perform some tests. once you've finished the test you will get a test result.
4. Right Click a row in the test results window and select "Add to Work Item..."
5. You will be asked to publish the test result. Click yes as this is required.
6. The next screen asks you to link your test result to a build. Select the build that you tested against and click ok.
7. Now you need to select a requirement from your work items that the test validates. I selected a query called Product Requirements and clicked Find. Then I highlighted a Requirement from the list and clicked ok.
8. You can repeat these steps to associate more test results to requirements. The graph will show that a requirement failed for a build if 1 or more test results failed.
Recent Comments