[Improvement]: Summary in Github actions are hard to process for microservices

[jorgeparavicini]

Problem Statement

The summary that TUnit generates during GitHub Actions runs is great, but very hard to read when using microservices. With microservices, I mean we have a bunch of test projects that we all run with a single dotnet run command. The resulting summary looks like this:

This list just goes on and on. If one test fails, good luck finding the details ^^

Proposed Solution

Ideally, these individual groups are joined into one. So we would have one list of tests run, with how many were successful and how many failed, with a single detail list. Alternatively, one could change the display to match how the trx test reporter does it. Here is a screenshot for inspiration:

Alternatives Considered

No response

Feature Category

Test Output / Reporting

How important is this feature to you?

Nice to have - would improve my experience

Additional Context

No response

Contribution

• I'm willing to submit a pull request for this feature

[thomhurst]

Are you running tests via a solution file? Because if so that presents a challenge.

This would spawn new processes for each test suite, and one process is not aware of another, and so it's hard to get them to communicate and aggregate the data together.

[jorgeparavicini]

Yes we do :/

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.