5 ms·
My personal wish is for the ability to attach HTML reports the the action runs without having to use the current actions/upload-artifact etc. Particularly for
by giobox 3y ago
My personal wish is for the ability to attach HTML reports the the action runs without having to use the current actions/upload-artifact etc.
Particularly for test builds, I very often just want to quickly view the output HTML report. The current approaches I am familiar with are the aforementioned upload-artifact, or using GH pages, but GH pages is not great when you have multiple different reporting output for the same repo, or you wanna quickly view historical reporting rather than latest.
I'd love a simple "attach-report" action that just put a link to an HTML report on the job summary, and clicking on it renders the html.
Other automated CI/CD style systems have much richer support out of the box for dealing with HTML report capturing and viewing.
- dmart 3y agoGranted, it's not HTML, but you can append Markdown output directly to $GITHUB_STEP_SUMMARY without dealing with artifact uploads etc.
- giobox 3y agoThanks, I'm aware of this option too, but if you say have an HTML report with the results of 200 tests, no one has time to write some logic to parse the results to a markdown summary frankly. Just give me the link! Similar too if the reporting captures video/screenshots of a given bug - the original report UI is far easier to deal with. Many test frameworks already natively put out an HTML report UI etc, it's just harder to get to than it should be with GH actions today.
- pests 3y ago> an HTML report with the results of 200 tests, no one has time to write some logic to parse the results to a markdown summary frankly. Not sure how GHA treats it, but markdown is a subset of HTML so by default all HTML pages are valid Markdown documents. No conversion required.
- Aeolun 3y agoThey just don’t show half of the stuff inside correctly.
- deleted 3y ago[deleted]