e2e: a Spectator watches a Room with both Seats taken #197

New issue

Closed

opened 2026-09-01 13:44:38 +00:00 by root · 3 comments

root commented

2026-09-01 13:44:38 +00:00

(Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#197, opened by @amaurycoudr on 2026-09-01 13:44 UTC.
Closed on GitHub on 2026-09-24 10:20 UTC as completed.

Parent

#191

What to build

A third browser opens a Room whose Seats are both taken, and watches: it is told plainly that it is watching rather than playing, it sees Moves arrive as they are played, its board is oriented White at the bottom because it has no Color, and the only thing it can do is leave.

A Spectator is the case where the Room's Connection count and its Seat count differ, so this is the ticket that proves the suite can model that difference. It depends on the Move helper, because "sees Moves arrive" is the assertion that makes watching worth testing at all.

Acceptance criteria

A third browser context opens a Room whose two Seats are occupied and is not given a Seat
The Spectator is told it is watching this game
A Move played by a seated Player appears on the Spectator's board without a reload
The Spectator's board is oriented White at the bottom
The Spectator has no control that would play a Move, resign, or make an Offer
The Spectator is told how an Offer resolved and how the Game ended
The Spectator can leave the Room
All five gate commands pass, and the suite passes

> _Imported from GitHub [amaurycoudr/chess-project#197](https://github.com/amaurycoudr/chess-project/issues/197), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-09-01 13:44 UTC._ > _Closed on GitHub on 2026-09-24 10:20 UTC as completed._  --- ## Parent #191 ## What to build A third browser opens a Room whose Seats are both taken, and watches: it is told plainly that it is watching rather than playing, it sees Moves arrive as they are played, its board is oriented White at the bottom because it has no Color, and the only thing it can do is leave. A Spectator is the case where the Room's Connection count and its Seat count differ, so this is the ticket that proves the suite can model that difference. It depends on the Move helper, because "sees Moves arrive" is the assertion that makes watching worth testing at all. ## Acceptance criteria - [ ] A third browser context opens a Room whose two Seats are occupied and is not given a Seat - [ ] The Spectator is told it is watching this game - [ ] A Move played by a seated Player appears on the Spectator's board without a reload - [ ] The Spectator's board is oriented White at the bottom - [ ] The Spectator has no control that would play a Move, resign, or make an Offer - [ ] The Spectator is told how an Offer resolved and how the Game ended - [ ] The Spectator can leave the Room - [ ] All five gate commands pass, and the suite passes

root commented

2026-09-01 13:44:38 +00:00

(Migrated from gitlab.core-project.space)