How to solve when the Elapsed time is mismatched between the Object Repositories and the Test Cases?

Technically, KS use Java HttpClient as our library to simulate HTTP request. When running in test execution: test case or test suite, KS will create a different Java process. When combining with HTTPClient, the first request is always slower than normal to establish and keep the connection alive, but the subsequence request connection’s elapsed time will be back to normal.

The suggestion is to send a temporary request at the beginning of test cases or test suite in a test listener and track the response’s elapsed time in the main test script.