WireMock is a simulator for HTTP APIs that allows testing applications that depend on external APIs without needing the real APIs to exist or be implemented. It works by replacing HTTP APIs during testing in a transparent way. Some key advantages of WireMock over traditional mocking include that it does not require modifying application code and can simulate APIs in realistic ways by configuring stub responses. WireMock can run as a standalone process or be embedded within tests to simulate APIs through JSON mappings and reliably test scenarios, edge cases, and faults in applications that integrate with external HTTP APIs.

1. WIREMOCK
Presented by CHAABA Ayoub
Software Testing & Verification

3. What is WireMock?

4. Mocking?
Something that doesn’t exist
in real or not developed yet
but we still want to use it

5. Stubbing/Stub?
IS a simple fake object. It
just makes sure test runs
smoothly.

6. Problem That
Arises
How do we reliably test
applications that depend on APIs
which we do not own or do not
exist?

7. Java-based simulator for HTTP APIs
Helps us test specific scenarios, edge-case &
faults
Can run as a Standalone Process or
embedded .
Allows us to reliably simulate the HTTP
dependencies of our application under test

8. How WireMocks fits into
your architecture during
testing
?

14. Common use cases for
WireMock

17. Advantages of WireMock
over Mocking

20. Demo Using WireMock as
Standalone server

22. Two folder named mapping and __files were created . In the __file folder you can simply put
folder and files, which your server will serve when called with a GET request.
In the mappings folder you can setup more advanced mocking behaviors(stub responses).

23. Configuring via JSON over HTTP (STUBBING VIA REST API STRING BODY)

24. Test With HTTP Client Insomnia

25. POST Test with HTTP client directly

26. GET Test with HTTP client directly

27. When there is no stub response

28. Creation Of JSON in mappings folder
N.B: mappings folder its just another word for mocked responses

29. Stubbing Via REST API JSON Response

30. Stubbing Via REST API JSON Response Using HTTP Client Insomnia

31. Demo Running WireMock
with JUnit

37. Demo OF Integration
Tests with WireMock
Springboot & T.D.D in a
Microservices
Architecture

38. TDD test before implementing the class

39. RestController +Request to not existing API+Test of calling the API

40. TEST FAILED

41. Solution: ADD WireMock dependency in
Gradle or Maven

46. Summary

47. Testing can be challenging when working
with external HTTP APIs
It works by transparently replacing HTTP APIs
during testing as in production environment.
It is advantageous over mocking as it
does not replace your application code.
WireMock is a simulator for HTTP APIs that
makes testing the applications that depend on
them easier

48. Thank You For
Your Attention