Force Unit Tests Pass Before Promoting to Next Stage

[kfidelak94]

^{Originally posted by **matthewpomar** February 18, 2022} Hi, Is there a way to automatically ensure all unit tests pass before changes are merged into the integration stage/branch? For example, an admin creates a validation rule that breaks 14 processes/flow/triggers and 30 Apex tests. The validation rule is promoted from the admin's development sandbox to the integration sandbox. The tests all fail in that integration environment now and other admins/developers are unable to test their changes there. Would be nice to force all Apex tests pass before a change is allowed into the integration stage (or any stage of choice).

[geomuck]

For sure! If you specify a different test option during deployment, you can choose to run whatever tests you like! Take a look at these links and see if they make sense, and follow up here with any additional questions?

https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/forcemigrationtool_deploy.htm#ant_deploy_testLevel https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_run_local_tests.htm

[matthewpomar]

Thanks @kfidelak94 @geomuck.

I understand that using tools like the Migration Tool and other metadata deployment tools, one has an option to run tests. What I mean is, from the perspective of setting up a stage, e.g. Integration, is there a way to force any and all changes that get deployed to that stage to run and pass tests before that change is accepted. Please see my example in the original post.

Thanks again.

[geomuck]

Oh I misunderstood. Good suggestion! That doesn't exist today (obviously), but we'll take it as an idea for an enhancement, thank you!

[uip-robot-zz]

This issue has been linked to a new work item: W-10752338

[Szandor72]

This would be super helpful. I think this would also mostly cover 'out of the box CI'