You need to sign in to do that
Don't have an account?
Pronow
How to bypass runAll test while deploying to Production?
Hello there,
I have a weired problem while deploying change sets to production. I am trying to deploy an updated trigger, and it gives warning that Trigger and Class Code Coverage is 0% and it should be 75% atleast. Now, previously, I deployed many classes(only classes), it didn't throw such an error.
I need proper understanding of difference between deploying Triggers and classes. Does same procidure applies for same or it differs.
Thanks in advance.
I have a weired problem while deploying change sets to production. I am trying to deploy an updated trigger, and it gives warning that Trigger and Class Code Coverage is 0% and it should be 75% atleast. Now, previously, I deployed many classes(only classes), it didn't throw such an error.
I need proper understanding of difference between deploying Triggers and classes. Does same procidure applies for same or it differs.
Thanks in advance.
All Answers
Usually this type of issue means that something has changed config-wise that means the unit tests aren't covering as much code. For example, if you have failing unit tests it can be because new required fields or validation rules have been introduced that stop creation of test objects. Or it can be because your tests are not isolated from production data and the volumes are causing an issue. Or it could be many other things :)
Unfortunately, the bottom line is that you will have to fix up the unit tests as part of the deployment.
However, I am still amazed that why my deployments succeeded when I deployed classes only and failed when I tried deploying triggers, the first thing. The second thing is that, can I export production code into eclipse/force.com ide and try editing and saving it directly? Will it work? Will it still execute runAllTests?