In addition to the general results review actions presented in Reviewing Results, the following options are available for reviewing functional test results.
Reviewing Results in the Quality Tasks view
If a test fails, the Quality Tasks view reports a task to alert you that the test failure requires review. These tasks are organized by test suite and test.
|To achieve this...||Do this...|
|See details about a failure.||Double-click the failure message then review the information reported in the Details tab that opens.|
|Open the configuration panel for the tool related to a reported failure.||Right-click that failure then choose Open Editor for Test.|
|Locate the Test Case Explorer node related to a reported failure.||Right-click that failure then choose Show Source in Test Case Explorer.|
|View the related traffic (when applicable).||Right-click an error message, then choose View Associated Traffic.|
|Learn more about the reason for a failure reported from an XML Assertion tool, Browser Validation tool, or Browser Data Bank tool.||Right-click the related message, then choose View Associated Editor.|
Reviewing Results in the Test Case Explorer
The Test Case Explorer indicates the status (pass/fail/not yet executed) of all available test cases.
- A green check mark indicates that the test passed.
- An unmarked test indicated that the test was not yet executed.
The Test Case Explorer can also show detailed information about failed and passed tests.
To view any tasks related to a test listed in the Test Case Explorer, right-click that test’s Test Case Explorer node, then choose Show in Tasks. Any tasks related to that test will then be shown in the Quality Tasks view.
If you would like to view the traffic for each individual test in a test suite, double-click the Traffic Viewer node of the desired test after the test has been completed. The traffic will display in the Traffic Viewer tab on the right side of the GUI.
The tabs allow you to toggle between request and response traffic. The Server response time label shows the time elapsed from the last byte sent to the first byte received. The server response time show ass <1 millisecond for one-way messaging scenarios in which you don't have both a request and a response to compare the send and receive times.
The Response and Request bodies display in Literal form by default.
For more information on the Traffic Viewer tool, see Traffic Viewer.