Delay not working about restmock HOT 5 CLOSED

while the logs might be misleading, they are not an indicator of whether the functionality is working or not. By default, the http's response body gets delayed indeed, and logs are printed out as soon as the response dispatcher finds a match for given request.

To reiterate: Logs are immediately logging responses while the real response gets delivered after some delay. This is a good point though to delay logs aswell

from restmock.

Ok, I get that !
But even when I do not watch the logs, the test ends in about 3 seconds - so I guess it is not working anyway.

What debug info can I give you ?

from restmock.

is bernardWebService.logout() a synchronous call? if its not, that is the case why tests finish before actual response gets delivered.

from restmock.

bernardWebService.logout() calls a Retrofit API method:

public boolean logout() throws IOException {
        // BernardAPI is an interface using Retrofit annotations
        Response<Void> response = BernardAPI.logout().execute();
        return response.code() == 200;
    }

The execute method of retrofit is synchronous, as written on its javadoc:

  /**
   * Synchronously send the request and return its response.
   *
   * @throws IOException if a problem occurred talking to the server.
   * @throws RuntimeException (and subclasses) if an unexpected error occurs creating the request
   * or decoding the response.
   */
  Response<T> execute() throws IOException;

from restmock.

Keep in mind MockWebServer, followed by RESTMock, delays the body of a response, not the entire response. so what you'd have to do is to wait for the entire body to arrive and then check the response.code. So something like this:

public boolean logout() throws IOException {
        // BernardAPI is an interface using Retrofit annotations
        Response<Void> response = BernardAPI.logout().execute();
        String body = response.body().string()
        return response.code() == 200 && body != null && !body.isEmpty();
    }

take a look into f7df1a4 for a unit test that demonstrates this behavior

from restmock.