Skip to main content

Test Configuration Page

The Test Configuration page is where you can manage and edit an existing test script. This page is split into 4 main areas:

  1. Test’s metadata – where the test’s overall configuration and metadata is found
  2. Test script – the test script itself
  3. Machine profiles – configuration of the probe machines to use in the test
  4. History runs – recent history of past runs of this test script

Test metadata

The test metadata stores the overall configuration and metadata of the test script. This includes the following fields:

Test Name

The name of the test. This appears at test execution as well as in the reports. We suggest making the names memorable – ones that explain what it is the test does.


A longer description of the test. Here you should explain what your test does in a bit more details – it will help you in the future to remember what you’ve done, as well as make it easier for others in your team to use the test.

Concurrent Probes, Session size & Number of sessions

In this subsection we determine the number of probes that are used in this test as well as how these probes are grouped into rooms/sessions.

The Concurrent Probes field enables you to set the number of probes (=browsers) that will take part in this test, while the Session size field indicates how many probes you want in the same room/session. The Number of sessions field is automatically calculated.

Learn more about session management in testRTC.


The Webhook field allows you to invoke a webhook call at the end of the test run. This webhook will be called when a test finishes for both failures and success scenarios. It can be used for testing as well as monitoring.

Learn more about configuring test script webhooks in testRTC.

Run Options

These options offer advanced settings that can be used by the test once executed. Each option is defined as a hashtag. You can use multiple options by separating them using a comma.

Check here to review the list of available run options.

Service URL

When a test is executed, it can be very helpful to be able to track the test progress by opening a browser, as a regular user, that points to the tested session.

The tested service URL definition can be helpful in few aspects:

  1. If a service URL is defined, you can click on the ‘Open’ link to manually open a new browser tab with the URL
  2. If the service URL’s ‘Auto open’ checkbox is checked, a new browser tab, with the service URL, will be opened automatically when the test execution is started
  3. The defined service URL can be used in the test’s script by using the process.env.RTC_SERVICE_URL environment variable

Test script

The test’s web browsing flow is defined as a NightWatch/Selenium test case. Nightwatch.js enables quick, simple but powerful tests writing, using only Javascript (Node.js) and CSS or Xpath selectors. Nightwatch.js uses the powerful Selenium WebDriver API to perform commands and assertions on DOM elements. For further information about NightWatch, please refer to

In the ‘Test Script’ section you can perform the following actions:

  • Upload – upload a script from a file.
  • Edit – edit the test’s script in testRTC’s internal editor
  • Request help – If you need assistance with script writing – we are here to help. Click on the ‘Request help’ button and we will contact you

Machine profiles

The Test Profiles section describes the executed agents’ configurations. By default, a single testing profile will be used for the test. In such a case, all agents in the test will have the same testing profile. If additional profiles will be defined for the test, the agents’ profiles will be divided between the agents (more details in next section).

The Testing Profile is composed of the following characteristics:


The Browser drop down enables to choose the executed agents’ browser type and version.


The Location drop down enables to choose the probes’ geographical location.

We offer a more granular location selection when needed.


Choose media (video and audio) that will be used in a test. You can choose based on the media resolution and bandwidth.

Network Profile

The Network Profile drop down enables to choose the probes’ network profile. The network profile is composed of different criteria, such as the agents’ bandwidth, latency and drop packets percentage.

For detailed available profile configuration, please refer to What are the test profile configurations?

Firewall Profile

The Firewall Profile drop down enables to choose the probes’ opened and closed networking ports and packets filtering rules. The firewall profile can be used to simulate different networking configurations such as different firewall and NAT rules.

For detailed available profile configuration, please refer to What are the test profile configurations?

Multiple Testing Profiles

In order to define multiple Test Profiles for a test, click on the ‘Add Profile’ button. A new Testing Profiles section will be added and can be modified.

The probes’ configuration will be distributed between the Test Profiles in a round-robin fashion – If you have more profile than users, then only the first few profiles will be assigned. If you have more users than profiles, then once the number of users reaches the number of profiles, we start the allocation of profiles all over again.

For example, for a test with 7 concurrent users and 3 Testing Profiles, the probes’ configuration will be:
Test Profile 1 Test Profile 2 Test Profile 3
Probe 1 Probe 2 Probe 3
Probe 4 Probe 5 Probe 6
Probe 7    

Read more about machine profiles allocation to probes.

Save and Run

After the test configuration is updated:

  • Click on ‘Save’ to save the test configuration.
  • Click on ‘Run’ to save the test configuration and run the test.

Fields’ content verification

Field with red border indicates that the field’s value is illegal.

Field with blue border is the current field (in focus).

Additional activities

In addition, the following activities can be performed:

  • Delete: Delete test.
  • Export: Export the test details to a local JSON file. This file can be later imported by clicking on the Import button on the Tests page.
  • Duplicate: Duplicate a test details to a new test.

History runs

At the end of the script editor you will see a list of recent runs of the test script. This allows easy access to the latest runs of this test along with the results.

Was this article helpful?

0 out of 0 found this helpful