Masquerade Service Simulator Released

A first version of Masquerade Service Simulator has been released. Masquerade is a configurable Service Simulator that returns simulated responses for service requests.

Service stubs can easily be implemented using Masquerade. Simply run Masquerade standalone using its embedded Jetty server or deploy it to an application server (e.g. Tomcat) of your choice, and configure your simulations using its web interface.

Service simulation is useful for example when

  • Providing a service stub for integration or regression tests
  • Doing functional tests against a system that is not (yet) available
  • Providing a stub for functionality that is yet to be implemented in an agile project

Supports the following request listener channels in this first release:

  • HTTP (using the servlet container and standalone on different port)
  • JMS (queue/topic, connection factories for WSMQ and ActiveMQ included)
  • File
  • FTP

Contains simulation actions for various request/response scenarios, while quite a few of them support XML, any kind of response can be simulated. Response simulations are based on simulation scripts that contain actions such

  • Template-based response
  • Adding content to the response
  • Groovy script step
  • Ruby script step
  • Java Script step
  • Synchronous/asynchronous responses
  • Wait step
  • Variable management and substitution steps
  • XML transformation steps

The simulator also provides an API to query for received requests (useful when asserting request contents in integration tests), and to specifiy expected responses externally before issuing requests.

The Source code repo is at

This entry was posted in Java, Masquerade, Testing. Bookmark the permalink.

One Response to Masquerade Service Simulator Released

  1. Lenny L. Miller says:


    Well I’m excited to try your simulator out and thanks for taking the time and energy to provide a very key element to our prospering agile community.

    I am interested in trying this tool out on a real project, and when I downloaded it and typed I received an error indicating I needed JMS, added that, and then re-ran .

    At that point I received an error regarding JSP Servlet (can provide details if desired) at that point I assaulted google with that error and it ,Ed me to a seemingly obvious fix where by I included the dependency. This did not work and I am still recording this error when I try to start this.

    It would be very helpful if you expounded on the steps to follow when building. For instance I was able to get past the JMS error by using google searches, and felt silly when I went back and noticed your JMS disclaimer.

    I look forward to being able to use your system this week so I can simulate an external service.

    Kind and gracious regards,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s