{"id":2085,"date":"2016-09-07T11:35:27","date_gmt":"2016-09-07T11:35:27","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/salesforce\/?p=2085"},"modified":"2025-05-08T09:00:28","modified_gmt":"2025-05-08T09:00:28","slug":"deployment-options-for-changeset","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/salesforce\/2016\/09\/07\/deployment-options-for-changeset\/","title":{"rendered":"Deployment Options for Changeset"},"content":{"rendered":"\n

Salesforce ‘Winter 16’<\/strong> release has provided a new way to deploy a change set in the production organization. These deployment changes include test options for change sets.<\/p>\n\n\n\n

Now, a user can choose which tests to run when validating an inbound change set in production or sandbox at the time of deployment. Test options provide flexibility in how much testing is done to achieve quality and code coverage requirements which will reduce execution time in a deployment. This feature is available in both Lightning Experience and Salesforce Classic.<\/p>\n\n\n\n

The following test options are available when deploying or validating an inbound change set :-
<\/ins><\/p>\n\n\n

\n
\"All<\/a>
All available test options<\/figcaption><\/figure><\/div>\n\n\n

-> Default : It keeps the default behavior for all tests. In sandbox, no tests are executed. In production, all local tests are executed if change set contains Apex classes or triggers.Local tests are all tests, except the ones that originate from managed packages. If package doesn\u2019t contain Apex components, no tests are run.
-> Run Local Tests : In this all tests in organization are run, except the ones that originate from installed managed packages. This test level is the default for production deployments that include Apex classes or triggers.
-> Run All Tests : In this all tests in organization are run, including tests of managed packages.
-> Run Specified Tests : Only the tests that user specify are run.User has to provide the names of test classes in a comma-separated list. Benefit of choosing this option is that it checks code coverage criteria at the Changeset level rather than checking it at the entire org level. The executed tests must cover the classes or triggers contained with in change sets with a minimum of 75% code coverage. This coverage is computed for each class or trigger individually and is different from the overall coverage percentage.<\/p>\n\n\n

\n
\"Run<\/a>
Run specified tests<\/figcaption><\/figure><\/div>\n\n\n

This last option has come as a boon to the Salesforce Developers who just work on an independent functionality and don\u2019t want the already existing test classes in Production to hamper their deployment. So, Happy Deployment \ud83d\ude42<\/p>\n\n\n\n

About Us<\/strong><\/span>
Greytrix<\/a> as a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners across the globe. We offers Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that requires apex code incorporation into the Salesforce platform.<\/p>\n\n\n\n

Greytrix<\/a> has some unique solutions for Cloud CRM such as Salesforce integration with Sage Enterprise Management (Sage X3<\/a>), Sage Intacct, Sage 100 <\/a>and Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development<\/a> and Technical Support<\/a> to business partners and end users.<\/p>\n\n\n\n

Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n\n\n\n

For more information, please contact us at salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n\n\n\n

Related Posts<\/span><\/strong><\/p>\n\n\n\n