Sufficiently long running tests receive a 443 error

[wspringe]

We have large tests in our org and for our larger tests and test classes, I receive a 443 error (failed to respond) when I try to run these tests through Illuminated Cloud 2. I’m not even seeing the tests as being submitted within the org’s test execution history. The tests execute normally through the Salesforce CLI.

[Scott Wells]

Hi. I can see a response code of 403 in the provided log, but I can’t see the details. Can you please enable debug logging for Apex Unit Testing, reproduce the behavior, and attach a new log for review?

[wspringe]

Sure, no problem

[Scott Wells]

Thank you. It looks like the 403 is being returned when running these tests synchronously. Can you please enable Illuminated Cloud | Configure Application | Unit Tests and Code Coverage | Always run unit tests asynchronously, rerun these tests, and see if the same issue occurs? If it does, please attach the resulting idea.log for review.

[wspringe]

Ah, that did the trick. Thanks!

[Scott Wells]

Okay, good to know. That means it's another bug in the Salesforce synchronous test execution REST API. And those bugs are why that configuration option exists. For the most part, execution of tests from a single Apex test class can be faster when run synchronously because there's no job queue, but for whatever reason there do seem to be differences between sync and async test execution that can result in some false negatives in the former. Glad that helped!