FAILURE MAP
← Case archive

FA-83950 / Sports scoring and tiebreakers / Member archive

Point-by-point service starts when only one player reaches ten · case 05

At 10-6 the server changes every point instead of every two points.

Member previewVariant 5 · 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 fixtureActualExpectedOutcome
regression: expedited deuce condition[10, 8, null, "A"][10, 8, null, "B"]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.

Sign in to the archive ↗