Skip to main content
Topics#ApexSam Mohyee's Question
Sam Mohyee (Northern Bank and Trust) asked in #Apex
Aug 16, 2018, 9:21 PM

Deployment with single Apex test taking 15+ minutes to even START the test run...

Here's what I've been staring at for 16 minutes so far. 

Deployment with single Apex test taking 15+ minutes to even START the test run...

Deployed via SFDX, specifying a single apex test to run, which has less than 40 lines of code. Takes only a fraction of a second to run in scratch org or sandbox.

But when I deploy to Production, all components are validated within a minute or two, then the status switches to 'Running {testname}'.... and stays that way. For literally 15 minutes or more. Before the test is even started. 

I'm not finding a lot of posts on this issue. Plenty of people talking about the time it takes to actually run the test. But I'm talking about the time it takes to start running the tests. This isn't a one time thing, but it also isn't consistent. Sometimes the tests will begin running pretty much immediately. Sometimes I'll end up cancelling and redeploying because a 30 minute delay to START testing seems ridiculous even given Salesforce's standards. And when I do cancel and redeploy? Good chance it'll take a fifth of the time, for no apparent reason.

What I'd really like is some better communication during this process. Why is my test run delayed? What was prioritized ahead of it? How can I anticipate deployment times so it's not a complete crapshoot regardless of build size? 
5 answers
  1. SUBRAMANI J (INFOSYS LIMITED)
    Aug 22, 2018, 9:27 AM
    do you have any debug logs level with FINEST ?

    Before running a deployment, verify that the Apex Code log level is not set to FINEST. Otherwise, the deployment is likely to take longer than expected. If the Developer Console is open, the log levels in the Developer Console affect all logs, including logs created during a deployment.
Write an answer...
0/9000