What’s the reason for wiremock instead of Mockito in integration tests [closed]

  softwareengineering

I enjoyed the process of writing an integration test for a system that relies on http, by mocking such end-points with Wiremock, and I feel upskilled, having wrestled with Matchers.

Now, Wiremock as a standalone server is very useful for multiple reasons but, although it has neat integration with JUnit, I don’t get the point in choosing it, instead of, for example, Mockito, as a mocking framework in tests. Someone, please school me.

5

Wiremock is designed specifically for integration testing, where Mockito is designed for unit testing. Wiremock describes itself as a “simulator for HTTP-based API’s”, whereas Mockito describes itself as “a mocking framework that tastes really good.”

In short, they’re two entirely different use cases, despite the similarities.

4

LEAVE A COMMENT