Summer '25 lets you run Flow Tests from the Salesforce CLI with the new sf flow run test command, which puts them within reach of CI/CD and automated regression runs.
Run Flow Tests from the CLI
Summer '25 adds a CLI command for executing Salesforce Flow Tests: sf flow run test. Teams can run flow unit and regression tests from local scripts, CI pipelines, or release automation, rather than starting each one by hand in Flow Builder.
Why this matters
Automated flow tests catch errors earlier and take the manual effort out of a release. If you already run DevOps pipelines, adding Flow Tests to CI/CD means flows get checked before they reach production.
How to use
- Open your terminal in a Salesforce DX project or authenticated org.
- Run:
sf flow run test. This executes all flow tests available in the org. - Wire the command into CI jobs (GitHub Actions, GitLab CI, Jenkins) so tests run during builds or before deployments.
Best practices
- Keep flow tests small and focused so failures point to specific behavior.
- Combine with source-driven development: run tests on feature branches and pull requests.
- Fail fast in CI: abort the deployment on a test failure and surface clear logs for developers.
Typical uses are regression testing after a flow change, validating flows during a release pipeline, and nightly suites behind a quality gate.
Next steps
If you haven't already, add flow tests in Flow Builder, then wire the sf flow run test command into your pipeline. Since Summer '25, flow testing can live in the same pipeline stage as everything else you ship.
Admins, developers and release engineers all get the same thing out of it: less manual testing, and a deployment you can trust a bit further.
#SalesforceSummer25 #Flows #DevOps #CI #Salesforce
For more, please follow our page!
Leave a Comment