Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform App Engine
Table of Contents
Choose your release version
    Home New York Now Platform App Engine Now Platform App Engine Application tools Automated Test Framework Building and running automated test suites

    Building and running automated test suites

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Building and running automated test suites

    Run a group of tests in a specific order to test an application or a group of related features.

    A test suite can contain both individual tests and other test suites. A test suite that contains another test suite is called a parent, and the test suite contained within the parent is called a child. While a test suite can have both individual tests and test suites as children, tests cannot have other tests as children. Tests can only contain test steps.

    Benefits

    Grouping tests into test suites offers these benefits.
    • Allows testers to run every test in a test suite with one action.
    • Allows testers to run all child test suites in a parent test suite.
    • Allows testers to see test results for every test in a test suite.
    • Allows test designers and testers to schedule when to run test suites.
    • Allows test designers and testers to schedule starting client test runners to support test runs.

    Hierarchies

    Automated Test Framework supports building a multi-level hierarchies where a test suite can be both a parent and child. For example, this figure illustrates Test Suite 1 as the parent at the top of the hierarchy. Test Suite 1.3 is a child of Test Suite 1 and also a parent of Test Suite 1.3.1 and Test Suite 1.3.2.

    Figure 1. Example of Test Suite Hierarchy
    Diagram of example test suite hierarchy

    Schedules

    To schedule a test suite, you need three components:
    • a test suite record
    • a schedule record specifying when you want the system to run the test suite
    • a scheduled suite run record that associates the test suite to run with the schedule for running it
    With this model, you can associate a schedule with many different test suites, and vice versa.
    Note: You can schedule only test suites, not individual tests. Scheduled tests will run only if there is an open Scheduled Client Test Runner page matching the scheduled suite's browser conditions. Scheduled tests cannot run on a machine that is locked, powered down, or does not already have the browser open.

    The watchlist on the test suite run record also allows you to specify users to receive an email when the system finishes executing the test suite run.

    If the test suite contains one or more form steps (steps involving a user interface), you must ensure that a scheduled client test runner is actively running in a browser when the schedule triggers the suite run.

    Note: See Browser recommendations and requirements for recommendations and requirements for running the client test runner.

    For step-by-step instructions on how to schedule a test suite, see Schedule an automated test suite.

    Filters

    Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites.

    • Create an automated test suite

      Group automated tests into a suite you can execute as a batch.

    • Add tests to a suite with a filter

      Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites.

    • Add test to an existing automated test suite

      Add a test to a test suite that already exists.

    • Add child test suite to parent test suite

      Add to a multi-level test suite by including a child test suite within a parent test suite.

    • Run an automated test suite

      After creating an automated test suite, run it in a non-production instance.

    • Schedule an automated test suite

      Schedule one or more test suites to run at a specific date and time.

    • Run a scheduled test suite using a script

      Execute a scheduled UI test suite immediately using a script without having to wait for the scheduled time. You can use this method while trying to automate the process of running a test.

    • Re-run failed tests in an automated test suite

      Re-run failed tests within a test suite without rerunning the entire suite.

    Related concepts
    • Suites
    Related reference
    • Step results record

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Building and running automated test suites

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Building and running automated test suites

      Run a group of tests in a specific order to test an application or a group of related features.

      A test suite can contain both individual tests and other test suites. A test suite that contains another test suite is called a parent, and the test suite contained within the parent is called a child. While a test suite can have both individual tests and test suites as children, tests cannot have other tests as children. Tests can only contain test steps.

      Benefits

      Grouping tests into test suites offers these benefits.
      • Allows testers to run every test in a test suite with one action.
      • Allows testers to run all child test suites in a parent test suite.
      • Allows testers to see test results for every test in a test suite.
      • Allows test designers and testers to schedule when to run test suites.
      • Allows test designers and testers to schedule starting client test runners to support test runs.

      Hierarchies

      Automated Test Framework supports building a multi-level hierarchies where a test suite can be both a parent and child. For example, this figure illustrates Test Suite 1 as the parent at the top of the hierarchy. Test Suite 1.3 is a child of Test Suite 1 and also a parent of Test Suite 1.3.1 and Test Suite 1.3.2.

      Figure 1. Example of Test Suite Hierarchy
      Diagram of example test suite hierarchy

      Schedules

      To schedule a test suite, you need three components:
      • a test suite record
      • a schedule record specifying when you want the system to run the test suite
      • a scheduled suite run record that associates the test suite to run with the schedule for running it
      With this model, you can associate a schedule with many different test suites, and vice versa.
      Note: You can schedule only test suites, not individual tests. Scheduled tests will run only if there is an open Scheduled Client Test Runner page matching the scheduled suite's browser conditions. Scheduled tests cannot run on a machine that is locked, powered down, or does not already have the browser open.

      The watchlist on the test suite run record also allows you to specify users to receive an email when the system finishes executing the test suite run.

      If the test suite contains one or more form steps (steps involving a user interface), you must ensure that a scheduled client test runner is actively running in a browser when the schedule triggers the suite run.

      Note: See Browser recommendations and requirements for recommendations and requirements for running the client test runner.

      For step-by-step instructions on how to schedule a test suite, see Schedule an automated test suite.

      Filters

      Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites.

      • Create an automated test suite

        Group automated tests into a suite you can execute as a batch.

      • Add tests to a suite with a filter

        Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites.

      • Add test to an existing automated test suite

        Add a test to a test suite that already exists.

      • Add child test suite to parent test suite

        Add to a multi-level test suite by including a child test suite within a parent test suite.

      • Run an automated test suite

        After creating an automated test suite, run it in a non-production instance.

      • Schedule an automated test suite

        Schedule one or more test suites to run at a specific date and time.

      • Run a scheduled test suite using a script

        Execute a scheduled UI test suite immediately using a script without having to wait for the scheduled time. You can use this method while trying to automate the process of running a test.

      • Re-run failed tests in an automated test suite

        Re-run failed tests within a test suite without rerunning the entire suite.

      Related concepts
      • Suites
      Related reference
      • Step results record

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login