Post one bot comment with screenshots, failed tests and coverage #497

Closed
opened 2026-10-21 10:07:09 +00:00 by root · 7 comments
root commented 2026-10-21 10:07:09 +00:00 (Migrated from gitlab.core-project.space)

Parent

#489

What to build

A reviewer sees a run's result on the pull request itself: one bot comment, updated on each run rather than posted again, holding the preview's screenshots, the tests that failed in checks, front-test and e2e, and the engine's statement coverage. It replaces GitLab's test widget and coverage report. A job that only reads the other jobs' reports posts it, with the bot's comment token, which no other job references.

Seam: a Forgejo Actions run (spec ## Seams).

Acceptance criteria

  • A pull request carries exactly one bot comment, however many runs it has had.
  • A failed test is named in the comment with its job.
  • The engine's coverage percentage appears, shown and never enforced.
  • The screenshots appear when a preview was deployed, and the comment still posts when none was.
  • The posting job runs none of the pull request's code and accepts only the expected files.
## Parent #489 ## What to build A reviewer sees a run's result on the pull request itself: one bot comment, updated on each run rather than posted again, holding the preview's screenshots, the tests that failed in `checks`, `front-test` and `e2e`, and the engine's statement coverage. It replaces GitLab's test widget and coverage report. A job that only reads the other jobs' reports posts it, with the bot's comment token, which no other job references. Seam: a Forgejo Actions run (spec `## Seams`). ## Acceptance criteria - [ ] A pull request carries exactly one bot comment, however many runs it has had. - [ ] A failed test is named in the comment with its job. - [ ] The engine's coverage percentage appears, shown and never enforced. - [ ] The screenshots appear when a preview was deployed, and the comment still posts when none was. - [ ] The posting job runs none of the pull request's code and accepts only the expected files.
root commented 2026-10-21 10:07:19 +00:00 (Migrated from gitlab.core-project.space)

mentioned in issue #498

mentioned in issue #498
root commented 2026-10-21 10:08:18 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #489

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

marked this issue as related to #495

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

marked this issue as related to #498

marked this issue as related to #498
root commented 2026-10-21 10:23:55 +00:00 (Migrated from gitlab.core-project.space)

mentioned in merge request !568

mentioned in merge request !568
root commented 2026-10-21 10:45:31 +00:00 (Migrated from gitlab.core-project.space)

mentioned in commit 9b8536f69a

mentioned in commit 9b8536f69a033ee948e74a97b3a255b1b2be4213
root commented 2026-10-22 09:46:37 +00:00 (Migrated from gitlab.core-project.space)

mentioned in commit 61d3258d7f

mentioned in commit 61d3258d7fb6eb796fd8a4f88f16729a1fcf3443
root (Migrated from gitlab.core-project.space) closed this issue 2026-10-22 09:54:51 +00:00
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#497
No description provided.