Skip to content

Trigger only one rule to fail on an element, meta_redirect_optional Violation not meta_refresh_delay Needs Review #2176

@philljenkins

Description

@philljenkins

While testing ACT meta related test cases, multiple rules are triggered for the same element with the issue.
I do not think this second rule should also trigger a Needs Review against the same element.

Checker rules

  • meta_redirect_optional is mapping to the ACT rule bisz58.
  • meta_refresh_delay is mapping to the ACT rule bc659a.

ACT rule bisz58 Meta element has no refresh delay (no exception) with 3 failed test cases:

Failed examples should be failed by at least one of the Checker rules fail reason codes.

  • Failed Example 1
    • Rule ID: meta_redirect_optional Reason ID: fail Violation
    • Rule ID: meta_refresh_delay Reason ID: potential_refresh Needs Review I do not think this second rule should also trigger against the same element.
  • Failed Example 2
    • Rule ID: meta_redirect_optional Reason ID: fail_longrefresh Violation
    • Rule ID: meta_refresh_delay Reason ID: potential_refresh Needs Review I do not think this second rule should also trigger against the same element.
  • Failed Example 3
    • Rule ID: meta_redirect_optional Reason ID: fail_longrefresh Violation
    • Rule ID: meta_refresh_delay Reason ID: potential_refresh Needs Review I do not think this second rule should also trigger against the same element.

ACT rule bc659a Meta element has no refresh delay with failed test cases:

Metadata

Metadata

Labels

ACTIssues/Rules related to ACTT70

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions