For information on how to use the MockServer please see http://www.mock-server.com/
Unfortunately both Travis CI and drone.io don't seem to be stable enough for MockServer. The MockServer uses lots of socket connections to complete its integration tests. The same build with no code or configuration changes run multiple times fails randomly on both Travis CI and drone.io. It is likely due to the server infrastructure using either a hypervisor or containers that is causing issues with the heavy socket use in the integration tests. As a result the build status will not be displayed any longer on github or at the top of the homepage.
Maven Central contains the following MockServer artifacts:
- mockserver-maven-plugin - a set of maven plugins to start, stop and fork MockServer using maven
- mockserver-vertx - a Vert.X module that mocks HTTP and HTTPS requests
- mockserver-jetty - a web server that mocks HTTP and HTTPS requests (using Embedded Jetty)
- mockserver-jetty:jar-with-dependencies - a fully stand alone web server embedded with all dependencies that mocks HTTP and HTTPS requests (using Embedded Jetty)
- mockserver-war - a deployable WAR for mocking HTTP and HTTP requests (that runs on any JEE web server)
- mockserver-proxy - an HTTP / HTTPS proxy that allows the recording and querying of requests and response
- mockserver-client - a Java and JavaScript client to communicate with both the server and the proxy
In addition MockServer SNAPSHOT artifacts can also be found on Sonatype.
Vert.X Module Registry contains the following artifacts:
- org.mock-server
mockserver-vertx2.0 - a Vert.X module that mocks HTTP and HTTPS requests
Vert.X Module Registry will shortly also have the following artifacts:
- org.mock-server
mockserver-vertx-proxy2.0 - a Vert.X module that proxies HTTP and HTTPS allowing the recording and querying of requests and responses
If you have any problems, please check the project issues.
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.