https://github.com/mountebank-testing/mountebank
Over the wire test doubles
https://github.com/mountebank-testing/mountebank
microservices-testing mocking mountebank service-virtualization stubbing test-automation test-framework testing
Last synced: 3 months ago
JSON representation
Over the wire test doubles
- Host: GitHub
- URL: https://github.com/mountebank-testing/mountebank
- Owner: mountebank-testing
- License: mit
- Created: 2013-10-27T00:48:22.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2025-08-06T21:46:34.000Z (3 months ago)
- Last Synced: 2025-08-13T23:19:47.518Z (3 months ago)
- Topics: microservices-testing, mocking, mountebank, service-virtualization, stubbing, test-automation, test-framework, testing
- Language: JavaScript
- Homepage:
- Size: 49.3 MB
- Stars: 2,032
- Watchers: 60
- Forks: 292
- Open Issues: 99
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# Project in transition
Currently the project is in transition to a collaborative group effort under a github organisation.
Work is being done to migrate and upgrade all CI/CD integrations from personal accounts to organisation accounts.
Pull requests are welcome, but don't expect anything to be merged until CI/CD infrastucture is up and running.
Many thanks goes to [Brandon Byars](https://github.com/bbyars) for all the effort building mountebank in the first place and maintaining the project for more than a decade and finally being helpfull and collaborative during this transition phase.
# Welcome, friend
mountebank is the only open source service virtualization tool that competes with the commercial offerings
in terms of protocol diversity, capability, and performance. Here's what
[Capital One wrote](https://medium.com/capital-one-tech/moving-one-of-capital-ones-largest-customer-facing-apps-to-aws-668d797af6fc)
about their mobile cloud migration (emphasis theirs):
>In fact, halfway through we discovered our corporate mocking software couldn’t handle the
>sheer amount of performance testing we were running as part of this effort (_we completely crushed
>some pretty industrial enterprise software in the process_). As a result, we made the call to move
>the entire program over to a Mountebank OSS-based solution with a custom provision to give us the ability
>to expand/shrink our mocking needs on demand.
At the moment, the following protocols are implemented, either directly in the tool or as a community extension:
* http
* https
* tcp (text and binary)
* smtp
* ldap
* grpc
* websockets
* graphql
* snmp
* telnet
* ssh
* netconf
mountebank supports mock verification, stubbing with advanced predicates, JavaScript injection,
and record-playback through proxying.
See [getting started](http://localhost:2525/docs/gettingStarted) guide for more information once you have it running locally.
## Install and Run
Install:
npm install -g mountebank
Run:
mb
There are a number of [command line options](http://localhost:2525/docs/commandLine) if you need
to customize mountebank.
All pre-release versions of mountebank are available with the `beta` [npm tag](https://www.npmjs.com/package/mountebank).
No `beta` version is published unless it has passed all tests.
## Learn More
After installing and running, view the docs in your browser at .
You can always learn more and support mountebank development by buying the book:
[](https://www.manning.com/books/testing-microservices-with-mountebank?a_aid=mb&a_bid=ee3288f4)
## Building
There are two packages: mountebank itself, and a test package called mbTest (which houses all
out-of-process tests against mountebank). First ensure all dependencies are installed for both packages:
npm install
Then, run all tests:
npm test
Several other test configurations exist. You can see the CI pipeline in .circleci/config.yml.
There are some tests that require network access.
A few of these tests verify the correct behavior under DNS failures. If your ISP
is kind enough to hijack the NXDOMAIN DNS response in an attempt to allow you to conveniently peruse their
advertising page, those tests will fail. I suggest that, under such circumstances, you talk to your ISP
and let them know that their policies are causing mountebank tests to fail. You can also set
the environment variable `MB_AIRPLANE_MODE=true`, which will avoid tests requiring your DNS resolver.
[npm-badge]: https://nodei.co/npm/mountebank.png?downloads=true&downloadRank=true&stars=true
[npm]: https://www.npmjs.com/package/mountebank
[codeclimate-badge]: https://codeclimate.com/github/bbyars/mountebank/badges/gpa.svg
[codeclimate]: https://codeclimate.com/github/bbyars/mountebank
[codeclimate-coverage-badge]: https://codeclimate.com/github/bbyars/mountebank/badges/coverage.svg
[codeclimate-coverage]: https://codeclimate.com/github/bbyars/mountebank/coverage