Juraj Misur

Related to https://github.com/auth0/go-auth0/issues/14

I noticed that you are not running the report if there is no failure: https://github.com/micronaut-projects/micronaut-core/blob/6e2f1d1b180ed56b31590e609503468c3e7c2490/.github/workflows/gradle.yml#L43. Maybe that's the case. Otherwise it would overwrite previous report with success.

What I suggest is to decouple the test reporting from build process. So even if the build fails for any reason, you want to see the test reports (if any)...

It's preferable. Otherwise you don't know if the report matches the build. But of course rerun of the same commit shouldn't change anything (unless you have flaky tests).

I have the same problem, I think it's / it was github's bug. There is a [discussion in the community](https://github.community/t/github-actions-status-checks-created-on-incorrect-check-suite-id/16685) but I don't think it's solved yet.

There is no way to assign new check run to a specific check suite. Therefore it appears in a random suite. Updating any existing check run would I think override...

Hi @Vampire, This action does not support specs (yet). As a lot of reporters are misusing that XML report structure, we always need to adapt for new usages. For example...

As this is very foreign to me, a PR would be appreciated, or at least some form of description about how bats works, some examples of test reports and from...

Hey @jamie-wearsafe. I'm not really sure how does that work or what would it improve? Can you elaborate more on this?

I'm unable to find such functionality in [javascript core library](https://github.com/actions/toolkit/tree/main/packages/core) though.