Open ingorichtsmeier opened 3 years ago
I've added an unfinished branch (failing-rest-calls) with a new process and a wiremock setup to try some examples: https://github.com/camunda-community-hub/Make-Rest-Calls-From-Camunda-Example/tree/failing-rest-calls
As github.com provides a high availability web site that most likely will not fail or be not available, it is not perfect to show edge cases with your REST Calls.
REST request can fail for many reasons like server is down, network issues, content gets scrambled, response delays.
Wiremock has some built in features to simulate failures: http://wiremock.org/docs/simulating-faults/.
The faults need some API endpoints on a Wiremock http server, therefore different API endpoints than https://api.github.com.
How should Wiremock be integrated into this example?
One option would be to extract the called endpoints into configurable settings with smart defaults.
Another option would be to create other test processes that call wiremock endpoints. They can be used to react on single failures in a Unit test or even show a huge load on the process engine calling delayed service endpoints.
What do you prefer? One or two, even both or more options?