Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Description
We typically use a standard error to simulate failures in engine/ES mockserver scenarios. However, it would make more sense to parameterize our failure scenario tests with various error types we might expected from the integrated service. An example would be how we now do for fetching engine authorizations on identity sync, as discussed in this PR: https://github.com/camunda/camunda-optimize/pull/2466#discussion_r467068579
ATs:
- We parameterize our failure scenarios for mockserver tests to test with various errors.