Search

Understanding Test Action Settings

Each test action in a Functionize test case has its own settings, flags, and options that allow you to fine-tune behavior. Action Settings can be accessed in two ways: via the Test Details page or via the Slider View.

Accessing Test Action Settings

Method 1: From the Test Details Page

  1. Open Test Details – Navigate to the Test Details page for your test.
  2. Expand Action Details – Click the action banner to expand details for that action.
  3. Access Settings – The expanded details pane contains all configurations.

Method 2: From the Slider View

  1. Open Test Details – Navigate to the Test Details page for your test.
  2. View Results – Click the View Results button at the top, or View next to any action.
  3. Access Action Settings – In the left-hand slider panel, click the gear icon for the action you want to edit.
  4. Access Settings – The popup window contains all configurations.

Note: Any adjustments must be saved using the Save button before exiting the settings window.

Test Action Options

Alongside the Settings and Advanced options tabs, there are additional options that can be taken on the test action:

  • Fail – Force-fail the test action.
  • Delete – Delete the test action.
  • Local Edit – Use Local Edit to modify the test action.
  • Clone – Copy the test action (adds the clone directly after the original).

Settings Tab Options

The Settings Tab provides the following options:

  • Verifications
    • DOM – Use operators to compare a DOM attribute to a specified value.
    • CSS – Use operators to compare a CSS attribute to a specified value.
    • Visual Verification – Use a visual verification for the test action.
      • Visual Check Type – Choose Baseline Comparison or Previous Action
      • Visual Match Requirement – Specify the percentage match threshold.
  • General
    • Optional – When selected, the test case execution will not fail if this action fails.
    • Skip Action – When selected, the test case execution will skip this action.
  • Mappings
    • Manage Extension – Add a pre-hook or post-hook extension to this action.
    • Add Test Data – Add test data to use with this action.
  • Note – Add notes about the test action.
  • Outcome Override – Provide JavaScript to override the result from any custom JS that is run in the test action.

Advanced Tab Options

In addition to the basic buttons above, the Advanced Tab provides:

  • Advanced General – Fine-tune execution behavior.
  • Miscellaneous – Context-specific settings.
  • Runtime Timeout – Control how long the system will wait before marking the action as timed out.
  • Options
    • Skip Screenshot – Do not take a screenshot for this action.
    • Clear Cookies – Clear cookies before the action executes.
    • Skip Scroll – Prevents Functionize from automatically scrolling to the element before interaction.
    • Enable Force React – Forces a React-based application to re-render components during the test.
    • Positional Selection – Selects an element by its position rather than attributes.
    • Override Default Self-Heal – Modifies the default threshold of acceptance for self-healing actions.
    • Enable Timing Model Override – Override the default settings for the timing model for this action.
  • Selector Type – Choose ML Selection (Default), Selector, or JS Override Selector.
  • Pre-Script – Add scripts to run before the action executes.
  • Post-Script – Add scripts to run after the action completes.
  • Element Miner – Provide selection information using the Element Miner syntax.

Additional Settings for Input Actions

An Input Action is used to enter data into a field within the Application Under Test (AUT). Input actions have slightly different options for configuration, including the ability to modify focus and data encryption settings.

Settings Tab

  • General section
    • Text field – Contains the value being input.
    • Skip Action –
    • Don’t lose focus –
      • When ON (default)
        • Keeps the mouse cursor in the field after data entry.
        • Prevents error messages that require focus loss from appearing.
        • Example: If “Don’t Lose Focus” is ON for an email field, the test will not detect an “invalid email format” error, since the field never loses focus.
      • When OFF
        • Allows the input field to lose focus after data entry.
        • Triggers UI processes or error messages that rely on focus changes.
        • Example: In Salesforce, turning this setting OFF allows the “invalid email format” error to appear when the field loses focus.
  • Executor Type – Choose ML, Operating System, Native JavaScript, or Force Selenium.

The Mappings and Note sections are the same as for other action types.

Advanced Tab

The Advanced tab for Input Action settings adds the following options:

  • Append – Append to, rather than replace, the value in the target field.
  • Encrypt – Encrypt the provided value to protect sensitive data during test execution.
  • Native Individual Characters – Perform input one character at a time, simulating natural human typing instead of pasting or bulk entry.
  • Outcome Override – Provide JavaScript to override the result from any custom JS that is run in the test action.

The other sections are the same as for other action types.

Input Encryption Notes

  • If an encrypted value is reused via Data from Previous Action, it is not automatically encrypted.
  • Changing the Encrypt status requires re-execution to update masking.
  • In cases where the test revisits the same input field later, masking may not persist. Add custom JavaScript if persistent obscuring is required. Contact Functionize Support for assistance.
  • Functionize makes a best effort to obscure fields in screenshots, but behavior may vary with navigation flows.

Summary

Action Settings give you fine-grained control over each test action, from simple edits to advanced runtime configuration. Key features include:

  • Access via Test Details Page or Slider View.
  • Advanced options like pre-/post-scripts and timeouts.
  • Focus Management (Don’t Lose Focus) for accurate UI simulation.
  • Encryption for protecting sensitive test data.

By combining these settings, Functionize ensures that every test action is flexible, secure, and aligned with real-world user behavior.

 

Automation Inputs More Characters Than the Field Limit

Sometimes automated tests type into a text field faster than the field’s MAXLENGTH validation can detect, causing more characters to be entered than allowed during manual typing.

How to Enable Native Individual Characters

To make sure the automation follows the field’s character limit, you should enable manual-style typing. This makes the automation enter text one character at a time, allowing the MAXLENGTH rule to work properly.

Steps:

  1. Find the input action in your test.

  2. Open the Advanced Settings for that action.

  3. Turn on Native Individual Characters.

When this option is enabled, the automation types each character individually and will not exceed the field’s character limit.

Limitations

There are no known limitations for this feature.