Feature Ideas

I would love if there were a way to send a monthly report to clients about the uptime of their form. Something like the number of tests and the percentage of successful ones. This would be ideal to integrate with something like WPRemote or WPUmbrella that can feed CheckView data into the monthly reports we are already sending.

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.

The more sites we add, the more effort we have to spend when we want to change the schedule of the test runs. It would be super handy if there is a bulk update feature where we can update all flows or just selected ones in bulk.

Currently, when creating or editing a test schedule, users can only select one day of the week (for weekly) or one day of the month (for monthly). It would be helpful to allow multiple selections for these options, for example, running a test every Monday and Thursday, or on the 1st and 15th of each month. It would be nice if we could: • Replace the existing single-select dropdown with a multi-select dropdown or checkbox list. • Support selecting multiple days in both “Weekly” and “Monthly” schedule types. • Display selected days clearly in the schedule summary for clarity.

Summary Please add support for verifying database submissions that include country-coded phone numbers (e.g., +41, +49, +1). Currently, CheckView does not support database verification for these formats, requiring the verification step to be disabled. Context This request arises from troubleshooting a Gravity Flow form where database verification had to be disabled because CheckView could not validate the country-coded phone number stored in the submission. Problem When Gravity Forms submissions use phone fields with country codes, CheckView is unable to validate the phone number stored in the database. This limitation prevents end-to-end verification for forms that rely on international phone formatting, which is common for multilingual or multinational websites. As a workaround, the database verification step must be disabled, reducing the reliability of automated tests. Enable CheckView to: Correctly interpret and validate phone numbers that include country codes.Match database-stored phone numbers regardless of formatting variations (e.g., spaces, parentheses, prefix symbols).Allow the database verification step to remain active for forms using international phone fields. Benefits Full E2E verification for Gravity Forms and other form systems using international phone input fields. More robust and globally compatible automated testing.

It’d be great if I could pick a specific device to test on (like iPhone 15 Pro, Galaxy S24, or iPad) instead of only having the generic mobile or desktop options. This would help simulate real-world scenarios more accurately.

It’d be amazing if CheckView had an REST API so I could trigger tests or pull results automatically.

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.

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.

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.

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.