Guideline: Verification and Reporting Points in IBM Rational Quality Manager |
This tool mentor describes how to optimize usage of verification and reporting points in RQM.
Relationships
Related Elements | Analyze Test Failure Develop Test Run Tests
Main Description
A manual test script contains steps, verification points and reporting points. The step is used to define an action to be executed. The verification and reporting points are special steps where a comparison must be executed between what’s observed in the object under test and what is expected. In the case of manual testing the object under test can be an application or a physical device ("Is the light switched on?"). There is no real difference on how RQM deals with a verification point and a reporting point. Adding more verification points to a script will give detailed reporting but will also be more time consuming (read expensive) to execute. Use verification points and reporting points wisely. Make note that for every step or verification or reporting point an associated defect could be created. Special attention must be given to the last verification or reporting point. This sets the Actual Result in the Execution Results of the test in RQM. The final state can be changed in the Execution Results before saving to a more comprehensive state. The available states can be set in the administrative System Properties. The Actual Result of the last execution is visible in the status of the test case. Reporting and queries make use of this status in the Test Case Execution Result (TER). By adding a final (reporting) verification point to each script, one can capture the overall assessment, complemented with a comment from the tester, of the execution in the script log. The pass/fail result might be 'translated' into a more comprehensive execution result for the test case. Note: The list for the Actual Result field can be customized by users with Admin privileges.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.