🎉 Ends Today! Unlock up to 35% with our Black Friday lifetime discount before its gone! 🎉
🎉 Unlock up to 35% with our Black Friday discount for a limited time! 🎉
Handling Bricks Forms in Test Flows
Bricks Builder dynamically assigns new unique IDs to form fields in every browser session, preventing auto-generated test flows from functioning reliably. While the form ID remains static, individual field IDs change per session, making standard field ID-based automation unreliable.
Unlike most major form plugins, Bricks does not use static field IDs. Instead, it regenerates field IDs dynamically per session, a feature designed to support forms inside loop structures. As a result, auto-generated test flows relying on field IDs will fail on subsequent runs.
Since auto-generated test flows cannot consistently interact with Bricks forms, users must create custom test flows that target the name attribute instead of the field ID.
Steps to Create a Custom Test Flow for Bricks Forms
- Identify the Field Name Attribute:
- Inspect the form field in your browser (Right-click → Inspect Element).
- Locate the name attribute (e.g., name=”email”).
- Manually Configure the Test Flow:
- Instead of relying on dynamically changing field IDs, configure test steps to target the name attribute.
- Example selector: input[name=”email”]
- Run and Verify the Custom Test Flow:
- • Execute the test flow multiple times across different sessions to confirm reliability.
If Checkview adds full Bricks Forms support, we will implement custom logic to ensure all test flows prioritize the name attribute over the field ID automatically. Until then, auto-generated test flows will not work with Bricks forms, and users should rely on custom test flows using the name attribute.