Form Actions and Integrations

While CheckView supports comprehensive form testing, limitations exist when dealing with third-party integrations, external triggers, and WooCommerce-specific actions. Currently, CheckView does not automatically disable these integrations or actions during tests, and this should be considered and reviewed when configuring your testing environment.

Third-party form integrations, WooCommerce actions, and external triggers, such as CRM submissions, Zapier, email notifications, and API calls will operate as they normally would in a live environment. This means that any form submissions, automated emails, triggered actions, or WooCommerce transactions connected to external systems will run during testing, potentially generating actual records or notifications.

To prevent unintended actions:

• Use Conditional Logic to Disable Integrations When Possible: Some form plugins and WooCommerce integrations provide conditional logic capabilities that allow you to control actions or triggers based on specific criteria, such as filtering field values like email addresses. When using CheckView, you can leverage this feature to prevent actions from being executed during tests by filtering out emails containing the “checkview.io” domain. Since CheckView’s dynamic email addresses always utilize this domain, applying this filter ensures no legitimate submissions are affected. Where supported, implement these filters to disable specific actions and external triggers during testing, ensuring a interference-free testing process.
• Use a Staging Environment: Whenever possible, run tests in a staging environment where these external triggers and integrations are disabled or safely isolated from live data.

Note: This video’s UI is outdated, but is still relevant to the workflow.