Test Settings

The Test Settings feature allows the user to add, edit, and review a variety of settings related to the test case. These include Basic & Advanced Settings, Webhooks, Timeouts, File Uploads, Cookies, Plugins, Headers, and Alerts. 

To Review and Edit Test Settings

There are 2 ways to access Test Settings.

  1. Go to Projects >> Functional Tests tab and locate the test case.
  2. Click on the Actions button >> Settingsmceclip9.png


  1. Click on the Actions button >> Details-->
  2. Then click on Test Settings button and select Edit Test Settings from the drop down menu.

Regardless of which path you choose to access, the following Test Settings screen will display, starting with the Basic tab.

Basic Tab


General settings for a test case are found in the Basic tab. Fields are as follows:

Test Name - Name of the test

Project - Name of the project

Site Environment - Site environment 

Folder - formerly known as Module, a categorization assigned to this test

Schedule - Shows the schedule of the test when running

Browser Run Order - Shows run order as parallel or sequential

Notes -  Any notes for this test

Tags - Tags categorization assigned to this test


Webhooks Tab


The Webhooks tab is used to set the state of an account either before or after a test case executes. NOTE: Currently we only support GET requests for both Pre- and Post-test hooks. Fields are as follows:

Pre-Test Hook "Account Set Up" - Used to fire off an API call before the test runs to set the required state of the test at execution.

  • Enter the API Call URL in the field (required)
  • Enter the Expected Response (optional)

Post-Test Hook "Account Clean Up" - Used after the test case is executed to fire off an API call to reset the test account status back to default.

  • Enter the API Call URL in the field (required)
  • Enter the Expected Response (optional)

Timeouts Tab


The Timeouts tab shows performance level time outs and thresholds for the test case.  If any of these set thresholds are exceeded during test case execution, the test case status will display a Warning.
NOTE: These timeouts will not fail a test case but instead will alert that one of these thresholds has been met/exceeded.

Advanced Tab


The Advanced tab showcases an extensive list of optional test case settings.  Note: This is not an all-inclusive advanced settings list, instead of what is most commonly addressed. 07/27/2020: This section will be updated shortly with an all inclusive list of options and their definitions.

Enable Video (on-demand runs): Will enable video of a test to execute in the cloud. 

Fail Test on Invisible Element: When selected, if trying to perform an action on an invisible element, the test will fail.

Continue On Error: When selected, if a test action fails, it will continue to execute as long as it's able.

Visual Completion: When selected, visual completion is turned on (Visual Completion shows how long it takes a page to visually load).

HTTP Authentication: Set here to use HTTP authentication at the test case level versus the project level.

Region: Select the region the test case is executing in.

Bandwidth Simulation: Set the bandwidth to simulate what the site looks like when users are using different bandwidths, a slower internet connection, or LTE.

Viewport Width/Height: Include these parameters when using responsive sites to set the width and height.

Orientation: Select either Portrait or Landscape.

Enable Screenshots: This selection is always enabled by default.

URL Override: This value replaces the environment's value for this particular test execution.

Note: Ignore Certificate Errors will be set to ON by default for all new and modified test cases that were created via Architect and NLP.

Files Tab

The Files tab will display ONLY if the test case has a step that includes the upload of a file.
NOTE: When using Architect the file must be attached or the test case will fail.

Plugins Tab


Attach a plugin to the test case using the Plugins tab. Choose a file and attach it.

Headers Tab


The Headers tab allows false data parameters, such as IP addresses, to have the application create and deliver a specific experience at execution.

Cookies Tab


Inject cookies into a test case in the Cookies tab. For example, logging in a user without having to go through the login steps.

Enter the Parameters for each cookie by typing in the cookie name and associated value for that cookie.

Alerts Tab


The Alerts tab sends alerts via email if this option is selected. The Alerts Delivery drop-down menu allows a user to select parameters for when alerts are sent. Enter the email address(es) in the field, separating each with a comma.


When finished reviewing and editing your Test Case Settings, click Save Changes.