Run the browser suite against a deployed URL #305

New issue

Closed

opened 2026-10-09 09:19:49 +00:00 by root · 7 comments

root commented

2026-10-09 09:19:49 +00:00

(Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#305, opened by @amaurycoudr on 2026-10-09 09:19 UTC.
Closed on GitHub on 2026-10-09 12:20 UTC as completed.

Parent

#303

What to build

The browser suite can run against an already deployed URL: a new target mode that starts no server and takes its base URL from the environment. The local and built modes stay as they are, and so does the guard that refuses to let CI fall back to dev servers. The suite itself does not change: every test already mints its own Room through the UI, so it can run against a shared deployment. Nothing is added to the front or the API for it (ADR 0022).

Verifiable now by running it by hand against the current production URL.

Seam: Deployed browser suite (e2e)

Acceptance criteria

With the deployed target and a base URL, the suite runs without starting any server and drives that URL
The deployed target without a base URL fails at once with a message naming the missing variable, rather than defaulting
The local and built targets behave exactly as before, including the CI guard
The whole suite passes by hand against the current production deployment
apps/e2e/CODING_STANDARDS.md's Running section names the new target

> _Imported from GitHub [amaurycoudr/chess-project#305](https://github.com/amaurycoudr/chess-project/issues/305), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-10-09 09:19 UTC._ > _Closed on GitHub on 2026-10-09 12:20 UTC as completed._  --- ## Parent #303 ## What to build The browser suite can run against an already deployed URL: a new target mode that starts no server and takes its base URL from the environment. The local and `built` modes stay as they are, and so does the guard that refuses to let CI fall back to dev servers. The suite itself does not change: every test already mints its own **Room** through the UI, so it can run against a shared deployment. Nothing is added to the front or the API for it (ADR 0022). Verifiable now by running it by hand against the current production URL. Seam: Deployed browser suite (e2e) ## Acceptance criteria - [ ] With the deployed target and a base URL, the suite runs without starting any server and drives that URL - [ ] The deployed target without a base URL fails at once with a message naming the missing variable, rather than defaulting - [ ] The local and `built` targets behave exactly as before, including the CI guard - [ ] The whole suite passes by hand against the current production deployment - [ ] `apps/e2e/CODING_STANDARDS.md`'s Running section names the new target

root commented

2026-10-09 09:19:49 +00:00

(Migrated from gitlab.core-project.space)

GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links).

Parent (sub-issue of): #303
Blocking: #308

> _GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links)._  - Parent (sub-issue of): #303 - Blocking: #308

root (Migrated from gitlab.core-project.space) closed this issue

2026-10-09 12:20:43 +00:00

root commented

2026-10-13 08:39:26 +00:00

(Migrated from gitlab.core-project.space)

mentioned in issue #308