iFrames Support

CheckView now supports interactions within iFrames using the Advanced Methods → iFrame option, allowing you to test embedded forms, payment fields, and other content that loads inside a nested browsing context.

When to Use This Feature

Many modern web experiences use iFrames to embed third-party forms, checkout flows (such as Stripe Elements), CRMs, and support tools. By default, browsers isolate iFrame content from the parent window for security, so CheckView needs to be explicitly told which iFrame to interact with for each step.

How to Use iFrame Support in CheckView

    1. Create or Edit a Step: Navigate to the test flow where you need to interact with content inside an iFrame.
    2. Click “Advanced Methods”: On any step that requires interaction with an element inside an iFrame (e.g., Assign, Click, Select, etc.), click the Advanced Methods toggle. Note most steps support iFrames, but not all, you can review the step parameters.
    3. Select “iFrame”: Choose the iFrame option from the dropdown. This tells CheckView that the action should take place inside a specific iFrame rather than the main page.
    4. Set the iFrame Selector: Input a CSS or XPath selector for the iFrame element. This selector should target the actual <iframe> element on the page, such as: 
    iframe#payment-frame
iframe[src*="typeform"]
.embedded-form iframe

    Best Practices

    • Use full selectors: Ensure your iFrame selector is specific and stable. Avoid overly generic selectors like just iframe unless there’s only one on the page.
    • Repeat for every iFrame step: Each step within an iFrame must explicitly set the iFrame selector in the advanced settings, CheckView does not persist the frame context between steps.
    • Combine with Pause or Wait: Some iFrames load dynamically; consider using a short Pause or Assert Element Is Present before interacting with fields inside the iFrame.

    Limitations

    • Not all embedded providers structure their content cleanly, if you’re unable to interact with a form or field, check for obfuscated or rotating class names.
    • Cross-domain restrictions may still apply if the iFrame content uses advanced sandboxing or CSP headers that block automation tools.

    Docs