Salesforce DevOps Testing is now generally available — and it’s here to help teams move faster without sacrificing quality. Built to work seamlessly with DevOps Center, DevOps Testing simplifies testing across your pipeline, ensuring that all changes made by your development teams meet your company’s quality standards before they can be deployed to production.

In this post, we’ll introduce you to DevOps Testing and show you an example of how DevOps Testing can be used with a range of different testing tools to thoroughly test your solutions.

What is Salesforce DevOps Testing?

Salesforce DevOps Testing extends DevOps Center with a unified strategy for automated testing. It brings together Salesforce tools like Code Analyzer v5 and Scale Test (with support for Apex Unit Tests, Flow Tests, and Agentforce Testing Center coming soon) and partner tools from ACCELQ, Copado, Panaya, Provar, Quality Clouds, and Tricentis. You can run everything from static code analysis to full regression tests within a single workflow.

DevOps Testing is the single source of truth for test definitions and test results, where you can define your test strategy across multiple tools, run tests automatically, and enforce quality gates to keep only high-quality changes moving forward.

This means that your teams are empowered to find issues earlier in their solutions and fix them well before any bugs make their way to production, where they are expensive to fix.

Finally, DevOps Testing is especially powerful when testing Agentforce before you deploy your agents. You’ll be able to not only run Agentforce Testing Center unit tests, but also comprehensively test Apex and Flow actions thanks to Code Analyzer v5 and our integration with Apex Unit Tests and Flow Tests. Our partner tools complement this even further with rigorous end-to-end testing.

Set up DevOps Testing

Let’s run through an example of a DevOps Testing setup. In this example, we’re using DevOps Center with a pre-configured “TDX25” project. This project has a pipeline with a number of development sandboxes, followed by integration, UAT, staging, and finally, our production environment.

Our TDX25 project uses the Coral Cloud Resorts sample app as a foundation. The sample app has been deployed in our development sandboxes and we’re now making changes to it ahead of deploying to production.

DevOps Testing is available as a managed package on AppExchange. You should install it in the same org where DevOps Center resides. Once you’ve installed it, you just need to assign permission sets to the following users:

• DevOps Testing Manager: For test managers who oversee the test strategy
• DevOps Testing User: For anyone running tests or reviewing results

Once permission sets are assigned, users will find the DevOps Testing app in the App Launcher.

Now, your users can go to the Test Providers tab and click “New.” Once you select the TDX25 DevOps Center project, you have a list of test providers you can choose from.

You can see that we already added and configured a number of test providers: Agentforce Testing Center, Apex Unit Tests, Copado Robotic Testing, Code Analyzer v5, and finally, Scale Test.

When you add a new test provider, DevOps Testing automatically synchronizes the various tests and test suites (groups of tests) between the selected test provider and DevOps Testing. You can track this sync process in the Test Provider Sync Histories tab.

You can look at your Test Suites tab and see all the test suites that are available.

Each test suite groups related tests; for example, you might have one for regression in staging and another for code quality checks in integration. Inside each suite, you’ll find individual tests, each of which can be assigned a severity level and marked as “essential” if it must pass before proceeding.

For instance, you can look at the CodeStyle test suite from Code Analyzer v5 and view its related list to find individual tests.

Tests from Code Analyzer v5 come with built-in severity levels (1 is most critical, 5 is least), and DevOps Testing uses those same levels. For test providers that don’t include severity, DevOps Testing assigns a default value — but you can always change it manually for any test.

Once your test providers are set up, the next step is assigning test suites to run automatically at different pipeline stages. Let’s look at an example of how we’ve done this in the Stage Assignments screen.

Here, we added three test suites to our Work Item: Review stage. This means that whenever a work item for this project enters the “Create Review” stage in DevOps Center, DevOps Testing will automatically run these test suites. You can easily add more by clicking “View” and “Assign Test Suites.”

We added three test suites: a regression suite from Copado Robotic Testing, a security suite from Code Analyzer v5, and tests from Agentforce Testing Center. Code Analyzer test suites are environment-specific, so this one uses settings from the next stage in the pipeline: our Integration sandbox.

For each suite, we applied the quality gate rule “All tests must pass” to ensure that only high-quality code moves forward.

Quality gates let you define what “good enough” means. Want all tests to pass before code moves forward? Set that as a rule. You can mix and match based on severity, pass rate, or essential tests — customizing your definition of quality for each pipeline stage.

That’s your configuration done! DevOps Testing is ready to automatically run tests and evaluate quality gate rules.

Test DevOps Center work items

We’re assuming that you’re already quite familiar with DevOps Center. As your low-code and pro-code developers collaborate to implement a project, they’ll create work items, allowing them to check in their changes to source control.

Let’s imagine that, as part of the TDX25 project, your developers have been working on a weather service API integration that helps Agentforce get real-time weather information for the Coral Cloud Resorts sample app.

When you take a work item that has been committed and click “Create Review,” you’ll get a new message that tests are still running or haven’t passed:

That means that DevOps Testing is hard at work! In the background, DevOps Testing is now running the three test suites configured previously, so you can go back to the DevOps Testing app and check their status in real-time in the “Test Suite Execution Groups” tab:

Here you can see a history of previous test runs with different statuses. The last one is the one we care about, so let’s find out more about it.

If you click through to the related tab, you can see individual results for each test suite, the associated work item, and detailed information on quality gates that were evaluated.

Finally, you can go one level deeper and view details for each test suite. For instance, if we select the Security test suite, we see the following:

You can see a summary chart showing test statuses, split by severity level, as well as a number of tabs where you can see full results and additional details. If a Code Analyzer v5 test had failed, you’d know exactly where the issue is in the codebase, so your developer can fix it manually or use Code Analyzer’s AI-powered quick fix.

That’s it! With DevOps Testing and its range of testing tools, your team is empowered to deliver high-quality solutions seamlessly.

Conclusion

DevOps Testing is more than just a new product — it’s a smarter way to build. Automate quality checks, reduce release risk, and free up your team to focus on what matters: delivering great experiences faster. Try it out and see how much smoother your DevOps flow can be.

Ready to elevate your development process and achieve higher levels of quality? Check out our resources section below and get started with Salesforce DevOps Testing!

Resources

DevOps Center documentation
DevOps Testing documentation
Code Analyzer v5 documentation
Salesforce+ session on Create Faster and Better Code with AI Tools
Salesforce+ session on Tools to Build, Test, and Release Agentforce

About the author

John Belo is Director, Product Management for Developer Experience Products, leading the Application Lifecycle Management product space within the team, including Testing, Observability, and DevOps. He oversees products such as Salesforce Code Analyzer v5, DevOps Testing, and Package Migrations (helping ISV partners move from 1st generation managed packaging to 2nd generation). He’s been with Salesforce for ten years and spent the majority of this time within the AppExchange team. He started by leading a team of ISV Technical Evangelists in EMEA, and is now part of the Developer Experience Product Management team, helping developers to deliver quality solutions faster than ever.