All Classes and Interfaces
Class
Description
Abstract superclass for JUnit 5 based test cases.
Abstract superclass for test cases.
Strategy for boundary conditional, message and signal events.
Strategy for boundary timer events.
Custom BPMN parse listener that:
1.
1.
Plugin to configure a BPMN Driven Testing conform process engine, used to execute generated test cases.
Builds a new test case context, used for code generation.
Represents a concrete call activity during test case execution.
Fluent API to handle call activities.
Collects the paths of all BPMN files within the project's resource directory (
src/main/resources).Please note: This constants cannot be used within the API classes nor within the generated test
code, since this class will not be available in the test classpath of the target project.
Default strategy for all handled activities, that provide a fluent handler API.
Default strategy, used for all unhandled activities (with type
TestCaseActivityType.OTHER).Fluent API to handle conditional, message and signal intermediate catch or boundary events.
Please note: Since conditional events rely on an expression to evaluate true, their wait state cannot be handled automatically - set variables or use
Please note: Since conditional events rely on an expression to evaluate true, their wait state cannot be handled automatically - set variables or use
EventHandler.execute(Consumer) with a custom action, if the variable
event is delete.Fluent API to handle external tasks.
Generates the handler for a given multi instance activity.
Generates a Spring test configuration, which is required for Spring based test code.
Generates a test case, using a test framework (JUnit 4 or 5) specific superclass.
Class that is responsible for generating test code and writing the generated files to the test source directory.
Class, used to collect the test code generation results.
Strategy, used per activity when generating a test case.
Function that provides the strategies of all activities, including scopes, that are on the same nesting level during execution.
Fluent API to handle jobs (asynchronous continuation and timer catch events).
Possible job cardinalities.
Fluent API for multi instance activities (call activities or tasks).
Fluent API for multi instance scopes (sub processes or transactions).
Special strategy for multi instance scopes.
Special strategy for activities that are enclosed by the multi instance scope.
Spring test configuration, used as superclass for the generated configuration.
If data source and/or transaction manager are not provided by the application context, this configuration will initialize and provide them to the process engine configuration.
Moreover, if the application context provides a list of process engine plugins, this list will be preferred in favor of the process engine plugins that are configured on the Maven plugin execution - see parameter
If data source and/or transaction manager are not provided by the application context, this configuration will initialize and provide them to the process engine configuration.
Moreover, if the application context provides a list of process engine plugins, this list will be preferred in favor of the process engine plugins that are configured on the Maven plugin execution - see parameter
processEnginePlugins.Fluent API to prepare and start the actual test case execution.
Link between test case, and its execution, utilizing a process instance that was instantiated by a
TestCaseExecutor and handlers (e.g.Fluent API to handle user tasks.