Test history refactoring and improvements #446
Conversation
you should just be able to open them in a Java IDE and put breakpoints in and run the test in debug mode. Nothing special required in this project |
Can VS Code do this? I tried putting some breakpoints and pressing F5 but it does nothing. What IDE do you use? Ok, I guess I will go back to Eclipse once again (after 10 years break). |
|
I (and most other Java developers) use IntelliJ. Eclipse should work but I haven't touched it in ~8 years so couldn't say. VS Code should be able but I've never tried. |
|
Thanks, after trying around a bunch of times, I settled on IntelliJ. |
More logging. Parallel history stream.
… tests. Add timeout and build count limit.
Reduce trend chart loading times. Display same count of builds in trend chart as in table. Workaround for jQuery issue.
Support decimal duration. Increase builds in view to 100.
Round maximum up if over 0.5.
Reuse the retrieved history for chart generator to avoid multiple requests.
Fix click on chart.
…it goofy). Improve chart appearance. Show both charts.
Add history size links. Improve history page load time.
Add Total line. More distinct line colors. Improve overall appearance.
Increase age computation window to 25 to skip over builds without results.
Fix test compilation error. Update POM.
Fix history chart layout with only few results.
mdealer
force-pushed
the
no-stage-name-in-test-name-junit-1.63
branch
from
5e719aa to
bbb187c
Compare
…d suites. Fix potential crash in history chart.
|
Updated via #625 |
See https://github.com/mdealer/junit-plugin/releases/tag/junit-1.63.2-refactor-test-history
TL;DR:
TODOs:
Some guidance on what is the best way to debug the automated tests without resorting to logging (that would take ages) would be helpful. Based on continuous live/production usage on our side, it works.
Live 'tested' with multibranch and plain pipeline jobs with JUnit and TestNG test reports. Newer versions of xUnit seem to have issues due to this being based on the older junit-plugin 1.63