Sebastian Brudziński
unread,Sep 21, 2016, 7:28:47 AM9/21/16Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to openlm...@googlegroups.com
Hello.
Since one of the goals of this sprint is to drop the links from
individual services to other services and only have OpenLMIS-blue tie
them together, I wanted to bring up the topic of testing the APIs that
depend on other services and to have a final decision on the strategy
that we want to follow while refactoring the current tests. I know that
we have discussed the possibility of using WireMock for the purpose of
mocking the external APIs for a longer time and which seems like the
easiest/simplest solution. However, from our recent calls and meetings I
understand, that we would rather want to mock the HttpClient /
RestTemplate or whatever else is used in the service to communicate with
the other service.
My question is, do we have any specific reason to avoid WireMock or
other similar library for mocking external APIs and doing it kind of
manually, by mocking the http client? I also want to make sure that we
agree on one strategy, so we don't end up having some tests mocking APIs
one way and other mocking them another way.
Thanks!
Sebastian Brudzinski.