We found that we have requirements to record wiremock stubs against 3rd party APIs to use them later on in integration tests.
Projects that already use wiremock-spring-boot-starter would really benefit if the project can handle recording and stubbing. (handling the dynamic wiremock port, adding WireMockServer as a bean, ease of setup)
What do you think @otrosien @jensfischerhh - is this functionality a good fit here
Coverage remained the same at 93.333% when pulling b6724cab059648b63bce5eb26e36d999eb22caa1 on mduesterhoeft:feature/record-mode into d49e4f2ef325ff2ffb73fc984e79cd386469d338 on ePages-de:master.
Coverage remained the same at 93.333% when pulling 6865b9259149b7f02f036f8a0fea3de3f69a5da3 on mduesterhoeft:feature/record-mode into d49e4f2ef325ff2ffb73fc984e79cd386469d338 on ePages-de:master.
We found that we have requirements to record wiremock stubs against 3rd party APIs to use them later on in integration tests.
Projects that already use
wiremock-spring-boot-starter
would really benefit if the project can handle recording and stubbing. (handling the dynamic wiremock port, adding WireMockServer as a bean, ease of setup)What do you think @otrosien @jensfischerhh - is this functionality a good fit here