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:
See getting started guide for more information.
npm install -g mountebank
Billions of other install options are also available with no platform dependencies.
There are a number of command line options if you need to customize mountebank.
You can always learn more and support mountebank development by buying the book:
mountebank has the following goals:
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@example.com.
|Node Version||Ubuntu 12.04||CentOS 6.7||OS X Mavericks||Windows Server 2012|
|npm||v6.10 (LTS)||(not tested)|
|OS package||v6.10||(not tested||N/A|
|Self-contained archive||v6.10||(not tested)|
|(Performance)||v6.10||(not tested)||(not tested)||(not tested)|
./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
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 firstname.lastname@example.org.