Skip to content

Attack unclassified transition rules with the invariant axis's operations - #102

Open
Mpdreamz wants to merge 1 commit into
mainfrom
heed/browse/issue-47-83529c
Open

Mpdreamz wants to merge 1 commit into
mainfrom
heed/browse/issue-47-83529c

Conversation

@Mpdreamz

Copy link
Copy Markdown
Contributor

Closes #47

Why: a hand-written Transitions/CheckTransition rule is Unclassified, so no axis ran it. InvariantAsync only looked at Axis.Invariant rules, so a planted bug the rule should catch left the suite green; only the report line mentioned it.

What: this takes the first option from the issue. OperationsKeepInvariants now also checks unclassified rules on every step the operations take. The Invariant axis is applicable (and a case in Cases) when a set has only unclassified rules and there are operations. The report line now says they are checked against the operations.

Not done: Vacancy counter-examples for unclassified rules, or an AllowUnclassified() opt-in.

Tests: new A_hand_written_transition_rule_is_attacked_by_the_operations_and_fails_when_one_breaks_it fails without the change and passes with it. The full CsCheck suite passes on net10.0 (313/313). I did not run net11.0.

🤖 Generated with Claude Code

…ions

A hand-written Transitions/CheckTransition rule is Unclassified, so no axis
ran it and a planted bug left the suite green. The invariant axis now checks
those rules on every step its operations take, and is a case when only
unclassified rules and operations exist.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

Unclassified transition rules are never attacked, and the suite stays green

1 participant