-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have tests grouped by suite in summary #1080
Comments
Looking at action-junit-report/src/testParser.ts Lines 226 to 236 in 9379f0c
suite_regex to '*' ?
|
to
Which is more information, but unsure if it's actually nicer. |
Ah, I didn't notice that. It doesn't really improve things from a UX perspective. I'd prefer to be able to have grouping. |
thank you very much for the ticket. That's quite a good idea. Would you also have a proposal on how to format it. E.g. all in one table with headers in-between or individual table per group? |
I'm far from a UX expert, but maybe:
The summary table could possibly be switched on/off by configuration. Something super-funky would generate a table with a row per suite, that folds out when clicked on it maybe. That might be not one, but two bridges to far for now though. |
This would be great. Agree with guusdk's suggested format. |
- simplify code significantly allowing for easier iterations and refactors in the future - retain testSuite / testCase hierarchy to enable the ability to implement requirements as noted in #1080, #1086 - deprecate `suiteRegex` and replace with more appropriate `check_title_template` definition - introduce new template for breadcrumb - update and enhance test-cases for new structure
While this does not yet support your requirement, I started refactoring the action to enable the new Furthermore does this refactor lay the foundation to enable a more structured report in the future. I don't have an ETA yet, however I do think that with the latest changes the possibility comes closer :D |
My test result is a one-file XML structure, that consists of one test-suite, in which sub-suites are nested:
Although not shown here, a testcases from the same suite do not necessarily share the same classname.
The test summary, as generated by this Action, seems to aggregate tests from all suites, as shown below. For my use-case, having the tests grouped by suite would add significant value. Is there a way to have the test summary group results by suite?
caveat: the XML file that is producing these results is a hand-crafted file. Apologies if I'm asking a question that's already supported, but not working properly in my setup, because of that.
The text was updated successfully, but these errors were encountered: