For usage guide please see: www.mock-server.com
Please see: Change Log
| Chat |  |
| Feature Requests |  |
| Issues / Bugs | |
| Backlog |  |
Maven Central contains the following MockServer artifacts:
- mockserver-netty - an HTTP(S) web server that mocks and records requests and responses
- mockserver-netty:shaded - mockserver-netty (as above) with all dependencies embedded
- mockserver-war - a deployable WAR for mocking HTTP(S) responses (for any JEE web server)
- mockserver-proxy-war - a deployable WAR that records requests and responses (for any JEE web server)
- mockserver-maven-plugin - a maven plugin to start, stop and fork MockServer using maven
- mockserver-client-java - a Java client to communicate with both the server and the proxy
In addition MockServer SNAPSHOT artifacts can also be found on Sonatype.
NPM Registry contains the following module:
- mockserver-node - a Node.js module and Grunt plugin to start and stop MockServer
- mockserver-client-node - a Node.js client for both the MockServer and the proxy
Docker Hub contains the following artifacts:
- MockServer Docker Container - a Docker container containing the Netty MockServer and proxy
- MockServer Helm Chart - a Helm Chart that installs MockServer to a Kubernetes cluster, available versions:
- mockserver-client-ruby
- Ruby client for both the MockServer and the proxy
- mockserver-client-java - a Java client for both the MockServer and the proxy
- mockserver-client-node - a Node.js and browser client for both the MockServer and the proxy
- kotest-extensions-kotest - Kotlin Kotest integration with MockServer
If you have any problems, please check the project issues and avoid opening issues that have already been fixed. When you open an issue please provide the following information:
- MockServer version (i.e. 5.15.0)
- How your running the MockServer (i.e maven plugin, docker, etc)
- MockServer log output, at INFO level (or higher)
- What the error is
- What you are trying to do
Pull requests are, of course, very welcome! Please read our contributing to the project guide first. Then head over to the open issues to see what we need help with. Make sure you let us know if you intend to work on something. Also check out
Feature requests are submitted to github issues. Once accepted they will be added to the backlog. Please check out