Reported by:
Oleh B.
Issue:
Not all checks from the test suite are executed, and the reason is not displayed. Users are confused about why some checks are skipped.
Root Cause:
Checks are assigned based on page_type matching. If the identified page type doesn't match the check's page_type, the check is not executed.
Current Behavior:
  • Checks require specific page_type to execute
  • If page type doesn't match, check is silently skipped
  • No indication in UI that checks were skipped
  • No explanation of why checks weren't assigned
Examples:
  • Check configured for "Login Page" won't run on "Home Page"
  • Check with specific page_type won't run if AI identifies page differently
  • No visibility into the page type matching logic
Current Workaround:
Set page_type to "Any" for checks that should execute on all pages.
Shipped Improvement:
Show unassigned checks in the UI
User Impact:
  • Better understanding of test coverage
  • Reduced confusion about "missing" checks
Use Cases:
  • Verify all intended checks are running
  • Optimize check suite coverage