Affects Version/s: None
Fix Version/s: None
Siddharth Seth have noticed some odd timings in the jenkins reports
I've created a sample project, to emulate a clidriver run during qtest:
- 1 sec beforeclass
- 3x 0.2s test
created using junit4 parameterized.
Double checkout; second project runs different tests...or at least they have different name.
here are my preliminary findings:
- using 2.16 beforeclass timngs are totally hidden or lost
- 2.19.1 does account for beforeclass but still fails to correctly aggregate the two runs of the similary named testclasses
it might worth a try to look at the bleeding edge of this jenkins plugin...