I'm attempting to deploy a change set from my Sandbox to the production environment. The change set includes 1 Custom Object, several dozen custom fields, a controller (Apex class), and a static resource (an image file). When deploying the inbound change set, I get code coverage errors relating to 2 triggers. There are no triggers in my change set, so I'm confused as to why I'm getting these errors on this specific operation.
The only reason I could see this happening is if the triggers already on the live server, independent of this change set, are written so that they lack the appropriate code coverage. However, wouldn't this error have popped up when the triggers were committed?
I'm only in charge of a small portion of our SalesForce instance, so I lack the scope of responsibilities necessary to start messing with these unrelated triggers. Is there anything I can do to get my change set deployed with this being the case?
Best Answer
There are no triggers in your change set, but is there test code for the apex controller? Salesforce requires 75% cumulative code coverage, which includes Apex controllers, so if the code coverage in your production org is just above 75% and your controller is untested it could drag the total code coverage down to below the threshold. It's also possible that the total is already below 75% in your production environment, possibly caused by an admin changing workflow rules, validation rules, or process builder processes without checking tests.