Skip to content
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

Optional more granular reporting for JUnit reports #575

Open
tosky opened this issue Nov 19, 2024 · 0 comments
Open

Optional more granular reporting for JUnit reports #575

tosky opened this issue Nov 19, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request regression

Comments

@tosky
Copy link

tosky commented Nov 19, 2024

What would you like to be added:

#509 changed the format of the JUnit reports to be more granular. A statement at the end of the Caveats section says

If needed, I could add a knob to make this high-granularity opt-in.in the end

This request is about introducing such knob to allow people to use the previous, less granular reporting format.

Why is this needed:

This potential need was already highlighted in the commit which changed the format, as highlighted above. I'd like to add that in the project I contribute, OpenStack Kubernetes Operators, we are starting to collect the results of KUTTL tests in a consistent way for internal reporting. The way each operator structured its tests is to have to have a basic mapping of 1-1 between tests and features. We don't want nor need to mark each step for reporting. So instead of having to post-process the JUnitXML file, it would be nice if kuttl could produce also (with some flag) the report in the old format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request regression
Projects
None yet
Development

No branches or pull requests

2 participants