FA-84002 / Sports scoring and tiebreakers / Member archive

Strike not rotated at the end of an over · case 02

The same batter is shown on strike for the first ball of the new over.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Ball-by-ball innings tally. Events: "0".."6" runs off the bat (legal ball); "W" wicket (legal ball, no runs, the new batter takes strike); "wdK" wide: 1 penalty + K run wides, all extras, not a legal ball, K runs completed; "nbK" no-ball: 1 penalty extra + K runs off the bat, not a legal ball; "bK"/"lbK" byes/leg byes: K extras on a legal ball. Batters change ends when an odd number of runs is completed, and again after the 6th legal ball of an over. Batters are numbered 1, 2 and then 3, 4, ... as they come in; batter 1 starts on strike. Return [total, wickets, overs "O.B", extras, batter on strike].

Why this case matters

Scoring apps derive totals, overs and strike from ball events; extras and strike rotation are error-prone.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
control maiden over	`[0, 0, "1.0", 0, 1]`	`[0, 0, "1.0", 0, 2]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.