Checkbox Check or Uncheck Error

This error occurs when CheckView attempts to check or uncheck a checkbox during a test flow, but the checkbox does not end up in the expected state after all interaction attempts.

What Causes This Error?

CheckView uses multiple strategies to toggle checkboxes — direct interaction, clicking the associated label, and clicking ancestor labels. If none of these succeed, the step fails with one of two errors:

  • “Element is not checked” — A Check step tried to check a checkbox, but it remained unchecked after all attempts.
  • “Element is checked” — An Uncheck step tried to uncheck a checkbox, but it remained checked after all attempts.

Common Causes

1. The checkbox is inside a custom-styled component

Many themes and plugins replace native HTML checkboxes with custom-styled elements (toggle switches, styled checkmarks, etc.). The underlying <input type="checkbox"> may be hidden or positioned off-screen, making direct interaction fail. CheckView attempts to click the associated label as a fallback, but if the label structure is non-standard, this may also fail.

2. JavaScript prevents the state change

Some forms use JavaScript to control checkbox state — for example, enabling a checkbox only after accepting terms via a modal, or preventing unchecking once checked. If JavaScript overrides the click, the checkbox state won’t change.

3. The selector matches the wrong element

If the selector targets a wrapper <div> or <span> instead of the actual <input> element, CheckView may click the element but it won’t toggle the checkbox. The selector should target the <input type="checkbox"> directly.

4. The checkbox has a label with links

Checkboxes with labels like “I agree to the Terms and Conditions” contain clickable links inside the label. CheckView detects this and calculates a safe click position to avoid triggering navigation, but in some layouts this may not work perfectly.

How to Fix

  1. Verify the selector — Open your browser’s developer tools (F12), find the checkbox, and confirm your selector targets the <input type="checkbox"> element directly. See Mastering Selectors for guidance.
  2. Check for custom checkbox components — If the checkbox uses a custom component (common with WooCommerce checkout blocks, Elementor, or theme builders), try targeting the native input inside the component. You may need to use a more specific CSS selector.
  3. Add a Click step instead — If the Check/Uncheck step isn’t working, try replacing it with a Click step targeting the checkbox or its label. This can sometimes work better with custom checkbox implementations.
  4. Check prerequisite steps — Some checkboxes only become interactive after other form fields are filled in or a prerequisite action is completed. Ensure your test flow fills in any required fields before the Check/Uncheck step.

Related

Docs