Mobile test settings

Mobile tests provisioned to run on Backbone nodes or the Last Mile network are configured with Backbone test settings and Last Mile test settings, respectively.After you provision a Mobile test that runs on Backbone nodes, you can configure Network throttling to simulate the desired mobile network speed. For details, see Backbone Test Settings.

In the Synthetic Classic Portal, settings for a Mobile test consist of:

Note that:

  • When initially adding a test or when creating a test template, only the basic settings are available.
  • When editing one Mobile test, all settings are available.
  • When editing more than one Mobile test, the Basic Settings and Advanced Settings tabs are merged to create the Common Settings tab. This tab lists the tests you selected for editing and the Mobile settings that you can edit.
  • Mobile tests have a fixed frequency of an hour. You can configure the test to run once or multiple times per hour, but you can't schedule the test to run once every two hours or longer than that.

Basic Settings

Test List

If you selected to edit more than one test, the Test List section at the top of the page lists each test you selected to edit and its status.

To remove a test from editing, click . For more information about editing multiple tests, see Editing Performance tests.

Edit Test Name

If you selected a single test to edit, the Edit Test Name field displays its name.

This setting is not available when creating a test template.

To rename a test, use these valid characters:

  • Letters
  • Numbers
  • Spaces
  • Period ( . )
  • Forward slash ( / )
  • Colon ( : )
  • Underscore ( _ )
  • Equal sign ( = )
  • Comma ( , )

The name cannot include the following reserved terms:

  • delete
  • drop
  • exec
  • insert
  • update

This setting is not available when creating a provisioning template.

Batch Order Name

If the test belongs to a batch order, the name of the batch order appears here.

This field does not appear if the test does not belong to a batch order.

Select Test Status

The test status can be:

  • Active – Currently collecting data based on the test configuration settings and is available for charting, reporting, and trending.
  • Inactive – Currently not collecting data and is available for charting only.
  • Delete – Remove the test from the Portal and the database. The test is not available for charting, reporting or trending. This option is not available when first adding a test.

This setting is not available when creating a provisioning template.


The Mobile locations that appear in the list depend on the type of script originally selected for the test:

  • Mobile scripts display all Mobile nodes.
  • Mobile-SMS scripts, which are scripts that contain SMS action(s), only display nodes that support SMS.
  • Mobile and Mobile-SMS scripts edited together only display nodes that support SMS.

Mobile locations can have the following appended to their name:

  • Baseline indicates the test will run over the Ethernet. Select this option to view the effect of mobile carriers on the test.
  • 4G indicates the test will run on the 4G network.
  • SMS indicates the location supports SMS.

To select a location:

  1. Optionally, use the search field to enter criteria to find the locations. Locations matching the search criteria appear in the list as the criteria is entered or change.
    To view all locations again, clear the search field.
  2. Specify the number of measurements per hour to be used for this location in the measurements per hour field prior to moving it.
    • Choose the location and click or double-click a location to move it.
    • Select multiple adjacent locations by holding the Shift key and using the mouse to select the first and last location.
    • Select multiple discrete locations by holding the Ctrl key and selecting the locations.


These options are only available for tests configured with the Mobile Agent.

Client (non-network) time in results

Client (non-network) time, also called render time, refers to the time spent by the client browser rendering the page, rather than the time spent downloading objects for the page.

When a page is being displayed in the browser, there is processing time by the browser after the objects are downloaded. That non-network time is not displayed in a waterfall chart by default; however, you can enable the reporting of client rendering time in the charts.

  • If the option to include client (non-network) time is disabled, the objects are displayed in the waterfall chart one right after another.
  • If client (non-network) time is enabled, gaps appear while the rendering takes place before the next page download begins.

When you select this option, the waterfall chart displays W3C metrics.

Include SPDY Support

Select whether to enable SPDY support.

SPDY is a networking protocol for transporting web content and is designed to reduce the latency of web pages.

Screen Capture

Use this section to define whether screen captures are available in various Portal pages.

  • Off – The default. Screen captures are not collected.
  • Screen Capture on Error (SCoE) – This option collects screen captures when an availability error occurs in a test execution.
  • Screen Capture on Error & Success – This option collects screen captures both when the test runs successfully and when an availability error occurs.

The information that can be captured includes screenshots, route tracing, and HTTP header information. For details, see Viewing Screen Captures.

Set Test Expiration Date

Select the expiration date for the test.

  • Expires on – Click the calendar icon to select an expiration date from the calendar.
  • Expires in – Enter the number of days the test will run, up to a maximum of 15 days.

The Portal automatically inactivates any test that reaches its expiration date at 0:00:00 GMT on the specified date.

Before the test expires, an email is sent to notify the contact person for the account of the pending test expiration.

If you need to find out who the contact person is for your account, or to change the contact person, open a Support ticket. You will need to provide your account name and account ID, which are displayed on the Account settings page.

This setting is not available when creating a provisioning template.

Save Test To

Use this setting to assign a test to a folder.

Use folders to organize tests if you have multiple tests running in your account. For example, if you have multiple tests for a website's workflow, you can group all these tests into a folder, and use the folder to create a Status overview tile in a custom dashboard to monitor the tests as a unit.

The folder options are:

  • Keep the default of <No Folder>.
  • Click <No Folder> and select an existing folder from the list.
  • Create a new folder: Select New folder and enter the folder name in the field.

Valid characters for a folder name are:

  • Letters
  • Numbers
  • Spaces
  • Period ( . )
  • Forward slash ( / )
  • Colon ( : )
  • Underscore ( _ )
  • Equal sign ( = )
  • Comma ( , ).

The name cannot include the following reserved terms:

  • delete
  • drop
  • exec
  • insert
  • update

You can use the Folder management page to create folders and manage their contents.

Advanced Settings

The Advanced Settings are available after you provision a test, when you open the test for editing. These settings are not available when you're creating a provisioning template.


Transaction Steps

Use transaction steps to rename steps so that they are more descriptive. For example, rename a step "Home Page" instead of the URL for the page.

Parameters: Defaults

Use parameters to change script values without having to edit the script. This is a useful setting for values that change periodically, such as a password.

If parameters are defined in the transaction (recorded in the Web Recorder or the Windows Recorder), this section lists the default values. If needed, enter a new value for each parameter.

If no parameters are defined for the test, the message "There is no default parameter value" appears.

Additional HTTP Headers

Use this section to specify additional header information such as cookies, cache control, GZIP encoding control, or connection keep alive rules.