noconnor

Try using ‘totalExecutions’ to run each test for a fix number of iterations instead of for a fixed ‘durationMs’ You could also look into running tests in parallel https://junit.org/junit5/docs/current/user-guide/#writing-tests-parallel-execution

You should not need all this template code anymore with version 1.30.0 You can look at the test [suite example code](https://github.com/noconnor/JUnitPerf/blob/master/junit5-examples/src/test/java/com/github/noconnor/junitperf/examples/ExampleTestSuiteUsage.java) to see how to configure suites with 1.30.0+

Spotted an issue with reflection and method access thats fixed now with 1.31.0, so you might want to upgrade to that. > I just wish to run the normal junit...

You could also look at adding `@ExcludeClassNamePatterns` or `@ExcludePackages` to explicitly exclude `TestBBSuites` and `TestSuiteEx` from the perf test suite

That error is **not** coming from the junitperf framework, its coming from the junit suite engine (i.e. `org.junit.platform.suite.engine.SuiteTestDescriptor`): ``` org.junit.platform.suite.engine.NoTestsDiscoveredException: Suite [com.tejasoft.tests.ju.ju5.ut.suites.TestBBSuites] did not discover any tests at org.junit.platform.suite.engine.SuiteTestDescriptor.computeTestExecutionResult(SuiteTestDescriptor.java:134) at...

If you add `@JUnitPerfTestRequirement` to the test suite the default values for this annotation will be used to validate the test results. Default values are documented [here](https://github.com/noconnor/JUnitPerf#test-configuration-options) The default behaviour...

I misspoke, the default behaviour is to expect no errors (whether or not the `@JUnitPerfTestRequirement` annotation is present). You can enable trace logging on `EvaluationTask` to identify the source of...

The results state that: * there were 10 invocations of `testWithdrawalWithSufficientBalanceAndAccess` * 1 of those invocations had no errors i.e see `success` (no assertions within the test method failed) *...

if this test requires an @BeforeEach to be executed before each performance test invocation you'll need to update to 1.33.0

I'll look into adding support to skip tests that fail Assumptions