While deploying non apex component if testLevel is set to "RunSpecifiedTests" then deployment fails if any Trigger has less than 1% code coverage

While deploying non apex component if testLevel is set to "RunSpecifiedTests" then deployment fails if any Trigger has less than 1% code coverage

Apex , Summer 15

Last updated 2016-07-28 ·Reference W-2650930 ·Reported By 1 users

Fixed - Winter '16

Summary
In summer 15 release ,the "runAllTests" deployment option is now replaced with "testLevel". Test levels enable you to have more control over which tests are run in a deployment. The default Test Execution in Production has changed ,When no test level is specified in the deployment options, the default test execution behavior depends on the contents of your deployment package.
- When deploying to production, all tests, except those that originate from managed packages, are executed if your deployment package contains Apex classes or triggers.
- If your package doesn’t contain Apex components, no tests are run by default.

But if you are not deploying any apex component and still want to run specific test classes in <runTest> tag while using "RunSpecifiedTests" for testLevel, then deployment fails if any trigger has less than 1% code coverage for both WorkBench and Force.com Migration Tool

PLEASE NOTE- When there are apex components in the deployment package and using testLevel="RunSpecifiedTests" and <runTest> tag specify test classes , deployment is successful even if any trigger has less than 1% code coverage , if that trigger test class is not specified in the <runtest> option , so please check your code coverage if you get this error.

Reference

http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_deployment_run_subset_of_tests.htm?edition=&impact=
http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_api_meta_new_calls.htm#testlevels

Repro
Example- The destination org has one trigger (LeadHtmlError) which has no code coverage and deployment package only contains profiles.

package.xml
-------------
<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">

<types>
<members>*</members>
<name>Profile</name>
</types>
<version>34.0</version>

</Package>

failing build. XML snippet
----------------------------

<target name="deployCodenonapexcompwithtest">
<sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="nonapexcomp" checkOnly="true" testLevel="RunSpecifiedTests">
<runTest>ChangePasswordController</runTest>
</sf:deploy>
</target>

Actual Results
------------------
BUILD FAILED
C:\Users\<user>\Documents\migration tool\sample\build.xml:98:
*********** DEPLOYMENT FAILED ***********
Request ID: 0AfM0000009UDOgKAO

Code Coverage Failures:
1. Class: LeadHtmlError -- Test coverage of selected Apex Trigger is
0%, at least 1% test coverage is required
*********** DEPLOYMENT FAILED ***********


Expected behaviour
-------------------
RunSpecifiedTests—Only the tests that you specify in the runTests option are run. Code coverage requirements differ from the default coverage requirements when using this test level. Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage
as there were no apex component so no code coverage should be in-forced.

Workaround
1) For deploying production org

<target name="deployCodenonapexcompwithtest">
<sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="nonapexcomp" checkOnly="true>
</sf:deploy>
</target>

2) For Sandbox production org

<target name="deployCodenotest">
<sf:deploy username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" deployRoot="nonapexcomp" checkOnly="true" testLevel="NoTestRun">
</sf:deploy>
</target>

Reported By (1)

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP14 AP15 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS110 CS11 CS116 CS12 CS137 CS138 CS13 CS14 CS15 CS152 CS151 CS16 CS17 CS18 CS19 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU9 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 NA104 NA100 NA101 NA103 NA102 NA105 NA129 NA130 NA132 NA131 NA21 NA32 NA33 NA37 NA39 NA40 NA42 NA44 NA45 NA46 NA47 NA49 NA50 NA51 NA52 NA53 NA54 NA56 NA57 NA58 NA59 NA60 NA61 NA62 NA63 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA78 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.