jamesdbloom
commented
4 years ago Are you creating a new instance of MockServer for every test and a new instance of MockServerClient?
I would not suggest doing that, they can be shared between tests.
However, how are you shutting down MockServer? Are you shutting it down currently? You can use a separate instance of both MockServer and MockServerClient for each test class as long as you call the stop() method on MockServerClient when each test class completes.
DmitryShabalin
Flow I have BaseIT where i want to add some default expectation for mockserver to lower boilerplate code in child tests. In some test needed some another behavior so i clear old and add new expectation. Its work correct.
I used here 1 MockServerClient Bean is it ok? Or i should create new bean per each child it class?
Issue description Its similar to issues#577. But i do not think its good to create mockServerClient every time for creating expectation and verification
I have about 260 test and somewhere between 60-100 test i faced with org.mockserver.client.netty.SocketCommunicationException: Response was not received from MockServer after 20000 milliseconds, to make the proxy wait longer please use
What you are trying to do
MockServer version The version you are using (i.e. 5.7.2)
To Reproduce I use docker. Steps to reproduce the issue: create Base class with default expectations and so not use server api in some tests.
Expected behaviour Possibility use default expectation for all tests which can even do not call some of expectation.