You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When testing Zeebe itself with this library, sometimes a bug will occur in one of the containers, and it's hard to reproduce locally. Having the state would allow one to restart with the same log/state and more easily reproduce certain class of bugs in a local JVM.
This is already possible, but requires some wiring together of the various components and reacting on test failure.
Describe the solution you'd like
Add a flag to the broker nodes, which accepts a local path where the state should be saved on failure. Implement TestLifecycleAware on the broker nodes, and save the state on failure when applicable.
Describe alternatives you've considered
Let users manually come up with it; possibly add documentation and an example test to showcase this.
The text was updated successfully, but these errors were encountered:
npepinpe
changed the title
Add a Junit 5 extension to automatically save the broker state
Add option to automatically save the broker state on failure
Sep 26, 2022
Is your feature request related to a problem? Please describe.
When testing Zeebe itself with this library, sometimes a bug will occur in one of the containers, and it's hard to reproduce locally. Having the state would allow one to restart with the same log/state and more easily reproduce certain class of bugs in a local JVM.
This is already possible, but requires some wiring together of the various components and reacting on test failure.
Describe the solution you'd like
Add a flag to the broker nodes, which accepts a local path where the state should be saved on failure. Implement
TestLifecycleAware
on the broker nodes, and save the state on failure when applicable.Describe alternatives you've considered
Let users manually come up with it; possibly add documentation and an example test to showcase this.
The text was updated successfully, but these errors were encountered: