Process Builder components are not cached during test execution, resulting in slow execution times for both Change Set and API (Ant, Eclipse) deployme
Last updated 2018-02-10 ·Reference W-4093518 ·Reported By 3 users
Process Builder flows have to be loaded into cache before each test execution. This can cause slow test performance resulting in long deployment times.
Please note, the associated fix is NOT available for customers by default.
To get this feature enabled, please raise a case with Salesforce support.
Initiate a deployment which contains Process Builder components that need to be tested.
Re-factor Process Builder flows one at a time (longest running after each re-factor) until deployment time is reduced.
Alternatively, if your Process Builder components are already tested you can use recent validation testing (https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/forcemigrationtool_deploy_validation.htm) to select which tests need to be run, and exclude tests related to Process Builder workflows. Also, consider excluding managed package tests that contain Process Builder components.
Is it Fixed?
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.