Integration/compatibility layer with zeebe-process-test #316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new module,
engine
, which provides aZeebeTestEngine
implementation backed by either a container or a cluster.The implementations define idle/busy state based on the rate of records exported (idle being no records within a certain period, and busy being at least one record within a certain period). It also allows for a grace period to be defined, meaning one can omit calls to
ZeebeTestEngine#waitForIdleState(Duration)
(with some caveats).The main entry point of the module is the interface
ContainerEngine
, which extends bothStartable
andZeebeTestEngine
. By extendingStartable
, we can let the Testcontainers extension manage the lifecycle of our containers/engine.Additionally, the concrete implementations implement
TestLifecycleAware
, which allows us to do pre/post test tasks, such as initializing theBpmnAssert
record source, and printing out the log on failure.Pull Request Checklist
mvn clean install -DskipTests
locally before committing