MockServer is flexible and support numerous usage patterns.

MockServer can be run:

• programmatically via a Java API in an @Before or @After method
• using a JUnit 4 @Rule via a @Rule annotated field in a JUnit 4 test
• using a JUnit 5 Test Extension via a @ExtendWith annotated JUnit 5 class
• using a Spring Test Execution Listener via a @MockServerTest annotated test class
• as a Docker container in any Docker enabled environment
• via a Helm chart in any Kubernetes environment
• from the command line as a stand-alone process in a test environment
• via a Maven Plugin as part of a Maven build cycle
• as a Node.js (npm) module from any Node.js code
• as a Grunt plugin as part of a Grunt build cycle
• as a deployable WAR to an existing application server

To simplify configuration all versions (except the deployable WAR) use a single port to support the control plane and data plane in HTTP, HTTPS or SOCKS.

MockServer is available in the following formats:

• java dependency
• Docker container
• Helm chart for Kubernetes
• executable jar
• Homebrew package
• maven plugin
• npm plugin
• Grunt plugin
• deployable WAR that runs on JEE web servers

It is also possible to build and run MockServer directly from source code

MockServer UI:

MockServer has a UI that can be used to view the internal state within MockServer, including:

• logs
• active expectations
• requests received
• proxied requests