Database Test Submission Validation

CheckView ensures accurate testing and verification of database submissions by implementing a process that integrates with native form plugin databases. This validation mechanism copies database submissions from the native plugin database into the CheckView database table, where the actual verification process takes place by matching the data with the platform’s expected outcomes.

Current Testing Capabilities

When validating database test submissions, CheckView’s integration is designed to confirm:

• Data Capture: Submissions are successfully captured in the native plugin database, ensuring the form is functioning as expected.
• Data Matching: Submissions are duplicated and stored in the CheckView database table, where they are compared against expected values or platform-specific criteria for accuracy.

However, please note:

• Scope of Validation: CheckView focuses on validating the presence and correctness of submissions against defined criteria. It does not verify additional elements such as third-party integrations or downstream data processing. Furthermore, validation occurs in the CheckView database table, not the form plugin or native WordPress database table.
• Customization: The system’s validation criteria are based on default configurations but can be tailored for specific test scenarios.

Limitations and Considerations

While CheckView’s database validation process is highly effective for ensuring data accuracy and proper form functionality, there are certain limitations to consider:

• Contact Form 7: Since Contact Form 7 does not have a built-in feature to save form submissions to a database, our platform temporarily stores test submissions in a dedicated CheckView database table for validation. Once the submission is successfully verified, it is automatically removed. If a site is using Flamingo, we validate the test submission against the Flamingo database entry instead, ensuring accuracy before removing the test submission.
• Native Plugin Dependencies: Validation is reliant on the native plugin database structure. Changes to the plugin or its database schema may require updates to the CheckView integration.
• Complex Validation Requirements: Scenarios involving intricate data relationships or custom field mappings may require additional setup or manual validation steps.