noconnor

Will add a fix this week, but for now if you comment out [this line](https://github.com/noconnor/JUnitPerf/blob/master/junit5-examples/pom.xml#L40) and run `mvn test` the example tests should run. The example tests include some failure...

if error count == evaluation count, it suggests that each call to `testWritePerformanceOneThread` is generating an exception. For debugging you can enable trace logging for the `com.github.noconnor.junitperf` package (how to...

You would need to enable the TRACE level logging for the `com.github.noconnor.junitperf` package to understand what error is being thrown. If you can get that logging, particularly for the [EvaluationTask](https://github.com/noconnor/JUnitPerf/blob/master/junitperf-core/src/main/java/com/github/noconnor/junitperf/statements/EvaluationTask.java)...

> logback.xml) on debug level for the JUnitPerf to show on console You need to set the logging to TRACE (not debug) for junitperf package

This seems to be the issue you are having: ``` org.junit.internal.runners.model.MultipleFailureException: There were 2 errors: org.jboss.weld.contexts.ContextNotActiveException(WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped) java.lang.NullPointerException(null) at org.junit.runners.model.MultipleFailureException.assertEmpty(MultipleFailureException.java:67) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:39) ``` And...

So when the `@Rule` is in place, the `before`, `test` and `after` will be executed in a loop 2000 times (ie `totalExecutions` number of times) Is there any code in...

It also might be worth mentioning that the test will be executed on a new thread. This stack overflow entry suggests the error you are seeing might be threading related...

You could use @BeforeClass and @AfterClass https://junit.org/junit4/javadoc/4.12/org/junit/BeforeClass.html https://junit.org/junit4/javadoc/4.12/org/junit/AfterClass.html

Again , this [post](https://stackoverflow.com/a/46538520) seems to suggest the issue you are having is threading related Junitperf tests will be executed in on a [thread separate](https://github.com/noconnor/JUnitPerf/blob/master/junitperf-core/src/main/java/com/github/noconnor/junitperf/statements/PerformanceEvaluationStatement.java#L59) to the thread that initialises...

This is just a trace log indicating that there was a failure in the test `TestBAWMock.java` at line 66 during the warm up phase : `Actually, there were zero interactions...