How to read test run results

Depending on the type of testing you run you get different data in the results.

Functional testing
Test request Full request and response headers
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 If you want, you can expand this section to check 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
Test results summary It’s the summary of the whole test run. On the right, you have the concise summary with:
  • Number of test cases executed. It’s the number of test cases executed out of those associated with the test definition. For the configuration changes to be safe to implement on the production environment, all test cases should be executed.
  • Number of IP versions for which the test was run.
  • Number of outstanding diffs. It’s the number of diffs found during the test run.
Diffs This is the list of all the differences found during the test run. They are divided into three groups: response headers, caching option, and metadata variables. See also: Test results concepts, Review diffs
Last 30 days activity In this tab, you can check the activity for this test.