+ Start a Discussion
SoCal AdminSoCal Admin 

Code Coverage / Deployment

Can someone please forward this to development:

 

There is no reason to test UNRELATED classes when deploying Apex classes and triggers.

 

If I use Eclipse to deploy ONE FREAKING class - there is no reason to TEST the entire metadata.

 

Is there any way to disable tests for UNRELATED CLASSES?


Salesforce is ***INCREDIBLY*** slow (15 minutes) for EACH deployment which should be done in 30 seconds. (or 10...)

 

Are there any OVERRIDE features to get past this poor design?  Or is it Working as Designed to waste time?

 

Please take the Unnecessary Elements out of your design work.

Rakesh BoddepalliRakesh Boddepalli

Cool !! :) SoCal Admin

 

Understand that you are working in a multi-tenant environment .

 

- The reason why salesforce.com tests all the classes each and every time you do deployment , is to benefit you . They don't want any of your broken code running their production orgs that may cause memory leaks and performance degradation to other customers present in a given pod/node.

 

- Additionally, before each and every salesforce.com release upgrade (i.e., Winter , spring and summer) they run all the test classes present in your org, so as to make sure that they are not breaking any of your code, without the test classes there is no way for them to test to your code.

 

- Yes, the salesforce.com deployment is very slow ; as your request will be queued in the queue to execute (so you are mercy of other customers).  Also note that salesforce.com doesn't store any complied version or binary version of code , it needs to replace your metadata files in real time to get the changes in real time. Of course they can make it faster with investing in more sophisticated hardware , but that will once their balance sheets turn to Green .. :)