ctrf-io / ctrf-io/github-test-reporter
Feature Request: better support for multiple reports on the same PR
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 376
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for this action! Love the flexibility, it's awesome 🙌🏽
I run several test suites on PRs and am hoping for this behavior with comments:
- only 1 comment for all test suites, with 1 section per test suite
- each test suite overwrites its previous section within the comment
Maybe this could be achieved with something like:
- comment-tag: shared
- comment-section-tag: web | python | api
- overwrite-comment-section: true
End result: each test run updates the same comment on the PR, with each separate suite overwriting its section within that comment.
I am currently sort of hacking this by depending on the fact that one of my test suites usually finishes first, so that one passes overwrite-comment: true, and others pass update-comment: true. But this breaks down if we start handling retries of individual test suites
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing comment options, especially overwrite-comment and update-comment, and trace how reports from separate test suites are handled. Done means multiple suites share one pull-request comment, each owns a tagged section, and retries update only that suite's section without breaking the others.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100