Salesforce
Salesforce DevOps Center and DevOps Testing Explained

Rishabh Kumar
Published On

Table of contents
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
What are Salesforce DevOps Center and DevOps Testing?
Salesforce DevOps Center is Salesforce’s own tool for tracking changes as work items and moving them through a pipeline of environments, backed by source control. Its testing layer lets teams group tests from Salesforce and partner providers into suites, assign those suites to pipeline stages, and set quality gates that decide whether work can move forward.
The testing layer has changed shape quickly. Salesforce first released it in 2025 as DevOps Testing, an extension to DevOps Center. In Next Generation DevOps Center, testing is built in, with no separate installation.
Either way, the same caveat applies. A quality gate is only as strong as the tests plugged into it, and the end-to-end journey layer still has to come from somewhere.
How DevOps Center works
DevOps Center replaces change sets with a more disciplined, source-controlled way of moving work through environments, without forcing admins to become Git experts.
Work items: Each change, such as a new field, a flow update or an Apex class, is tracked as a work item with a description and an owner.
Source control underneath: DevOps Center records changes in a connected repository, so there’s a history of what changed, when and by whom.
Pipelines: Teams define the stages changes move through, typically development, integration, UAT and production, and promote work stage by stage.
Clicks or code: Admins use a point-and-click interface, while developers work in their usual tools against the same repository.
DevOps Center is free to install, which has made it the default first step for teams leaving change sets behind.
How Testing Works Inside DevOps Center
Concept | What it means |
|---|---|
Test providers | Where tests come from. Salesforce’s own include Apex unit tests, Flow tests and Code Analyzer, with Scale Test and Agentforce Testing Center also offered. Partner providers named by Salesforce include ACCELQ, Copado, Panaya, Provar, Quality Clouds and Tricentis, with some still listed as coming soon for Next Generation DevOps Center. |
Test suites | Groups of tests from one or more providers, defined once and reused |
Stage assignments | Which suites run at which stage, so fast checks run early and broader suites later |
Quality gates | Rules that decide whether work may move on, such as all tests passing, a minimum pass rate, a severity threshold, or every essential test passing |
Activity history | A record of every test event, result and gate decision across the pipeline |
Suites run automatically on key pipeline events, such as when a review is created or before a promotion completes. If a gate’s rules aren’t met, the promotion stops.
What Native Covers, and Where it Stops
DevOps Center does well | What it leaves to you |
|---|---|
Tracks every change as a work item, with source-controlled history | Deciding which business journeys a change puts at risk |
Moves work through stages consistently | Testing changes that never pass through the pipeline |
Runs tests from several providers in one place | Writing and maintaining the end-to-end journeys those providers run |
Enforces quality gates on work items | Proving journeys that cross into ERPs, policy platforms, portals and other systems |
Keeps a history of what ran against each work item | A release-level account of what was tested, why, and who decided |
The second row is the one teams underestimate. DevOps Center sees the changes your team makes. Three times a year, Salesforce changes the platform underneath you.
Release updates switch on by date. Connected systems change on their own calendars. None of that arrives as a work item, so a test strategy that only runs on promotion simply never sees it.

Release updates are the change teams forget most often, because they switch on by date rather than by deployment. Our guide to testing Salesforce release updates shows how to catch them before they're enforced.
Which Tests Belong at Which Stage
Gates work best when each stage asks a different question.
Stage | The question | Typical suites |
|---|---|---|
Review created | Is the change well formed? | Code Analyzer, Apex unit tests for touched classes |
Integration | Does it break anything nearby? | Apex and Flow tests across the package, a small set of end-to-end smoke journeys |
Does the business process still work? | Full end-to-end journeys for affected processes, run as each persona | |
Before production | Is this release safe to ship? | The release regression pack, plus any journeys a reviewer marked essential |
Between promotions | Has anything changed underneath us? | The same journeys on a schedule, and on every sandbox preview |
The last row sits outside the pipeline on purpose. It’s the one that catches Salesforce releases and connected-system changes.
Choosing which regression tests run at each stage, so early gates stay fast and later gates stay thorough, is covered in CI/CD regression testing.
Where Virtuoso QA Fits in a Devops Center Setup
Virtuoso QA supplies the end-to-end journeys that make the UAT and pre-production gates meaningful, and keeps them running between promotions.
Journeys are triggered from the source-control pipeline alongside DevOps Center, using generated CI/CD scripts, the Virtuoso QA API or webhooks, and the result decides whether work moves on. The same journeys also run on a schedule and on each sandbox preview, so platform releases and connected-system changes get tested even though they never become work items. Because journeys follow processes across Salesforce and connected web applications and APIs, a quote that should become an ERP order is checked all the way through. Touchstone’s proposals, approvals and versions are recorded alongside run results, so the gate decision has a trail behind it.
One honest note. Virtuoso QA isn’t currently a named partner provider for DevOps Center testing, so it doesn’t appear in the provider list. It connects through the pipeline instead.
Virtuoso QA's Salesforce test automation runs end-to-end Salesforce journeys from your pipeline, on every sandbox preview and on a schedule, and records what each gate decision was based on.
Related Reads
Frequently Asked Questions
What is Salesforce DevOps Center?
Do I Need to Install DevOps Testing Separately?
Which Test Providers Work with DevOps Center Testing?
Is DevOps Center a Replacement for Copado or Gearset?
Do Quality Gates Replace End-to-end Testing?
Written by

Rishabh Kumar
AI Testing & Quality Engineering Contributor
Rishabh leads business development and marketing at Virtuoso QA. He writes about AI-powered test automation, end-to-end testing, self-healing tests, and quality engineering, exploring how these capabilities can improve test coverage, reduce test maintenance, and support reliable software releases.










