Test Settings

Test Settings Overview

The Test Settings in Functionize is a feature that allows users to add, edit, and review various settings related to a test case. These settings include General & Advanced Settings, Webhooks, Timeouts, Cookies, Headers, Auth, and Alerts. Users can customize these settings to configure the behavior and execution of their test cases.

 

To Review and Edit Test Settings

There are 2 ways to access Test Settings:

  1. Open a Project to the Test Listing page and locate the test case to update Test Settings
  2. Under the Actions column, click the Test Actions button (...) >>Settings menu option


OR

  1. Click on the Test Actions button (...) >> Details or click on the test case Name


  2. You will be taken to the Test Details page, then click the Test Actions button (...) >>> Test Settings


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

 

  General Tab



General settings for a test case are found in the General Tab. The fields are as follows:

  • Test Name: Name of the test
  • Project: Name of the project
  • Site Environment: The project environment in which the test is created
  • Folder: A categorization assigned to this test used to help filter tests on the Test Listing page
  • 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: A categorization assigned to this test used to help filter tests on the Test Listing page
  • Not Approved for Learning: Approve the the test for AI learning and self-healing

 

Webhooks Tab



The Webhooks tab is used to set the state of a test case, either before or after a test case executes.
Note: Currently we only support GET requests for both Pre- and Post-test hooks.

The fields are as follows:

  • Pre-Test Hook: Test Set Up - used to fire off an API call before the test runs to set the required state of the application under test prior to execution
    • Enter the API Call URL in the field (required)
  • Post-Test Hook: Test Clean Up - used after the test case is executed to fire off an API call to reset the application under test status back to an original state
    • Enter the API Call URL in the field (required)
  • Extensions Post-Hook: Test Clean Up - executes after the test runs, and allows for custom integrations with Test Management solutions - for information, click here

 

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.

  • Page Load Timeout: the maximum amount of time the ML timing model will wait for a whole page to load before attempting selection
  • Missing Element Timeout: the maximum amount of time the ML timing model will wait for an individual element to load before attempting selection
  • DOM Loaded Threshold: the point at which the DOM loads on the screen and provides a warning message if the threshold is exceeded
  • First Paint Threshold: the point at which the first pixel renders on the screen and provides a warning message if the threshold is exceeded

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, under Test Settings, is a section that showcases an extensive list of optional test case settings. It includes options such as enabling video execution in the cloud, setting Proxy at the test case level, selecting the region for test case execution, Self-Heal validation, setting viewport width and height for responsive sites, and more.

Note: This is not an all-inclusive list of advanced settings, instead it is a list of what is most commonly used.

  • Enable Video (on-demand runs): Will enable video recording of a test executed in the Functionize Cloud, if enabled the following video icon will appear next to the Play button


  • Ignore Certificate Errors: When select, any Browser raised certificate errors will be ignored
    Note: The setting will be set to ON by default for all new and modified test cases that are created via Architect
  • Continue on Verification Failure: When selected, if a test fails on a Verify Action, it will continue to execute as long as it's able
    Note: This setting will significantly slow the execution of your tests and only the first 3 failures will be displayed on the orchestration report page
  • Maximum Verification Failures: Testers can now set the maximum number of verification failures allowed on a test, this allows for more flexibility in handling verification failures during test execution
  • Continue On Error: When selected, if a test Action (other than a Verify Action) fails, it will continue to execute as long as it's able
    Note: This setting will significantly slow the execution of your tests and only the first 3 failures will be displayed on the orchestration report page
  • Capture Network logs: When enabled, the test will capture the network logs
    Note: Functionize recommends not leaving this enabled, only enable when needing to troubleshoot an issue, as this setting can collect large amounts of data depending on the site
  • Capture Console logs: When enabled it will capture the console logs
    Note: Functionize recommends not leaving this enabled, only enable when needing to troubleshoot an issue, as this setting can collect large amounts of data depending on the site
  • Display PDF in Browser: When selected, if the test interacts with a PDF file, the PDF file will be opened in the browser window
  • Disable Self heal validation: Self-heal validation is a feature that uses Artificial Intelligence to automatically identify and resolve test failures - this self-healing capability helps eliminate the need for manual diagnosis and resolution of test failures
  • Disable Web Security:Turns off certain security mechanisms implemented by the browser
    Note: It allows users to bypass the same-origin policy and access resources from any domain.
  • Disable iOS CORS: Disabling Cross-Origin Resource Sharing (CORS) restrictions on iOS devices
  • Memory Saver Mode On: When enabled,the browser/application reduces its memory footprint and helps improve system performance and responsiveness.
  • Block the 3rd Party Cookies:  When enabled all the third-party cookies will get blocked in all browsing modes, ensuring a consistent browsing experience.
  • Region: Select the Google Datacenter region in which the test case is executing
  • Window Width/Height: Include these parameters when using responsive sites to set the window width and height
    Note: Any Pageinit or Urlchange Actions after the first step of the test will reset the window width and height back to originally recorded values.
  • Orientation: Select either Portrait or Landscape page orientation
  • Enable Screenshots: This selection is always enabled by default, but can be turned off if Tester does not want screenshots captured due to highly sensitive data or any other reason
  • Environment Management: This value replaces the environment's URL value for this particular test execution, using syntax:
    https://www.existing-site.com::https://www.replace-with-site.com
  • Proxy Settings: Proxy Settings in the test settings refer to the configuration options that allow users to set up and use a proxy server for accessing the application under test behind a Customer's firewall - the proxy settings enable users to specify the proxy server details, such as the IP address and port, which will be used to route internet traffic for the test execution
  • Enable Timing Model: When selected, this determines how long the Al Timing Model waits for an element to appear, Aggressive = faster and Conservative = slower
  • Override Default Self-Heal: When selected, It will override the default self heal
  • Self Heal: A feature that uses machine learning to detect changes in an application or website and automatically update tests to reflect those changes, this helps to avoid false positives and ensure that tests are up to date

 

Headers Tab



The Headers tab allows simulated 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 Tester 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 Tester to select parameters for when alerts are sent. Enter the email address(es) in the field, separating each with a comma.

 

Auth Tab



If the site under test uses HTTP authentication, the Tester can enter the following details under the Auth tab:

  • Initial Pageinit HTTP Authentication: Enter username:password
  • MTLS client key: Enter client key
  • MTLS client certificate (pem format): Enter client certificate
    Note: Please see additional details on mTLS certificates here
  • Additional HTTP Authentication: Enter the URL without protocol
    • Domain
    • Username
    • Password

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