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 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.
mountebank is the first open source tool to provide cross-platform, multi-protocol test doubles over the wire. Just point your application to mountebank instead of the real dependency, and test like you would with traditional stubs and mocks.
At the moment, the following protocols are supported:
- http
- https
- tcp (text and binary)
- smtp
mountebank supports mock verification, stubbing with advanced predicates, JavaScript injection, and record-playback through proxying.
See getting started guide for more information.
Install:
npm install -g mountebank
Billions of other install options are also available with no platform dependencies.
Run:
mb
There are a number of command line options if you need to customize mountebank.
After installing and running, view the docs in your browser at http://localhost:2525, or visit the public site.
You can always learn more and support mountebank development by buying the book:
mountebank has the following goals:
- Trivial to get started
- mountebank is easy to install, without any platform dependencies. mountebank aims for fun and comprehensive documentation with lots of examples, and a nice UI that lets you explore the API interactively.
- A platform, not just a tool
- mountebank aims to be fully cross-platform, with native language bindings. Servers are extensible through scripting.
- Powerful
- mountebank is the only open source stubbing tool that is non-modal and multi-protocol. Commercial "service virtualization" solutions exist, but their licensed platforms make it hard to move the tests closer to development and can even require a specialized IDE. mountebank provides service virtualization free of charge without any platform constraints.
Not all of mountebank's goals are currently implemented, but fear not, for he has a team of top-notch open source developers, and they are legion.
mountebank is used by a large number of companies and I think it's important to convey my best guess as to what the feature roadmap is. I've adopted GitHub tools to manage the roadmap. Specifically, the Roadmap project page shows the features by release. I generally re-prioritize and update the ETAs each release. I'm in the middle of writing the mountebank book at the moment too, so please be patient.
Visit the Google group for any support questions. Don't be shy!
mountebank is provided free of charge and maintained in my free time. As such, I'm unable to make any kind of guarantees around either support turn-around time or release dates. If your company has commitments that require more confidence and are willing to pay a reasonable services fee to obtain that confidence, you can contact me directly at [email protected].
For cross-OS compatibility, mountebank uses TravisCI, Appveyor, and CircleCI. Only CircleCI runs on commit (TravisCI and Appveyor are triggered in the CircleCI pipeline), and you can view the success of the TravisCI and Appveyor builds in CircleCI as the "osx" and "windows" jobs, respectively.
./build should do the trick on Mac and Linux, and build.bat on Windows, assuming you have at least node 4.0.
If not, yell at me.
There are some tests that require network access (grunt airplane ignores them in case that offends your
moral sensibilities). 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 run grunt airplane,
which will avoid tests requiring your DNS resolver.
Contributions are welcome! Some tips for contributing are in the contributing link that spins up when you run mb. I have a liberal policy accepting pull requests - I'd rather you sent them even if you can't figure out how to get the build working, etc. I'm also available via Skype or something similar to help you get started. Feel free to reach me at [email protected].