FA-83859 / Sports scoring and tiebreakers / Member archive

Rally log validation ignores the end-of-game cutoff · case 04

Corrupt characters are silently skipped or trailing garbage after a finished game is reported as an error.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

points is a string of rally winners, each character A or B. A game ends at the first point where a player has at least 4 points and leads by at least 2; characters after that point are ignored. Return "game A"/"game B" when finished; otherwise "deuce" when both have at least 3 points and are level, "advantage A"/"advantage B" when both have at least 3 points and differ by one, else "S-R" using the labels 0, 15, 30, 40 in A-B order. A character other than A or B that is reached before the game ends returns "invalid point <c>".

Why this case matters

Live scoreboards and umpire tablets derive the displayed tennis game score from a raw rally log.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: input validation scope	`"advantage B"`	`"invalid point x"`	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.