Publish and view test reporting directly in your GitHub Actions CI/CD workflow and Pull Requests with detailed test summaries, failed test analyses, and flaky test detection.
When analysing a ctrf file to generate a report, there should be a way to exit with a non-zero exit code if failed tests have been found.
For now, it generates amazing reports and annotations, but does not actually bubble those failures up to the environment they are running in.
For example:
I have a test suite of 100 tests, and 1 test fails. That failure should cause the entire workflow to be marked as failed, but should still report the failure in a comment or in the summary.
This allows for CI runs that make testing a requirement for merging, imrproving overall automation of the CI stage of development
When analysing a ctrf file to generate a report, there should be a way to exit with a non-zero exit code if failed tests have been found.
For now, it generates amazing reports and annotations, but does not actually bubble those failures up to the environment they are running in.
For example:
I have a test suite of 100 tests, and 1 test fails. That failure should cause the entire workflow to be marked as failed, but should still report the failure in a comment or in the summary.
This allows for CI runs that make testing a requirement for merging, imrproving overall automation of the CI stage of development