Running server test assets on an agent

When you have server test assets that you want to run on a Linux, Mac, or Windows system by using an agent, you can register the agents and run the tests.

You must have completed the following tasks:
When you initiate a test run that requires a capability such as the Safari browser, and if you have not specified any agent to run, the test enters a Waiting for agent state. This state indicates that the job is valid but is waiting for a suitable agent to run it. If an agent that has the required capability is registered with the project, then the agent picks up the job and runs the test, which is in an Waiting for agent state. You can also cancel or stop the test runs that are in the Waiting for agent state.
Note: The default time limit for the agent to be in the Waiting for agent state is 15 minutes after which the test run attempt stops. If you started the test run from the command line, then the time limit is 60 mins.
  1. Log in to Test.
    The Projects page of the initial team space is displayed.
  2. Open the project that contains the test assets, and then click Execution.
  3. Select the branch of the repository that contains the test assets.
    The test assets that are contained in the selected branch of the repository are displayed in the following tabs on the Execution page:
    Tab Description
    SUITES Lists all suites, Compound Tests, JMeter tests, JUnit tests, Postman tests, Rate Schedules, Selenium tests, or VU Schedules that are in the selected branch of the repository.
    TESTS Lists all API tests, functional tests, performance tests, or server test assets that are in the selected branch of the repository.
    ADVANCED Lists all assets that are displayed when custom filters are applied for assets in the selected branch of the repository.
  4. Select the tab based on the type of test assets that you want to run, as indicated in the following table:
    If... Then...

    You want to run Suites.

    Click the SUITES tab.

    You want to run a Web UI test.

    Click the TESTS tab.
    You want to find Suites and tests by using custom filters, and then run Suites and tests.

    Click the ADVANCED tab.

    The test assets in the selected tab are displayed.

  5. Identify the test asset that you want to run by scrolling through the list, searching for the test, or applying a filter.
  6. Click the Execute icon Image of the icon. in the row of the identified test asset.
    The Execute test asset dialog is displayed.
  7. Select the version of the test resources that you want to run in the Version field.
  8. Follow the instructions to select a browser:
    1. Click the ENVIRONMENT tab, if it is not already open.
    2. Select an environment from the list that is available for the test run from the Environment drop-down list.
      The variables and profile overrides in the selected environment override the values defined in the test when you run a test or suite.
    3. Select a browser or device profile for the test run from the Browser drop-down list.
      The browser that is used to record the test is selected as the default browser and the browser specified here overrides the default browser and the browser defined in the profile override.
  9. Optional: Click the DATA SOURCES and select a dataset tab if you are running a test asset that contains datasets.
  10. Optional: Click the VARIABLES tab, and then add or upload variables if the test requires a variable that must be passed to the test at the test run time.
  11. Click the LOCATION tab, and then select the agent that you have added in the Override field.
    After selecting the agent, if the specified browser is not available to the agent, Test displays a warning indicator in the Environment tab.
  12. Click Execute.
    The test run is initiated.
You have run server test assets on an agent.
You can perform any of the following tasks:
  • Stop the test run at any point after the test run is initiated from the Execution page. See Stopping test runs.
  • View the results, reports, and logs of the test from the Results page after the test completes the run. See Test results.