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
It would be so much helpful if we have timings from the beginning of tests (or just timestamps of the records) in the io.camunda.zeebe.process.test.filters.logger.RecordStreamLogger#logGenericRecord. It could help in different scenarios, where could be race conditions, too much waiting, etc.
The text was updated successfully, but these errors were encountered:
We should consider if we need this in all test outputs. Perhaps it could be enabled through configuration somehow. If it is useful in most cases, we could make it the default behavior.
Our current priority for this is: later. We see value in it, but it is not critical for us to work on now.
@aivinog1 Would you be willing to contribute to this? If so, please consider how we could add a configuration for this.
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. 🚀
Description
Hello 👋
It would be so much helpful if we have timings from the beginning of tests (or just timestamps of the records) in the
io.camunda.zeebe.process.test.filters.logger.RecordStreamLogger#logGenericRecord
. It could help in different scenarios, where could be race conditions, too much waiting, etc.The text was updated successfully, but these errors were encountered: