Run the browser suite against each preview #308

Closed
opened 2026-10-09 09:19:58 +00:00 by root · 8 comments
root commented 2026-10-09 09:19:58 +00:00 (Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#308, 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

After each preview deploy, the browser suite runs against that preview in its deployed target, so a regression only the image, the proxy, HTTPS or the stream through Traefik can cause fails a check on the PR. The trace upload on failure works as in the existing CI browser job.

Seam: Deployed browser suite (e2e)

Acceptance criteria

  • Each successful preview deploy is followed by the browser suite against that preview's URL
  • A failing test fails a check visible on the PR, with traces uploaded
  • A failed deploy does not run the suite
  • The existing CI browser job against the built target is unchanged
> _Imported from GitHub [amaurycoudr/chess-project#308](https://github.com/amaurycoudr/chess-project/issues/308), 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._ <!-- github-issue:308 --> --- ## Parent #303 ## What to build After each preview deploy, the browser suite runs against that preview in its deployed target, so a regression only the image, the proxy, HTTPS or the stream through Traefik can cause fails a check on the PR. The trace upload on failure works as in the existing CI browser job. Seam: Deployed browser suite (e2e) ## Acceptance criteria - [ ] Each successful preview deploy is followed by the browser suite against that preview's URL - [ ] A failing test fails a check visible on the PR, with traces uploaded - [ ] A failed deploy does not run the suite - [ ] The existing CI browser job against the `built` target is unchanged
root commented 2026-10-09 09:19:58 +00:00 (Migrated from gitlab.core-project.space)

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

> _GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links)._ <!-- github-relations --> - Parent (sub-issue of): #303 - Blocked by: #306, #305
root (Migrated from gitlab.core-project.space) closed this issue 2026-10-09 12:20:44 +00:00
root commented 2026-10-13 08:41:06 +00:00 (Migrated from gitlab.core-project.space)

mentioned in issue #305

mentioned in issue #305
root commented 2026-10-13 08:41:06 +00:00 (Migrated from gitlab.core-project.space)

mentioned in issue #303

mentioned in issue #303
root commented 2026-10-13 08:41:07 +00:00 (Migrated from gitlab.core-project.space)

mentioned in issue #306

mentioned in issue #306
root commented 2026-10-13 08:42:07 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #303

marked this issue as related to #303
root commented 2026-10-13 08:42:09 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #305

marked this issue as related to #305
root commented 2026-10-13 08:42:10 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #306

marked this issue as related to #306
root commented 2026-10-13 10:28:28 +00:00 (Migrated from gitlab.core-project.space)

mentioned in commit 6d49970a4e

mentioned in commit 6d49970a4e075822b99813fae6af85e9e437eb0e
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
amaurycoudr/chess-project#308
No description provided.