Saturday, December 9, 2017

Get rid of your external dependencies with WireMock




Contents:

1) Introduction - why WireMock?
2) Getting started
3) Framework preparation
4) Simple examples

1) Introduction - why WireMock?

So far in my posts focusing on API testing I was using external services only. This isn't particularly bad for higher level tests, but sometimes we would like to work on our localhosts only. This eliminates potential flakiness related to network fluctuations, deployment being in progress or general instability of services we rely on. Today I'd like to recommend you one tool that hugely simplifies our quest for testing an app in total isolation - WireMock. It's not a tool just got released and doesn't work for anyone except the author, it's more like established industry standard used by many companies (including Pivotal).

I read once that someone didn't like my Rest Assured post. Reader was claiming that it's too old framework to show on blogs. The thing is I want my readers to learn valuable stuff and reuse my GitHub examples so I don't want to change my approach in 'technical' posts. My general recommendation regarding tools is pretty much aligned with what I present here: always choose older and more popular one unless you are 100% sure that new 'cutting-edge' tool is indeed that great. Gatling is perfect example of that. I know a lot of people who thought it brilliant, but upon problems with more complex scenarios gave it up and came back to  JMeter instead.

2) Getting started

As usual we need to add Maven dependency first. I'm including also javax.json library for simple JSON creation, but you can choose what you want here.

Unfortunately I had also a lot of problem with my classpath. WireMock uses jetty server 9.22 which is pretty old. This generates conflicts with selenium-java so I had to add a lot of ugly exclusions in my pom. See commit for details. This may happen for you so get ready to analyse your mvn dependency:tree.

3) Framework preparation

A bit of side note first: I often hear that testers would like have some kind of online portfolio available publicly. I recommend to follow my path and integrate blogging with coding. It gives me a lot of online presence with relatively small effort. As a bonus I guarantee you that even with such a simple tests you would learn something extra for yourself.

End of chit-chat, now meat only.

First of all opposite to what I usually do I'll be using Junit. By the way there is definitely not a good idea to mix TestNG and Junit in on project. My IntelliJ  was struggling to choose proper framework automatically and I had to choose import after every @Test. Do yourself a favor and don't follow my path - chose Junit from start ;) 

I chose to use hierarchical approach in my tests. This class would be extended by each Test class. 

There are three methods:
1. JUnit WireMock @Rule starts server on random port (it's important to randomize it because it allows us to run  tests simultaneously).
2. We set port for RestAssured baseUrl (it would be http://localhost: + this port)
3. We cleanUp stubs after each test


4) Simple examples

I have prepared three very simple scenarios. Please take a look at @Before section. That's where all the WireMock magic happens. We can define what kind of requests would be captured and how WireMock would respond for them. In this example GET request for http://localhost:port/ip returns JSON defined in getMockedIpEndpointJson() method.

For actual request sending I'm using RestAssured which is familiar for my readers.

As you can see WireMock allows us to build requests in almost the same way as RestAssured. Those two frameworks make great duo.


Second test is almost identical, but contains more complex assertions.


Last but not least we can of course use POST, PUT, DELETE methods. Here is rather silly POST example.


Isn't it beautiful? :)