# Testing a 38-match Premier League season challenge

A full Premier League season gives every club 38 matches. That makes an unbeaten-season simulator easy to describe, but difficult to balance. A player must manage wins, draws, and losses across the entire schedule without letting one bad result end the run.

I used the [Premier League 38-0 challenge](https://wordlecup.today/38-0/premier-league/) as a compact test case for this kind of browser game. The useful part is not only the final record. The game also makes each decision visible, so a tester can check how the interface responds after a win, a draw, or a loss.

## A small test checklist

1. Start a new season and confirm that the record is 0 wins, 0 draws, and 0 losses.
2. Play several matches and check that the match count increases by one each time.
3. Confirm that a draw preserves the unbeaten run.
4. Confirm that a loss changes the season state immediately.
5. Refresh the page and verify whether the current run restores as expected.
6. Complete all 38 matches and check the final summary.

The distinction between a draw and a loss matters. A draw is not a perfect result, but it still protects an unbeaten campaign. The interface should explain that state clearly instead of treating every non-win as the same outcome.

## Why this format works for short sessions

The challenge has a clear finish line. It does not ask the player to learn a large ruleset before the first action. Each match produces immediate feedback, while the 38-match target gives the session a longer arc.

For developers, the same structure is useful as a state-management exercise. The result history, match counter, persistence behavior, and completion state can all be checked without a large testing harness.