@Target(TYPE) @Retention(RUNTIME) @Documented @Inherited @ExtendWith(FlowableCmmnExtension.class) public @interface FlowableCmmnTest

Convenience for annotation that activates the FlowableCmmnExtension JUnit Jupiter annotation.

Usage:

 @FlowableCmmnTest
 class YourTest {

   @BeforeEach
   void setUp(CmmnEngine cmmnEngine) {
       ...
   }

   @Test
   void myTest(CmmnRuntimeService runtimeService) {
       ...
   }

   ...
 }

The CmmnEngine and the services will be made available to the test class through the parameter resolution (BeforeEach, AfterEach, test methods). The CmmnEngine will be initialized by default with the flowable.cmmn.cfg.xml resource on the classpath. To specify a different configuration file, annotate your class with CmmnConfigurationResource. Cmmn engines will be cached as part of the JUnit Jupiter Extension context. Right before the first time the setUp is called for a given configuration resource, the cmmn engine will be constructed.

You can declare a deployment with the CmmnDeployment annotation. The extension will make sure that this deployment gets deployed before the setUp and cascade deleted after the tearDown. The id of the deployment can be accessed by using CmmnDeploymentId in a test method.

can be used to set the current time used by the cmmn engine This can be handy to control the exact time that is used by the engine in order to verify e.g. e.g. due dates of timers. Or start, end and duration times in the history service. In the tearDown, the internal clock will automatically be reset to use the current system time rather then the time that was set during a test method.

Author:: Filip Hrisafov

Annotation Interface FlowableCmmnTest