FA-83954 / Sports scoring and tiebreakers / Member archive

Service changes every point from the start · case 04

The next server is wrong after the first point of the game.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

One table tennis game to 11 with a two-point lead; later rallies are ignored. Service changes after every two points; once both players have at least 10 points it changes after every point. Return [a, b, winner, None] when finished, else [a, b, None, next server].

Why this case matters

Match software must show who serves next, especially after 10-10.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
boundary second point same server	`[0, 1, null, "B"]`	`[0, 1, null, "A"]`	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.