jamesdbloom/mockserver repository overview

⁠MockServer               

mock server [email protected]⁠

⁠Documentation

For usage guide please see: www.mock-server.com⁠

⁠Community

• Backlog:                     
• Freature Requests:  
• Issues / Bugs:           
• Chat:                           

⁠Versions

⁠Maven Central

Maven Central contains the following MockServer artifacts:

• mockserver-netty⁠ - an HTTP(S) web server that mocks and records requests and responses
• mockserver-netty:jar-with-dependencies⁠ - 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⁠.

⁠Node Module & Grunt Plugin

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

Docker Hub contains the following artifacts:

• MockServer Docker Container⁠ - a Docker container containing the Netty MockServer and proxy

⁠Helm Chart

• MockServer Helm Chart⁠ - a Helm Chart that installs MockServer to a Kubernetes cluster, available versions:
  • 5.7.2⁠
  • 5.7.1⁠
  • 5.7.0⁠
  • 5.6.1⁠
  • 5.6.0⁠
  • 5.5.4⁠
  • 5.5.1⁠
  • 5.5.0⁠
  • 5.4.1⁠
  • 5.3.0⁠

⁠MockServer Clients

• 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

⁠Document

⁠Issues

If you have any problems, please check the project issues⁠.

⁠Contributions

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 the milestones⁠ to see what is planned for future releases.

⁠Maintainers

• James D Bloom⁠