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.

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)
   • What It Will Do: In future updates, this setting will allow you to specify:
     • Browser type and version (e.g., Chrome, Firefox, Safari).
     • Operating system and version.
     • Screen resolution.
     • Device type (e.g., desktop, tablet, mobile).
   • Current Status: Currently, CheckView supports one standard browser configuration.
   • Pro Tip: Stay tuned for this feature to test responsiveness or cross-browser compatibility directly in CheckView.
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.

Pro Tips for Using Advanced Settings

1. Optimize Step Timing Strategically:
   • Use Step Delay for global timing adjustments on slow sites.
   • Add specific Pause Steps for localized delays without slowing down the entire test flow.
2. Balance Element Timeout:
   • If a test frequently fails due to missing elements, increase the Element Timeout.
   • Avoid unnecessarily high timeouts, as they can inflate test durations without adding value.
3. Customize User Agent for Specific Scenarios:
   • Research and copy valid user agent strings for the browsers or devices you want to simulate.
   • Use free tools like WhatIsMyBrowser.com to generate user agent strings.
4. Understand Environmental Factors:
   • Slow tests can result from external factors like server load or third-party scripts. Use Step Timing settings as part of a broader optimization strategy.

The Advanced Settings in CheckView offer powerful tools for refining your test flows. By fine-tuning Step Timing and leveraging browser-related settings like Custom User Agent, you can ensure your tests are accurate, efficient, and tailored to your needs. .