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 by default. While the form ID typically remain 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 by default in many cases. 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 unqiue name attribute or set unique IDs in the Bricks form input settings. Below are details on using the field name attribute to create the proper setup for a Bricks form to be tested:

Steps to Create a Custom Test Flow for Bricks Forms

1. Identify the Field Name Attribute:
   • Inspect the form field in your browser (Right-click → Inspect Element).
   • Locate the name attribute (e.g., name=”email”).
   • Note if you are attribute has an arbitrary ID in it, not a unique name, then you need to set a unique attribute name or ID in the Bricks field input settings before processing.
2. 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”]
3. 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.