Raja Nagendra Kumar
Raja Nagendra Kumar
Is there a way to reduce the overhead as suite has substantially slowed.. however, did like that it is able to tell the methods that are slower than configured performance...
I see this hooking onto every test case. hence I see the report all these methods are not part of any suite as I am running zero suites in this...
com.tejasoft.tests.ju.ju5.ut.perf.noconnor.utils.JUnitPerfInterceptorSuite Currently all of them are hardcoded, love this to be configurable from gradle script ideally with noconnor gradle plugin Kindly ignore if my wishlist is too much..
``` public final class JUnitPerfInterceptorSuite extends JUnitPerfInterceptor { private static final HtmlReportGenerator REPORTER = newHtmlReporter("suite_reporter.html"); private static final DescriptiveStatisticsCalculator statisticsCalculator = new DescriptiveStatisticsCalculator(); @Override public void postProcessTestInstance(Object testInstance, ExtensionContext context)...

As these seem to be common for all, it is advised to move them out of the example module.
Does it support @Suite annotation of JUnit 5, rather than @RunWith as it is for JUnit 4
``` [INFO] Skipping JaCoCo execution due to missing execution data file. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.955 s [INFO] Finished at: 2023-06-01T11:07:03+05:30 [INFO] ------------------------------------------------------------------------ [WARNING]...
Any good compaision docuyment of this with https://github.com/authorjapps/zerocode - seems to be active and https://github.com/clarkware/junitperf - very old not sure if it still works, however I did use it in...
Directories should be selectable (browse & select), rather than they have to be typed now.  Package names can also browse and selectable  similar to what exists in application...