-
Notifications
You must be signed in to change notification settings - Fork 195
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
Investigate the test reporter with github action #4944
Comments
This is something I have wanted for a long time. I looked into it a long time ago. It's a bit tricky to implement, because our build is broken into so many different steps.... |
Yeah, maby we can take a look what the quarkus bot is doing this work. |
@jamesnetherton @zhfeng is anyone already started working on this ? If not I would like to help, thanks! |
Thanks for taking a look at this one! |
I can try to move this forward. We can keep things simple and generate a summary from the JUnit XML files after tests have completed on each job. There's a POC of what it'd look like on my fork: https://github.com/jamesnetherton/camel-quarkus/actions/runs/8897198115#summary-24432612744 |
Added an initial step for this in #6076. I will try to improve it over time. |
Currently it is hard to find the failing tests in by scrolling the CI building logs. I think if we can find a test reporter action to hightlight the failing tests, that could be very helpful. It needs to report from the surefire and failsafe test log files.
The text was updated successfully, but these errors were encountered: