Test Flow Advanced Settings

The Advanced Settings in CheckView’s Test Flow Editor provide precise control over how the bot interacts with your website within a specific test flow. These settings are ideal for troubleshooting failed test flows, optimizing timing, or simulating specific browser conditions. Note these default test flow settings can also be set within the Organization Settings.

Step Timing Settings

The Step Timing section controls how quickly the CheckView bot progresses through a test. It includes two key settings:

  1. Step Delay
    • What It Does: Sets the delay between each test step.
    • Default: 1 second.
    • Range: 0–5 seconds.
    • Use Case: Adjust this setting if your website is generally slow or test steps fail because the bot moves too quickly for the site to respond. Increasing the delay gives the website more time to process between actions.
    • Pro Tip: Use Step Delay sparingly. If only one or two fields require extra time (e.g., during a page reload or a slow API call), add a Pause Action Step instead. This keeps the test flow efficient while addressing specific timing issues.
  2. Element Timeout
    • What It Does: Specifies how long the bot waits for an element to appear or load before interacting with it.
    • Default: 10 seconds.
    • Range: 1–10 seconds.
    • Use Case: Lower the timeout for faster websites to minimize test runtime. Increase the timeout for sites with elements that load slowly, such as after complex JavaScript rendering or server delays.
    • Pro Tip: Use a balanced approach. A very short timeout (e.g., 1–2 seconds) can result in false failures, while unnecessarily long timeouts may slow down testing.
  3. Typing Method
    • What It Does: Determines how CheckView inputs text during test execution, allowing you to control whether the bot types instantly or simulates a more human-like input style.
    • Default: Instant (default, fastest)
    • Options:
      • Instant (default, fastest): Fills all text fields instantly. Recommended for most tests where speed and efficiency are the priority.
      • Human (more natural, slower): Types characters one by one to mimic real user behavior. Ideal for tests that rely on field-level validation, input timing, or conditional logic triggered by key events.
    • Use Case: Use Instant Mode for typical forms, checkout flows, and general automated testing to minimize runtime and improve efficiency. Switch to Human Mode for forms that rely on on-input validation, dynamic field responses triggered by typing behavior, or in cases where certain text fields require more natural input for compatibility.

Browser-Related Settings

The Browser section allows you to configure how CheckView simulates the browsing environment. While currently limited, these settings are foundational for more advanced options coming soon.

  1. Browser Platform (Future Feature)
  2. Custom User Agent
    • What It Does: Allows you to override the default CheckView user agent with a custom one.
    • Use Case: Simulates requests from specific browsers or devices for more realistic testing. Bypasses firewalls or analytics tools that may flag or block the default CheckView user agent.
    • Pro Tip: Use this setting to prevent CheckView from appearing in analytics reports by mimicking a standard browser user agent. Ensure the user agent string matches your testing scenario for accurate results.

Docs