Project Settings

Project Setting Overview

The Project Settings in Functionize is a feature that allows users to add, edit, and review various settings related to a specific Project. These settings include:

  • General 
  • Timeouts
  • Advanced
  • Access
  • Integration
  • Headers
  • Cookies
  • Authentication
  • Alerts 

Users can customize these settings to configure the behavior of their project.

 

How to Access Project Settings

There are 2 ways to access the Project Settings:

Test Case Listing Page

    1. Open any Project
    2. On the , click on the Project Actions hamburger menu >> Project Settings


    3. The Project Settings modal will appear

Test Case Detail Page

    1. On the Test case listing page, click on the test Actions button >> Details or click on the test case name
    2. On the Test Case Details page, click on the Project Actions hamburger menu >> Project Settings


    3. The Project Settings modal will appear

 

General Tab

The General tab is available to update basic project details. The fields are as follows:

  • Environment: The project environment in which the test is created
  • Certificate Errors: An error that occurs when a website's security certificate is not trusted by the browser
  • HTTP Auth: Authentication details for the environment
  • Environment Management: This is used to override the existing URL for all test cases under the project
    Note: Use the syntax: https://www.existing-site.com::https://www.replace-with-site.com
  • Host: This is used for Basic Authentication credentials of test sites
  • Proxy Settings: Refers 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, the IP address and port, which will be used to route internet traffic for the test execution
  • Region: Select the Google Datacenter region in which the all test case is executing

 

Timeout Tab

The Timeout tab shows performance level time outs and thresholds for all the test cases under this Project.  If any of these set thresholds are exceeded during test case execution, the test case status will display a Warning.

  • Environment: Users can select Project Environment
  • 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
  • Page Load Alert Threshold: The amount of time it takes for a page to load before an alert is triggered, this alert is set up in the Alerts tab of the Test Settings modal
  • Page Performance Threshold: It allows users to set a maximum page load time, maximum DOM interactive time and maximum visual completion time
  • Page Load Timeout: The maximum amount of time the ML timing model will wait for a whole page to load before attempting object selection
  • Missing Element Timeout: The maximum amount of time the ML timing model will wait for an individual element to load before attempting object selection

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 Project Settings, is a section that showcases an extensive list of optional Project settings. It includes options such as enabling video execution in the cloud, setting Proxy at the Project 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.

  • Default browser for initial desktop execution: Users can select any browser as default for initial desktop execution
  • Default browser for initial mobile execution: Users can select any browser as default for initial Mobile execution
  • Visual Completion: Used to verify the web-Element visually
  • Fails on Invisible: When selected, the test will fail if the element is not visible on the web page
    Note: It is useful for ensuring that tests are passed or failed correctly when executed again in the future.
  • Window Width/Height: User can set the window width and height for the Project by inputting the value, 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.
  • Enable Logging: Generates the log files of test cases that capture relevant information, such as error messages, warnings, and other events
  • Open Shadow DOM: Allows users to access and interact with elements that are encapsulated by the Shadow DOM
  • Force System Screenshot: Captures the entire screen or a specific window screenshot
  • Disable Ajax cataloging: Turns off the use of asynchronous requests for updating or refreshing catalog data
  • Enable Trust Score: Uses machine learning to detect and fix errors in tests
  • Disable Notifications: Allows users to turn off notifications for particular projects
  • Detailed Logging: Provides a thorough and in-depth detailed logging of what is happening within a test case
  • Capture Network logs: 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: The test 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.
  • Disable iOS CORS: Disabling Cross-Origin Resource Sharing (CORS) restrictions on iOS devices
  • Update From Run Time: Allows users to update their test scripts while the test is running
  • 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.
  • Maximum Concurrent (Parallel) tests allowed: Allows maximum tests running in parallel at a time for a particular project
  • Orientation: Users can select either Portrait or Landscape page orientation for the test cases
  • Element match requirement default: User can set default value to show how much percentage a element will match
  • Full page visual check default: User can set default value to show how much percentage a page will match
  • Continue On Error: 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 down the execution of your tests.
  • Skip IE Clear Cookies: Tests are not affected by cookies stored in the Internet Explorer browser
  • Ping URL: User can input a URL in order to check the status of a URL before running a test
    Note: This feature can be used to ensure that the URL is available and that the test will run correctly
  • Show Extra Data: Additional data (screenshots, logs, and other data) associated with a test run will show in the test case
    Note: Additional data (screenshots, logs, and other data) can help with debugging and troubleshooting
  • Disable RCA: Disables the Root Cause Analysis (RCA) for a particular test
    Note: User can disable RCA for a specific test, or for tests that are not suitable for RCA
  • Bypass Previous Run Data: Bypasses the data from the previous run of a test and starts a new run with fresh data
    Note: It is especially helpful when testing in multiple environments
  • Ignore PSR ML Data: Ignores the Machine Learning (ML) data generated by the Performance Stress Report (PSR)
  • Un-Cropped Screenshots: Allows users to get a full view of the page and all the elements on screenshot
  • Timing Model: The maximum time the execution engine waits can be specified as the Missing Element Timeout on the Timeout TAB, this allows users to control how long the Functionize AI Timing Model waits for an element to appear - the more Aggressive the setting used, the faster the AI timing model executes, and the more Conservative the setting used, the slower the AI timing model executes
  • 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
  • Environment: Users can select an Environment for a particular project
  • Default schedule time (PST): Users can select default schedule time
  • DNS Override: Simulate different network conditions or to redirect domain names to local servers

Alert section:

Alerts can be set up at the Project level so Users can get alerts based on these parameters

  • Status: A measure of the success or failure of an action or test
  • Pageload Threshold: Allows users to set a maximum time limit for a page to load
  • Performance Downloaded: Allows to measure the performance of a web page and is tracked by Functionize every time a test runs
  • Performance Interactive: Allows users to interact with a test while it is running on the Functionize Test Cloud
    Note: It allows users to edit the test execution, so if an intermediate step fails, users can stop the failed test or rearrange the order of the tests in real time
  • Performance Firstpaint: Allows users to quickly identify and diagnose performance issues in their web applications
    Note: It also tracks page load speed and provides action duration reports to show the performance of each test action

 

Access Tab

The Access tab is used to make the owner of the Project.

  • Change Project Owner: Select the owner from drop-down then click on the Confirm button
  • Make Private Button: Used to make the Project Private


  • Select the Member(s) to give access to the Project
  • Click on the Confirm button

 

Integration Tab

The Integration tab is used to Integrate any other Website:

  • Website: Select the integration target website from the drop-down

 

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.

  • Click on Add New Header
  • Header: Input parameters name
  • Value: Input parameter value

 

Cookies Tab


The Cookies tab is used to inject cookies into a test case. For example, logging in a User without having to go through the login steps.

  • Click on Add new cookie
  • Cookie: Input cookie parameter(s) name
  • Value: Input cookie value

 

Alert Tab

The Alerts tab is used to send notifications about projects to the selected Users.

  • Select users for project notifications: Click the checkbox next to the User(s) name

 

Auth Tab

The Auth tab is used if the site under test employs HTTP authentication. The tester can enter the following authentication details:

  • 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