Test results record
Summarize
Summary of Test results record
A Test Results record in ServiceNow captures detailed information about the execution of a single automated test. It provides insights into the test’s status, timing, errors, and outputs, helping you understand test outcomes and troubleshoot failures effectively.
Show less
Key Features
- Status Tracking: Indicates the test execution result, such as Success, Failure, Success with warnings, Running, Skipped, Error, or Cancelled, allowing you to quickly assess test health.
- Timing Details: Records the start time, end time, and duration of the test execution for performance monitoring.
- Previous Test Result: Displays prior test execution results for re-runs, helping trace test history (visible to admin roles).
- Error Sections:
- Client Error Details: Shown when failures are due to client-side errors, providing references to failing steps, detailed error messages, and screenshots. Enables identification and resolution of UI or client-related issues.
- Failure Details: Shown for non-client error failures, including failing steps, error summaries, and screenshots to aid diagnosis.
- Additional Information: Includes output logs, browser user agent strings from the test, and detailed error messages for failed tests.
- Retention Option: Allows you to retain test records indefinitely beyond standard data retention policies for compliance or audit purposes.
- Attachments: Screenshots generated during test failures are attached for visual context.
Related Data and Navigation
- Step Results: Access detailed results for each test step and logs.
- Test Logs: View logs related to the test for troubleshooting.
- Test Transactions: Review system transaction logs linked to the test execution, helping correlate test steps with backend transactions.
- Warnings: Lists client errors treated as warnings, aiding in recognizing non-critical issues.
Practical Use for ServiceNow Customers
This record empowers you to precisely analyze automated test executions, identify the root causes of failures—whether client-side or server-side—and monitor test performance over time. By leveraging detailed error messages, screenshots, and related logs, you can streamline troubleshooting and improve your automated testing reliability. Additionally, the ability to retain test results indefinitely supports compliance and auditing requirements.
A Test Results record contains detailed results information about one test execution. Client Error Details and Failure Details sections appear when a test fails due to error conditions, and include detailed error information you can use for troubleshooting purposes.
| Field | Description |
|---|---|
| Test | Name of the test. |
| Status | Result of the Test execution:
|
| Retain indefinitely | Check box to keep this record even after the specified data retention period has passed. For more information, see Table Cleanup. |
| Start time | Date and time of day at which this test started executing. |
| End time | Date and time of day at which this test finished executing. |
| Duration | Elapsed time it took to execute this test. |
| Previous test result | Results of the previous test execution, indicating if the test passed or
failed. Only appears if this test result is for a re-run of a failed test and you
are logged on with the admin, atf_test_admin, or atf_test_designer role. Click the
information icon ( |
Client Error Details
This section only displays when a test fails due to a client error.
| Field | Description |
|---|---|
| Failing step | Reference to the first test step result that failed during this test. Click the
information icon ( |
| Summary | The following text indicates that a client error occurred at this step, and
includes the detailed error message: This step failed because the client error 'DETAILED ERROR MESSAGE' was detected on the page being tested. See failing Test Logs. To ignore these errors in the next test run, use ‘Add all client errors to warning/ignored list’ links. Test designers and developers should always investigate client errors to determine if there are issues with your business process. For more details, see Identify and resolve client errors. |
| First failing client error | Reference to the first client error that failed during the test. Click the
information icon ( Note: For details on how to allow client errors as ignored or warning
entries, refer to Allowed client errors |
| Failing step screenshot | Screenshot of the step that failed. Click |
Failure Details
This section only displays when a test fails due to a cause other than a client error.
| Field | Description |
|---|---|
| Failing step | Reference to the first step result that failed during this test. Click |
| Summary | Output of the step that failed. |
| Failing screenshot | Screenshot of the step that failed. |
Additional information
This section is visible for all test results.
| Field | Description |
|---|---|
| Output | Output generated for the test step.
|
| Browsers involved | User agent strings returned by browsers that ran the test. |
| Related list | Description |
|---|---|
| Step Results | Record for each step result and log entry for this test. |
| Test Log | Record for each test log related to this test results record. |
| Test Transactions | Record for each transaction (from the system transaction log [syslog_transaction] related to this record). To view the step results associated with a transaction, click the appropriate link in the Step Results column. To view the transaction logs associated with a transaction, click the appropriate link in the Transaction column. Note: The system may not be able to log some transactions
with short durations. |
| Warnings | List of test logs containing client errors with a warning status. The Warnings related list only appears on test results with warnings. |