You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in some circumstances that timeout isn't sufficient for some web services we test against so it would be great if their was a means to override these default values.
The text was updated successfully, but these errors were encountered:
so the outer method run doesn't return a http client. So I'm assuming to accept a http client some refactor of the existing code would need to be done? If that was done then I assume the http client would be created without the default request config, which likely would be done by a consumer of the library right (me in this case)?
Another very quick fix potentially could be
public static int SOCKET_TIMEOUT = 60000;
public static int CONNECT_TIMEOUT = 5000;
public static int CONNECTION_REQUEST_TIMEOUT = 5000;
or nicer again through the use of getters and setters.
Sorry, I meant we can change the PostmanRequestRunner constructor to also take an optional http client provider. That way, you can pass in your own http client. For example:
public interface HttpClientProvider {
CloseableHttpClient getHttpClient();
}
public PostmanRequestRunner(PostmanVariables var, boolean haltOnError, HttpClientProvider provider) {
...
}
At the moment the default timeout values within the following source file
https://github.com/poynt/postman-runner/blob/master/src/main/java/co/poynt/postman/PostmanRequestRunner.java are
SocketTimeout -> 60000
ConnectTimeout -> 5000
ConnectionRequestTimeout -> 60000
in some circumstances that timeout isn't sufficient for some web services we test against so it would be great if their was a means to override these default values.
The text was updated successfully, but these errors were encountered: