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 helps customers track whether a test passed, failed, or encountered warnings or errors, providing essential data for troubleshooting and quality assurance.
Show less
Key Features
- Status Tracking: The record tracks test execution status with values such as Success, Failure, Success with warnings, Waiting, Running, Skipped, Error, and Cancelled.
- Timing Details: Includes start time, end time, and duration of the test execution for performance insights.
- Previous Test Result: Displays outcomes of prior test runs when rerunning failed tests, accessible to roles like admin and test designers.
- Client Error Details: Visible only when a test fails due to client-side errors, showing the failing step, error summaries, first failing client error, and screenshots for troubleshooting.
- Failure Details: Displays when failures are not caused by client errors, including the failing step reference, summary output, and screenshots.
- Additional Information: Provides output generated by test steps, error messages, and browser user agents involved in the test.
- Related Lists: Includes detailed step results, test logs, transaction records, and warnings related to client errors marked as warnings.
- Retention Control: Option to retain the test result record indefinitely, overriding normal data cleanup policies.
Practical Use for ServiceNow Customers
ServiceNow customers can use Test Results records to:
- Quickly identify the success or failure of individual tests along with detailed failure causes.
- Access granular error information, including client errors and server-side issues, to accelerate troubleshooting.
- Review test execution timelines and previous run outcomes to monitor stability and test reliability over time.
- Manage and interpret warnings related to allowed client errors to focus on critical issues.
- Utilize screenshots and logs attached to failing steps to gain visual context and detailed diagnostic data.
- Control data retention for critical test results important for compliance or audit purposes.
This comprehensive information empowers test designers, developers, and administrators to maintain and improve automated test quality efficiently within the ServiceNow Automated Test Framework (ATF).
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 ( ) to navigate to the original test result. |
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 () to view detailed step results and error information in the Step Results
form. |
| 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 ( ) to view detailed test results and error information in the Test Logs
form. 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 to download the screenshot. |
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 to download the screenshot. |
| 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. |