Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
Previously we made weak assertions for our Zeebe Incident Importing ITs. This was because of how we created incidents in our tests resulting in unexpected documents being exported. However, it turned out to be an issue in how Optimize resolves them rather than how Zeebe creates them, and can be remedied with the changes described here: https://github.com/camunda-cloud/zeebe/issues/8089
We should implement the suggested changes and use stronger assertions in our tests