Skip to content

Fix cross-rule interference in ACT tests#353

Merged
koddsson merged 3 commits intomainfrom
fix/349-cross-rule-interference
Mar 13, 2026
Merged

Fix cross-rule interference in ACT tests#353
koddsson merged 3 commits intomainfrom
fix/349-cross-rule-interference

Conversation

@koddsson
Copy link
Owner

Summary

  • Fixed ACT "passed" tests that failed due to cross-rule interference when no scanner rule maps to the ACT rule
  • When expectedUrls is empty (no scanner rule maps to the ACT rule), the generated assertion now uses expect([]).to.be.empty to avoid false negatives from unrelated rules firing
  • Unblocked 3 previously skipped qt1vmo (image-alt) test cases that were ignored due to document-title cross-rule interference

Fixes #349

Test plan

  • All 175 tests pass
  • Previously skipped cross-rule interference tests now pass
  • No regressions

🤖 Generated with Claude Code

For "passed" ACT tests where no scanner rule maps to the ACT rule being
tested, the generated assertion now trivially passes instead of checking
that all scan results are empty. This prevents unrelated rules (e.g.
document-title) from causing false failures on tests focused on other
rules.

Removes 3 qt1vmo test URLs from ignoredExamples that were skipped due
to cross-rule interference, since they now generate correctly scoped
assertions.

Fixes #349

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@koddsson koddsson enabled auto-merge (squash) March 13, 2026 11:31
@koddsson koddsson merged commit 66ecc40 into main Mar 13, 2026
1 check passed
@koddsson koddsson deleted the fix/349-cross-rule-interference branch March 13, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix cross-rule interference in ACT tests by scoping scan results

1 participant