Dependencies

QuickPerf test

Dynamic Tests

Project examples

JUnit 5 >= 5.6.0 is required

You can use JUnit 5 and QuickPerf BOM files.

In the case of Maven, you can add the following dependency management:

The following JUnit 5 dependencies are required:

If you get a java.lang.NoClassDefFoundError: org/junit/platform/launcher/core/LauncherDiscoveryRequestBuilder, then the junit-platform-launcher dependency is missing.

You also need the following QuickPerf dependency:

You can now use the core and JVM annotations, except the JVM profiling annotations, by transforming the test class into a QuickPerf test class (see just below).

Want to use SQL annotations with Spring? Please read this.

A QuickPerf test executes QuickPerf annotations. With JUnit 5, you can transform your tests into QuickPerf tests in two ways.

Add @QuickPerfTest on the test classes.

JUnit 5 can automatically register QuickPerf extension. So, with this mechanism, you don't have to add QuickPerfTest annotation on the test methods.

To enable the automatic extension registering, add a junit-platform.properties file in src/test/resources. After that, add the following line to this file:

With JUnit 5, you can define a test method that generates other tests. This particular method is a test factory, creating dynamic tests.

You can use Quickperf annotations on test factory methods, be aware that in this case, the annotation applies to all dynamic tests created by the test factory method, not on the test factory method on itself.

The following example will fail:

The @ExpectSelect(2) annotation will apply to both dynamic tests; as each generates only one query, you will have two failures (one for each test). The correct usage would have been @ExpectSelect(1).

JVM & JUnit 5

Hibernate & JUnit 5

Spring Boot & JUnit 5

Spring Boot & JUnit 5 & Testcontainers

Micronaut & Hibernate

Micronaut Data

Quarkus