Slow Test Communication

[Luke Buthman]

Hi Scott, hope you had a nice holiday season. I noticed something tonight where the reported test time is ms, while the actual time is 46-52 sec. I found an old post of yours on Reddit, and thought I’d let you know about this instance. So is it that while the job is sitting in the Salesforce queue, it is idle and thus not being timed. Yes, the test runs in 78 ms, but the elapsed time is 46.91 sec. Is it like that? And yes, I am executing this against a sandbox. Feel free to close this ticket out, just wanted to let you know.

[Scott Wells]

Hi. If I understand correctly, you're saying that the test duration reported by IC2 can include the time spent in queue and not just the execution time, correct? That may be the case, but it's all based on the times reported by the Salesforce APIs. I'm just capturing the duration values provided in the API's RunTestSuccess and RunTestFailure responses, and the IDE is then presenting those.

Please let me know if I'm misunderstanding the issue, though.

[Luke Buthman]

Yeah, that is what I was seeing or at least that would explain it. Is there anything I can do, that you have seen in your experience, to reduce the time it sits on their queue? I am aware that it is outside your domain of influence, but maybe you know a Jedi trick.

[Scott Wells]

Unfortunately there’s typically not any workaround for long queues in the servers. The best approach is to report it to them with concrete examples, specifically citing your org ID and instance ID in the support case. Then they can look into why queues are long in that environment and, if the stars align, correct the issue.

[Luke Buthman]

Ok, thanks for the clarification! I feel like I can live with it. This is already so convenient, isn’t it lol. I remember the Dev Console days, and executing those tests. IC2 users have it pretty good. Thanks for keeping this going. Happy New Year!

‌