Post test results in CI

[bruno-garcia]

Today test results are already parse:

It would be great if the results were posted either as an action, like:

From this workflow, in this build

Or even as a PR comment like codecov does for coverage. It's particularly useful when tests fail so if it can show something from failing tests like the first 10 log lines it would be useful. But worse case linking to the failing build would be helpful.

[Tyrrrz]

Woot how does that work. I've never seen that before.

[Tyrrrz]

Looks like this action is responsible for generating the report: https://github.com/axel-op/dart-package-analyzer
Trying to figure out how it does it...

Seems that the report itself is formatted as Markdown content:

https://github.com/axel-op/dart-package-analyzer/blob/d56ba070e9dcacc6d8ba48a41938b1e2b973de41/app/lib/github.dart#L58-L92

And the report seems to be published here:

https://github.com/axel-op/dart-package-analyzer/blob/d56ba070e9dcacc6d8ba48a41938b1e2b973de41/app/lib/github.dart#L203-L217

That in turn calls this API method:

https://docs.github.com/en/rest/reference/checks#update-a-check-run

Sounds doable, but I'm not too eager to implement this in PowerShell 😂
Can we do this when/if we migrate our workflow to a JavaScript GitHub action?

[bruno-garcia]

Can we do this when/if we migrate our workflow to a JavaScript GitHub action?

Sure, if that lives inside github.com/getsentry, no problem :)

Eager to have the workflow run on macOS too 🚀

[bitsandfoxes]

It is such the pain to go through the test results right now. I'm bumping the priority on this here since it's no new functionality that we'd have to build and it'd make our lives so much easier.

Does Codecov already have something for Unity tests?