Using tparse for nicer CI test display

[oxisto]

Why didn't I notice this nice tool before?

[mfridman]

Hehe, we could also output to the GITHUB_STEP_SUMMARY variable (announced here).

https://github.com/mfridman/tparse/blob/main/.github/workflows/ci.yml#L32-L39

That way we see a nice summary and any failures. Can ignore the -slow 20.

Here is a sample of what that looks like (in addition to the CI logged output):

https://github.com/mfridman/tparse/actions/runs/2771562675#summary-7602716816

[oxisto]

Hehe, we could also output to the GITHUB_STEP_SUMMARY variable (announced here).

https://github.com/mfridman/tparse/blob/main/.github/workflows/ci.yml#L32-L39

That way we see a nice summary and any failures. Can ignore the -slow 20.

Here is a sample of what that looks like (in addition to the CI logged output):

https://github.com/mfridman/tparse/actions/runs/2771562675#summary-7602716816

Ah very cool! I can try to add that later.

[mfridman]

I can pick this up, did you want me to commandeer this PR?

[oxisto]

I can pick this up, did you want me to commandeer this PR?

Sure, go ahead.

[mfridman]

Before committing to a new /v5 api, I'd love if we could add a bit more coverage for some of the code paths. Wdyt?

No all of them, but the unhappy paths in the parser, the error contracts, etc.