Architect Settings

Architect Settings allow for a more fluid test case creation experience using Architect by establishing a set of criteria for a streamlined process. 

Access Architect Settings

  1. Launch Architect via the Create New Test process.
  2. Click the Insert Action button.
  3. Click on Settings gear icon.
  4. All settings can be toggled ON/OFF.

List of Architect Settings

Faster Performance: Not recommended unless there are a large number of elements on your site. When enabled we don’t pull as much data during Architect test recording. Executions may run more slowly until the test passes as we learn your application.

Coverer: Coverer must be enabled in order to perform a double click action.

Mouseover: When on/enabled, a mouseover hover action is disabled in test creation.

Mouseout: When on/enabled, a mouseout hover action is disabled in test creation.

Focus: When enabled, the site under test cannot force focus away from Architect onto a specific element when the page loads.

Long Text: By default, we limit the number of characters in any field to 250. When enabled, there is no limit to the number of characters of text that can be captured. 

Force 100% Zoom: Some sites force a particular zoom setting causing Architect to appear broken within a smaller rectangle. If testing a site such as this, set the Force 100% Zoom to on/enabled.

Enable AI Assist: When on/enabled, the user will receive various messages throughout the test creation process to encourage higher quality, robust tests. On/enabled by default for all users.

Disable Service Workers: Some sites use service workers to cache network data. When this happens, Architect cannot record actions correctly. Set this to off/disabled to prevent this situation from occurring.

Enable Tab Keypress: Adds Tab key as an option for keypress actions.

Enable SVG Children: When enabled, Architect can properly record user interactions with SVG child elements.

Enable Pointer Events: Some sites disable pointer events for items such as tooltips. Enabling this gives Architect the ability to click on these elements therefore making them verifiable. 

Always clear browser data:  When on/enabled, this feature will make sure the browser data/cookies are always cleared before proceeding to record.  The user will no longer see the Cookies Warning pop up when beginning a test case in Architect.