Raja Nagendra Kumar
Raja Nagendra Kumar
>I think you should have 186 results in the junitperf report but i can see you only have 134. >i think some test names are clashing and the html reporter...
> I think whats happing is you are running all your tests and then running a suite class annotated with @JUnitPerf that re-runs all your tests , so you run...
> , the test method is run in a loop by the `junitperf` framework. > > That is the only way to run a method multiple times. Does this mean...
>Yes. Junit calls the junitperf interceptor. JUnit calls JUnitPerf Once > The interceptor calls the test as many times as it can in 60secs. JUnitPerf is calling this method approx...
> If you can run with that version when you get a chance and attach the junit report zip with full details again that would be helpful in troubleshooting. [reports.zip](https://github.com/noconnor/JUnitPerf/files/11925634/reports.zip)...
> * junitperf run: loop (beforeEach -> method -> afterEach) -> **next test** JUnitPerf waits for the `next test` that should be triggered by junit? > **junitperf run: loop** (beforeEach...
> Looks like these tests are missing from the report: These are the tests that have different engines such as to run JUnit 4 and 3 part of` JUnit 5...
4. Size of these html files are too huge, that way browsers and IDEs are unable to show or open graphs are not shown
Also download as CSV (may be a name of performance timing report can be a better name) is showing 100 iterations
The label Latency in y-axis can say the unit as ms, though the tooltip is any way giving that as ms (Milliseconds)