Use stronger assertion for Zeebe incident imports

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.7.0-alpha2, 3.7.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      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

            Assignee:
            Unassigned
            Reporter:
            Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: