Improve Release Quality with Lifecycle Center Testing
Learning Objectives
After completing this unit, you'll be able to:
- Explain what Lifecycle Center Testing is and how it fits into the Lifecycle Center pipeline.
- Describe the two phases of automated testing and when each one is triggered in the pipeline.
- Identify when to use On-Demand Testing and how it helps your team respond to a failed test run.
It’s release day. Your team has been building for weeks. There are new features, bug fixes, and configuration changes all moving through the pipeline together. The release manager clicks Promote in Lifecycle Center, previously named DevOps Center. Instead of crossing their fingers and hoping nothing breaks in Production, they already know the answer. Every test and quality gate has passed. The code sailed through every pipeline stage.
Lifecycle Center Testing makes it the standard.
What Lifecycle Center Testing Does
Lifecycle Center Testing is built into Lifecycle Center—no separate installation or enablement required. Lifecycle Center Testing embeds automated and manual testing directly into your Lifecycle Center pipeline. Lifecycle Center Testing enforces quality at every stage—from the moment a developer creates a review to the final promotion into production.
Instead of relying on post-deployment fixes or manual sign-off processes, Lifecycle Center Testing gives your team a systematic way to enforce release standards at every checkpoint. It runs tests automatically and blocks substandard changes before they ever reach your customers.
Automated testing happens in two phases.
- Left-shift testing: Your test runs the moment a developer creates a review in DX Inspector. When you catch issues early—before code enters the shared pipeline—you fix them faster, cheaper, and with less disruption to the rest of the team.
- Testing before promotion: Your test runs automatically before code advances from one pipeline stage to the next. Each stage—integration, staging, and production—can enforce discrete quality standards, which ensures only validated changes reach your environments.
When automated testing fails because quality gate criteria aren't met, an execution error occurs, or a configuration issue arises, on-demand testing lets you manually verify whether tests are passing. A new test execution runs automatically when the promotion is attempted.
How Lifecycle Center Testing Works for You
Imagine you're a release manager at a financial services company, and your team is preparing a major update to your customer portal. The pipeline includes development, integration, staging, and production stages—and any bug that reaches production means costly downtime and frustrated customers. Here's how Lifecycle Center Testing keeps quality intact at every step.
During development: A developer finishes building a new payment validation flow, commits the changes, and creates a review in DX Inspector. The moment the review is created, left-shift testing automatically runs the test suites that the DevOps Testing Manager assigned to the development stage. The results come back with a failure—one of the essential tests for payment processing didn’t pass. The developer sees the details, fixes the logic, commits the update, and the next review triggers a clean pass that moves changes to the integration stage. The defect never made it into your team’s shared pipeline.
Before promotion: The work item is marked as Ready to Promote and the team initiates the move from integration to staging. Before the promotion completes, Lifecycle Center Testing automatically runs the test suites that the DevOps Testing Manager assigned to the staging stage—this time including Code Analyzer test provider, which applies stricter security scanning than the development stage. All quality gates criteria pass and the promotion proceeds.
When something goes wrong: A prepromotion test run fails in the staging stage due to a configuration error. The promotion is blocked. The release manager uses on-demand testing to manually verify that the issue is resolved. Then the team retries the promotion, and a fresh automated execution runs which gives them confidence before the change reaches production.
With testing built in from the very first review, good quality code moves through the pipeline faster, your team spends less time running manual checks, and there are no last-minute surprises on release day—because the hard work was already done at the start.
Everything Your Team Needs to Release with Confidence
Lifecycle Center Testing also provides these capabilities to help your team maintain release quality consistently.
- Multi-provider support: Connect native Salesforce providers—Apex Unit Testing, Flow Tests, and Code Analyzer—or certified partner tools to different pipeline stages to build layered quality coverage across your entire pipeline.
- Flexible quality gate rules: Create quality gate rules that define exactly what it means to pass—minimum test pass percentages, severity level thresholds, or essential tests that must never fail. Assign rules to test suites at each stage and let the system do the enforcement.
- Test suite group execution: When Lifecycle Center Testing detects a Review Event or Pre-Promotion Event, all assigned test suites run together as a single coordinated job. Monitor live execution status and drill into individual test suite results from the Related tab.
- Activity history for testing: View every test event, execution result, and quality gate decision in Tests Activity History, which gives your team a complete audit trail across all pipeline stages.
Get Started with Lifecycle Center Testing
To start enforcing quality automatically in your pipeline, make sure you:
- Have an active pipeline with at least one stage configured.
- Connect and sync your test providers.
- Assign test suites to your pipeline stages.
- Configure quality gates for the stages where you want enforcement.
After these are in place, automated testing triggers automatically every time a developer creates a review or promotes code to the next pipeline stage. That means less time spent on manual verification before every release, and more time building. Your team moves faster because quality enforcement happens automatically.