MockServer 7.1.0: Response Verification & Advanced Breakpoints

MockServer 7.1.0 Release Overview #

MockServer 7.1.0, released on 2026-06-15, introduces significant enhancements for API and Mobile Testing, focusing on deeper verification capabilities and advanced debugging with breakpoints.

Key Changes #

Verification Enhancements The primary update in verification allows QA engineers to now verify responses received from proxied or forwarded systems. Previously, verification focused solely on the request. With 7.1.0, you can add an httpResponse matcher to your verification calls (PUT /mockserver/verify). This enables matching against status code, headers, body (JSON, XML, regex, etc.), and reason phrase. When httpRequest is also present, both must match. verifySequence also gains an httpResponses list for ordered response assertions. This expands the scope of what can be asserted, providing more control over end-to-end flow validation.

Advanced Breakpoints & Request Replay MockServer 7.1.0 transforms breakpoint management. Breakpoints are no longer global flags but are now matcher-driven. You register a request matcher (PUT /mockserver/breakpoint/matcher) along with specific phases (REQUEST, RESPONSE, RESPONSE_STREAM, INBOUND_STREAM) to pause at. This allows for granular control over when and where an exchange pauses.

Interactive resolution of these breakpoints occurs over the callback WebSocket, requiring a clientId for registration. This enables clients (including the dashboard) to receive paused exchanges and interactively decide to modify, continue, or abort them. This applies to standard requests/responses and extends to per-frame streaming breakpoints across various protocols like SSE, HTTP/3 gRPC, and WebSockets.

Client APIs for Java, Node, Python, and Ruby have been updated to support these new breakpoint features. The Java client, for instance, offers MockServerClient.addBreakpoint(matcher, phases…, handlers…) with typed handlers for each phase, allowing specific logic for request, response, or stream frame handling. Each breakpoint routes to its own handler via a X-MockServer-BreakpointId header.

For more details, refer to the official MockServer 7.1.0 changelog.

Impact for QA Teams #

These updates provide QA teams with more precise control over API testing and debugging. The ability to verify responses directly improves assertion accuracy for proxied services. Advanced, matcher-driven breakpoints simplify complex debugging scenarios, allowing testers to inspect and manipulate traffic at specific points interactively, accelerating root cause analysis.