Wiremock
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Wiremock | 5,564 | 1,626 | 752 | 14 hours ago | 104 | September 10, 2020 | 326 | apache-2.0 | Java | |
| A tool for mocking HTTP services | ||||||||||
| Vcrpy | 2,418 |  | 860 | 111 | 2 days ago | 65 | June 29, 2022 | 123 | mit | Python |
| Automatically mock your HTTP interactions to simplify and speed up testing | ||||||||||
| Hoverfly | 2,077 | 1 | 21 days ago | 80 | August 22, 2022 | 31 | apache-2.0 | Go | ||
| Lightweight service virtualization/ API simulation / API mocking tool for developers and testers | ||||||||||
| Httpretty | 2,038 |  | 2,640 | 93 | 25 days ago | 59 | August 16, 2021 | 113 | mit | Python |
| Intercept HTTP requests at the Python socket level. Fakes the whole socket module | ||||||||||
| Gock | 1,795 | 120 | 407 | 3 months ago | 21 | August 03, 2021 | 38 | mit | Go | |
| HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽ | ||||||||||
| Httpmock | 1,670 | 217 | 758 | 4 days ago | 16 | May 06, 2022 | 2 | mit | Go | |
| HTTP mocking for Golang | ||||||||||
| Wiremock.net | 1,104 |  | 23 | 12 | a day ago | 200 | June 10, 2022 | 21 | apache-2.0 | C# |
| WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality. | ||||||||||
| Gentleman | 875 | 1 | 2 years ago | 16 | February 18, 2021 | 17 | mit | Go | ||
| Full-featured, plugin-driven, extensible HTTP client toolkit for Go | ||||||||||
| Mockttp | 656 |  | 22 | 43 | 14 days ago | 89 | July 04, 2022 | 25 | apache-2.0 | TypeScript |
| Powerful friendly HTTP mock server & proxy library | ||||||||||
| Apitest | 630 | 7 | 22 | 25 days ago | 105 | May 22, 2022 | 1 | mit | Go | |
| A simple and extensible behavioural testing library for Go. You can use api test to simplify REST API, HTTP handler and e2e tests. | ||||||||||
WireMock - a web service test double for all occasions
!!! Log4j notice !!!
WireMock only uses log4j in its test dependencies. Neither the thin nor standalone JAR depends on or embeds log4j, so you can continue to use WireMock 2.32.0 and above without any risk of exposure to the recently discovered vulnerability.
Key Features
- HTTP response stubbing, matchable on URL, header and body content patterns
- Request verification
- Runs in unit tests, as a standalone process or as a WAR app
- Configurable via a fluent Java API, JSON files and JSON over HTTP
- Record/playback of stubs
- Fault injection
- Per-request conditional proxying
- Browser proxying for request inspection and replacement
- Stateful behaviour simulation
- Configurable response delays
Full documentation can be found at wiremock.org
Questions and Issues
If you have a question about WireMock, or are experiencing a problem you're not sure is a bug please post a message to the WireMock mailing list.
On the other hand if you're pretty certain you've found a bug please open an issue.
Contributing
We welcome bug fixes and new features in the form of pull requests. If you'd like to contribute, please be mindful of the following guidelines:
- All changes should include suitable tests, whether to demonstrate the bug or exercise and document the new feature.
- Please make one change per pull request.
- If the new feature is significantly large/complex/breaks existing behaviour, please first post a summary of your idea on the mailing list to generate a discussion. This will avoid significant amounts of coding time spent on changes that ultimately get rejected.
- Try to avoid reformats of files that change the indentation, tabs to spaces etc., as this makes reviewing diffs much more difficult.
- Abide by the Architecture Rules enforced by ArchUnit.
Building WireMock locally
To run all of WireMock's tests:
./gradlew clean test
To build both JARs (thin and standalone):
./gradlew jar shadowJar
The built JAR will be placed under build/libs.
To publish both JARs to your local Maven repository:
./gradlew publishToMavenLocal
