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
We keep an array of mapped records in the engine agent, mostly because we reuse the RecordStreamSource. Instead the extension could open a long living stream to the engine, and push records out as they come in. We can register commit listeners to be notified of new records as they are appended. This would get rid of the more complicated way of reading records on demand, and no serialization needs to take place during assertion
The text was updated successfully, but these errors were encountered:
remcowesterhoud
changed the title
We keep a records array in the containerized engine, mostly because we reuse the RecordStreamSourceImpl. What if instead the extension just opened a long living stream to the engine, and it just pushed records out as they come in? You can register commit listeners to be notified of new records as they are appended, so you could just do that instead of having a more complicated way of reading records on demand. Happy to expand if that's not clear. The RecordStreamSourceImpl could then just be in the extension and wrap a plain list or the likes, and no serialization needs to take place during assertion
Stream records from the agent to the testcontainer extension
Apr 20, 2022
Heads up! We are building a new Java testing library for Camunda 8.6. The new library will replace Zeebe Process Test.
Read more about upcoming changes here and stay tuned for updates. 🚀
We keep an array of mapped records in the engine agent, mostly because we reuse the
RecordStreamSource
. Instead the extension could open a long living stream to the engine, and push records out as they come in. We can register commit listeners to be notified of new records as they are appended. This would get rid of the more complicated way of reading records on demand, and no serialization needs to take place during assertionThe text was updated successfully, but these errors were encountered: