v1.3.0
Note that this release changes some default command line behavior. It's not a breaking change -
all previous functionality is still supported, but it means you may need to pass in some additional
command line flags (specifically --mock
and --debug
) to get the same behavior
as before, if you depended on either the requests
or matches
arrays recorded
with imposters and stubs previously.The following changes are part of this release.
New Features
- Thanks to Paul Phillips, mountebank now works with node v0.12 and v4.0.
- A
timestamp
has been added to each element in therequests
array to allow for richer verification testing. - The
matches
array is only included if you use the--debug
command line parameter. In practice, this array confused people. It is still supported, but is only intended for debugging purposes to determine when a stub matches or doesn't. - The
requests
array is only included if you use the--mock
command line parameter, and the--nomock
parameter no longer matters. This is the inverse of prior behavior and represents learning that the default use case for most people is to turn off recording requests by default (which represents a memory leak), as many people prefer long runningmb
instances set up with config files or used for performance testing.
Many thanks to the following kind folk for help with this release:
- Paul Phillips
- Quadir Kareemullah
Install
npm install -g mountebank@1.3.0 --production
or:
Option | node.js required? | sudo required? | links | Description |
---|---|---|---|---|
Self-contained archives | No | No | Simply unpack and run mb from inside |
|
OS-specific packages | No | Yes | Puts mb at /usr/local/bin , which is generally in the PATH . |
|
source tarball | Yes | No | source tarball if you roll that way. |