Test logs record

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Test logs record

    The Test Logs record in ServiceNow's Automated Test Framework (ATF) captures detailed console logging and test execution data during test runs. This information is stored in thesysatftestresultitemtable and includes browser console logs, test results, and error messages generated by individual test steps or environments. Access to specific test logs is available from the Test Log related list on the Test Results form.

    Show full answer Show less

    Key Features

    • Status Tracking: Test logs indicate the outcome of each test step with statuses such as Success, Failure, Success with warnings, Ignored, Warning, Waiting, Running, Skipped, Error, and Cancelled. These statuses help you quickly assess test progress and results.
    • Test Log Types: Logs are categorized as Step Results (detailing execution and console output), Client Logs (log entry text), or Client Errors (actual client-side errors). This categorization facilitates targeted troubleshooting.
    • Allowed Client Errors: Client errors can be marked as ignored or warnings through the Allowed Client Errors feature. This prevents recurring, accepted client errors from causing test failures in future runs, helping maintain test stability.
    • Detailed Timing Information: Each log records start time, end time, duration, and the exact time the log entry was recorded, supporting precise analysis of test execution timing.
    • Contextual Data: Logs include step names, descriptions, browser type and version, and references to associated test results and allowed client error records, providing comprehensive context for each test step’s execution.

    Practical Use for ServiceNow Customers

    By leveraging the Test Logs record, you can monitor and diagnose automated test executions effectively. The detailed status indicators and output logs allow you to:

    • Identify and understand test step failures and warnings quickly.
    • Filter out known client-side errors that do not impact test validity using allowed client errors, thereby reducing noise in test results.
    • Access comprehensive execution data for root cause analysis and continuous improvement of test cases.
    • Correlate logs with specific browsers and environments to troubleshoot environment-specific issues.

    Overall, Test Logs enable you to maintain high-quality automated testing processes by providing transparency into each test step’s execution and outcomes.

    The Test Results Item (test log) record contains console logging and test execution information.

    During test execution, any information reported to the environment is recorded in the Test Log (sys_atf_test_result_item) table. This information can include browser console logging, results, and error messages recorded by step environments. You access specific test logs from the Test Log related list in the Test Results form.

    Field Description
    Status The result of the test log:
    Success
    Test step run passed.
    Failure
    Test step run failed.
    Success with warning(s)
    Test step passed but encountered client error(s) that were allowed as warnings in the Allowed Client Error table.
    Ignored
    Client error that has been allowed with a report level of Ignored.
    Warning
    Client error that has been allowed with a report level of Warning.
    Waiting
    Test or suite waiting to start.
    Running
    Test or suite is running.
    Skipped
    Occurs if an earlier test in the suite failed and Abort on failure is set to true.
    Error
    An error occurred in the test framework. For example, the test runner halted or the server encountered an unintended scenario. The error message appears in the Summary field of the Steps Results record for the step that threw the error.
    Cancelled
    User canceled the test or suite.
    Type Type of test log:
    • Step Result
    • Client Log
    • Client Error
    Note:
    If a Client Error, you can optionally add it as an ignored or warning entry in the Allowed Client Errors. Doing so prevents the allowed client errors from affecting ATF test executions when they recur in future test runs. For more details, refer to Allowed client errors.
    Output Output generated for the test log.
    • For a step result, the console logging and test execution outputs from the step, including any explanation why a step failed or was skipped.
    • For a client log, the log entry text.
    • For a client error, the actual client error is displayed.
    Step Name of the step executed. This field may be blank for a client log.
    Test Result Reference to the test result associated with this step result. Click Reference field icon to view detailed test result information.
    Description For a step result, the actions performed in this test step.

    For a client log, blank.

    For a client, this message displays: This client error occurred on the page in Browser Type Browser Version (for example, Chrome 62.0.3202.62).
    Start time Time at which this test step started executing.
    End time Time at which this test step finished executing.
    Duration Time duration it took to execute this test step.
    Recorded at Time at which this step or log entry was recorded.
    Allow listed client error Reference to the Allowed Client Error record (if any). Click Reference field icon to view the Allowed Client Error record for this client error.