Test run results
View test runs results
You can access test results in several ways.
- From the Runs and results page. On the Test Center homepage, in the left menu, click , and expand the test run that you want to see. There, you can also download the PDF with the results, by clicking the download icon , next to the Run again button.
- From either Recent activity list.
- On the Test Center homepage, in the Recent activity list, click Test progress/results next to the test run you started.
- Find the test object for which you run the test and expand it in the list. In its Recent activity tab, click Test progress/results next to the test run you started.
- From the notification email you receive when a test run completes successfully. To view test results, click Go to results.
Functional testing results
In the structure tree, you can see all tested test cases and how many of them passed, failed, or were inconclusive because Test Center failed to explicitly verify whether the test case passed or failed. Click the category of test cases, Passed, Failed, or Inconclusive to filter the results. Click to view details of the test case of interest.
Field | Description |
---|---|
Test request | Test request of the test run. |
Client profile | Client profile of the test run. |
Expected | This is the condition for which you run the test. |
Actual | This is the actual value Test Center got from running the test for the set test request. |
Result | There are two possible test run results: - Fail. Itâs when the Expected and Actual values differ. In such case, the tested changes need to be thoroughly checked as they donât behave as they should and may cause problems when activated on the production environment. - Pass. Itâs when the Expected and Actual values are the same. It means that the tested changes behave in expected manner and are safe to implement on the production environment. |
Full request and response headers | The exact request and responseâs headers. All customized requestâs headers are noted at the end with annotations: added, filtered, or modified. |
Comparative testing results
In the structure tree, you can see all test definitions for a hostname with the number of diffs found while running the test. To check details about a diff, click next to it.
Field | Description |
---|---|
Response headers diff details | It's the comparison of headers between two tested hostnames. |
Instances | It's the list of test cases where the diffs were detected. You can accept them or add notes to them. |
Add a note to a diff
You can add a note to diffs for you and another users to see. This can help explain why you did or did not accept the diffs.
Before you begin
Open the results of your comparative testing.
To add a note to a diff:
- Click next to a diff's instance of interest.
- To add a note:
- To a single instance, hover over it and click .
- To multiple instances at the level of a test case, in the test case name row, click ... > Add note to all.
- To all instances within run test cases, above the instances table, click ... > Add note to all.
- Enter a note.
- Click Add.
Review diffs
Review diffs by accepting or unaccepting them.
Before you begin
Open the results of your comparative testing.
To review diffs:
-
Click next to a diff's instance of interest.
-
To review:
- A single instance, switch Accept next to it.
- Multiple instances, at the level of a test case, in the test case name row, click ... > Accept all or Unaccept all depending on whether the instances were already accepted.
- For all instances within run test cases, above the instances table, click ... > Accept all or Unaccept all depending on whether the instances were already accepted.
- A single instance, switch Accept next to it.
-
Click Save.
What to do next
If all of the diffs represent desired or expected behavior, you can return to Property Manager to activate your configuration changes, confident that they won't cause problems. If some diffs still show undesired or unexpected behavior, you can return to Property Manager to adjust your configuration changes and retest them with Test Center before activating them.
Updated about 1 year ago