MockServer 7.0.0 brings significant advancements, focusing on AI agent mocking, platform modernization, and enhanced resilience testing. This release marks a major step forward for API and mobile testing. For full details, refer to the MockServer 7.0.0 Release Notes.

Key Changes

LLM & AI Agent Mocking: The standout feature is the new LLM / AI-agent mocking suite. This provides provider-correct mock completions and streaming for seven major LLM providers (Anthropic, OpenAI, Gemini, Bedrock, Ollama). QA teams can now create multi-turn scripted conversations with per-session isolation and use a comprehensive MCP toolset for agent interactions, including mock_llm_completion, verify_tool_call, and explain_agent_run.

Platform Modernization & Performance: MockServer now supports HTTP/3 streaming responses, including SSE and chunked proxy forwarding. This release also raises the minimum runtime to Java 17 and completes a full Jakarta EE 10 / Servlet 6 migration, impacting dependencies like Spring, Tomcat, Jetty, and Netty. The Testcontainers library has been upgraded to 1.21.4. A new transparentProxyTproxy configuration property enables IP_TRANSPARENT socket binding for advanced transparent proxying on Linux.

Resilience & Scalability: An opt-in clustered MockServer state is introduced via the mockserver-state-infinispan module, allowing replication of expectations and scenario state across a JGroups cluster. For resilience testing, a general HTTP chaos/fault injection (HttpChaosProfile) can now be attached to any mocked or forwarded response, enabling MockServer to act as a chaos proxy. Agent resilience and correctness testing features include structured-output validation, a CI cost-budget gate, declarative LLM fault/chaos profiles, and VCR record/replay.

Security Enhancements: Released Docker images are now cosign-signed by digest, allowing consumers to verify image provenance. The documentation site (mock-server.com) has received website security hardening with new response headers and CAA records.

Impact for QA Teams

QA engineers gain powerful capabilities for testing AI-driven applications, simulating complex LLM interactions, and validating agent behavior. The ability to inject HTTP chaos and manage clustered state enhances testing of distributed systems and microservices, while the platform upgrades ensure compatibility with modern Java ecosystems.

FAQ

Q: What is the primary focus of MockServer 7.0.0? A: The primary focus is on first-class LLM/AI-agent mocking and a major platform modernization, including Java 17 and Jakarta EE 10.

Q: Can MockServer now simulate network issues for upstream services? A: Yes, the new HttpChaosProfile allows injecting probabilistic errors and latency into mocked or forwarded responses, making it useful as a chaos proxy.

Q: Is Java 17 a mandatory requirement for this version? A: Yes, MockServer 7.0.0 requires a minimum runtime of Java 17 due to platform modernization efforts.