Framework agnostic REST api testing
summary
Demos show creating and persisting WireMock mappings via record‑and‑replay into JSON files, using curl or the jar to stub endpoints, simulate fixed and random delays (examples: 2000 ms fixed, log‑normal distributions), inject errors, and use response templating to capitalize a captured path segment. Client behavior is validated with RestAssured while entire mocked services run inside Docker and JVM tests use TestContainers to start Postgres, seed data, manage ports and cleanup (Ryuk), proving isolated, repeatable REST tests without real services.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:56Why this session
- 2:12State of developer ecosystem
- 3:30Session focus
- 4:18Designed
- 7:48Open API
- 10:37Wiremock
- 12:07Record and map
- 16:07Request matching
- 19:37Mappings
- 21:47Mappings from scratch
- 24:29Why I like this
- 26:00Project overview
- 27:10Wiremock setup
- 27:52Groovy setup
- 30:27Request body
- 36:14Request path
- 38:27Modifying
- 39:09Offset
- 39:58Test Containers
- 44:00Security
- 45:27Postgres
related talks
31mModern Testing Tools for Java Developers
32mWiremock: because your microservice needs a buddy when you're testing
13mSpeed up writing tests with Wiremock Spring Boot
33mMock Me If You Can: Using Mocks in Container Applications for Integration Testing
41mAdvanced HTTP Mocking with
38mDoublers in Tests. Wiremock vs Mockito
57mModern Testing Tools for Java Developers
44mFake It until You Make It! API Integration Testing with Containers & WireMock