Download as PDF, PPTX
![<david.schmitz@senacor.com>
How does it work?
Client Wiremock
Request
Mapping
Response
Data
body.json:
[{"publicId":"...","data":"..."},
{"publicId":"...","data":"..."}]](https://image.slidesharecdn.com/resiliencetestingwithwiremock-160322164036/85/Resilience-testing-with-Wiremock-and-Spock-10-320.jpg)
![<david.schmitz@senacor.com>
…but what about bad responses?
Client Service
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
[300 MB of random garbage]
GET http://service/resource/12](https://image.slidesharecdn.com/resiliencetestingwithwiremock-160322164036/85/Resilience-testing-with-Wiremock-and-Spock-18-320.jpg)
![<david.schmitz@senacor.com>
How does it work?
Client Wiremock
Request
Mapping
Response
Data
body.json:
[{"publicId":"...","data":"..."},
{"publicId":"...","data":"..."}]](https://image.slidesharecdn.com/resiliencetestingwithwiremock-160322164036/75/Resilience-testing-with-Wiremock-and-Spock-10-2048.jpg)
![<david.schmitz@senacor.com>
…but what about bad responses?
Client Service
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
[300 MB of random garbage]
GET http://service/resource/12](https://image.slidesharecdn.com/resiliencetestingwithwiremock-160322164036/75/Resilience-testing-with-Wiremock-and-Spock-18-2048.jpg)
Uploaded byDavid Schmitz
Resilience testing with Wiremock and Spock
The document discusses the use of WireMock for effective REST testing, emphasizing the importance of testing both happy and not-so-happy paths in software systems. It outlines WireMock's features, such as stubbing, request verification, fault injection, and how it operates as an embedded server. The summary concludes by stressing the necessity of testing resilience and unexpected behaviors, as well as utilizing record and playback functionalities for external service interactions.
More Related Content
Similar to Resilience testing with Wiremock and Spock
Resilience testing with Wiremock and Spock
- 1. <david.schmitz@senacor.com> Resilient Services withWiremock Effective REST tests using Wiremock and Spock https://flic.kr/p/orejhX
- 2. <david.schmitz@senacor.com> How does yoursystem handle failures?
- 3. <david.schmitz@senacor.com> Everybody tests thehappy path… https://flic.kr/p/9MHEme
- 4. <david.schmitz@senacor.com> Happy Path Tests HTTP/1.1200 OK {“publicId":"42634558","data":"foo"} GET http://service/resource/12 Client Service
- 5. <david.schmitz@senacor.com> But what aboutthe not-so-happy path? https://flic.kr/p/CSnr1
- 6. <david.schmitz@senacor.com> Enter Wiremock • Stuband Mock framework for testing HTTP(s) traffic • Features include • Request verification, • record, playback, • fault injection, • unit test and stand alone Client Unit Test Embedded Wiremock Client Standalone Wiremock
- 7. <david.schmitz@senacor.com> How does itwork? Client Wiremock Request Mapping Response Data $ curl -H ‘Accept: application/json’ http://localhost:8080/sample/
- 8. <david.schmitz@senacor.com> How does itwork? Client Wiremock Request Mapping Response Data • Starts embedded Jetty Server • Acts as a proxy to the actual service • Is used by the client transparently
- 9. <david.schmitz@senacor.com> How does itwork? Client Wiremock Request Mapping Response Data "request" : { "url" : "/sample/", "method" : "GET", } } }, "response" : { "status" : 200, "bodyFileName" : "body.json", "headers" : { "Content-Type" : “application/json" … } }
- 10. <david.schmitz@senacor.com> How does itwork? Client Wiremock Request Mapping Response Data body.json: [{"publicId":"...","data":"..."}, {"publicId":"...","data":"..."}]
- 11. <david.schmitz@senacor.com> Creating a WiremockUnittest Prepare Stub Configure Wiremock Consume REST service
- 12. <david.schmitz@senacor.com> Creating a WiremockUnittest Prepare Stub Configure Wiremock Consume REST service
- 13. <david.schmitz@senacor.com> Creating a WiremockUnittest Prepare Stub Configure Wiremock Consume REST service
- 14. <david.schmitz@senacor.com> Creating a WiremockUnittest Prepare Stub Configure Wiremock Consume REST service
- 15. <david.schmitz@senacor.com> Creating a WiremockUnittest Prepare Stub Configure Wiremock Consume REST service
- 16. <david.schmitz@senacor.com> …but what aboutfailures? HTTP/1.1 503 Service Unavailable Client Service GET http://service/resource/12
- 17.
- 18. <david.schmitz@senacor.com> …but what aboutbad responses? Client Service HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 [300 MB of random garbage] GET http://service/resource/12
- 19.
- 20. <david.schmitz@senacor.com> …but what abouttimeouts? java.net.SocketTimeoutException: Read timed out Client Service GET http://service/resource/12
- 21.
- 22.
- 23. <david.schmitz@senacor.com> Record and Playback Runrequests Start Wiremock in record mode Start Wiremock in playback mode
- 24.
- 25. <david.schmitz@senacor.com> Summary • Resilience canbe tested • Do not rely on happy paths and mocks only • Use stubs and verify in unit tests • Use record and playback for external services • Make sure not to be the developer responsible for a downtime during the busy-business-time :D
- 26.
- 27.
- 28.
- 29. <david.schmitz@senacor.com> Testing a Client ClientUnit Test Embedded Wiremock