Nice integration with artifacts

[svrooij]

I just discovered some test library that integrates really well with github action artifacts.

In the GitHub summary they produce just a link to the artifact. And the artifacts opens a nice html overview.

Maybe we should make an opt-in to do just this with the Maester action?

[svrooij]

@SamErde and @merill what do you think about this?

[SamErde]

This should be the default way to see Maester results when it is run in GitHub Actions. I believe the GitHub summary should primarily surface information about the workflow run itself and just show a short summary of the test results.

[svrooij]

Or maybe just to summary table (with the number of tests run,skipped,...) in Github summary with a link to the report. But this report should then not rely on any external resources.

[SamErde]

Yes, exactly!

To clarify one thing, when you say, "not rely on any external resources," do you simply mean it should be a single self-contained HTML file? Actually, I think each run could still generate multiple artifacts: HTML, JSON, MD, etc -- but is that still what your comment refers to?

[svrooij]

Yes, exactly!

To clarify one thing, when you say, "not rely on any external resources," do you simply mean it should be a single self-contained HTML file? Actually, I think each run could still generate multiple artifacts: HTML, JSON, MD, etc -- but is that still what your comment refers to?

For it to work from artifacts it cannot access other resources as if you would publish it to a webserver.

So I mean 1 self contained html page with everything included. Can be next to the other files that are produced now.

[SamErde]

<ThisIsTheWay.gif>