Feature Ideas

It would be helpful to have a button or link directly on each Test Flow page that allows users to open a support ticket related to that specific flow: • Add a visible “Open Support Ticket” button/link on the Test Flow detail page. • The button should link to the CheckView support/contact form. • Pass relevant query parameters (e.g., Flow ID, Flow Name, Org ID, etc.) in the URL so the ticket form is auto-filled with context from the specific test flow. • Include a subject prefix like “Issue with Test Flow: [Flow Name]” to streamline support intake.

Requesting a feature that allows users to fix failed test steps and resume execution from any point, no need to rerun the entire test upon failure, just rewind to the failure, apply fixes, and continue validating from there. This would streamline troubleshooting by enabling faster iteration when fine-tuning flows, especially after failed interactions or unexpected behavior mid-test.

While creating test flows and setting form URLs for , it would be great to support traditional builders besides Gutenberg-based builders for detecting URLs where the forms are found: Elementor Beaver Builder Divi Builder Bricks Builder

I’d like to request a feature where CheckView automatically retests failed checks at scheduled intervals (e.g., every hour) until the issue is resolved. This would function similarly to an uptime monitor, providing updated status checks instead of requiring manual intervention each time a test fails.

Effective collaboration and documentation are essential for maintaining accurate and efficient QA processes. With Test Flow Comments, users can now add inline comments directly to test flows. This feature enhances communication, making it easier to document failures, provide context, and share insights with the team.

Many websites and staging environments use Basic Authentication (Basic Auth) as a simple security layer to restrict access. Currently, CheckView may encounter authentication barriers when testing these sites. Adding native support for Basic Auth would allow tests to seamlessly bypass authentication prompts and execute without manual intervention.

Certain websites require interaction with specific elements before test execution begins or at various points during the test. This is useful for handling pop-ups, cookie banners, modals, and dynamic UI elements that may interfere with automation. Adding support for pre-test and in-test click actions on specific CSS classes would improve test stability and execution flow.

Currently, email notifications triggered during CheckView test executions are typically suppressed or redirected to test-specific inboxes to avoid sending test emails to real recipients. However, certain scenarios require allowing email notifications to reach original recipients for end-to-end validation, such as testing user communications, transactional emails, and workflow automations.

Many web applications generate PDFs for invoices, reports, order confirmations, and other critical documents. Automated PDF Testing in CheckView would allow users to verify the accuracy of generated PDFs by extracting and validating text, structure, layout, and embedded elements.

Currently, test executions in CheckView run to completion unless they encounter a failure. However, there are scenarios where users may need to abort a test flow or execution manually or conditionally to optimize test runs and prevent unnecessary processing. Implementing an Abort Test Flow feature would allow users to stop tests dynamically based on predefined conditions or manual intervention.

Many web applications rely on date pickers for user inputs, making it essential for automated tests to interact with them correctly. CheckView should support a variety of date picker formats and behaviors to ensure test execution across different implementations.

Forminator Forms support would enable auto-generated test flow for forms built with the Forminator plugin. This would also allow bypassing of anti-spam mechanisms, validation of submission data and email verification similar to existing supported form plugins.