org.flowable.dmn.engine.test

Annotation Type FlowableDmnTest

@Target(value=TYPE)
 @Retention(value=RUNTIME)
 @Documented
 @Inherited
 @ExtendWith(value=FlowableDmnExtension.class)
public @interface FlowableDmnTest

Convenience for annotation that activates the FlowableDmnExtension JUnit Jupiter annotation.

Usage:

 @FlowableDmnTest
 class YourTest {

   @BeforeEach
   void setUp(DmnEngine dmnEngine) {
       ...
   }

   @Test
   void myTest(DmnRuleService dmnRuleService) {
       ...
   }

   ...
 }
 

The DmnEngine and the services will be made available to the test class through the parameter resolution (BeforeEach, AfterEach, test methods). The DmnEngine will be initialized by default with the flowable.dmn.cfg.xml resource on the classpath. To specify a different configuration file, annotate your class with DmnConfigurationResource. Dmn 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 dmn engine will be constructed.

You can declare a deployment with the DmnDeployment or DmnDeploymentAnnotation annotation. If both annotations are used then DmnDeployment takes precedence and DmnDeploymentAnnotation will be ignored. The extension will make sure that this deployment gets deployed before the setUp and DmnRepositoryService.deleteDeployment(String) cascade deleted after the tearDown. The id of the deployment can be accessed by using DmnDeploymentId in a test method.

FlowableDmnTestHelper.setCurrentTime(Instant) can be used to set the current time used by the dmn 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. 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