Validate solution upgrades in a test environment

Upgrading a solution changes its deployed components and configuration. Validating the upgrade in a dedicated test deployment before applying it to production reduces the risk of disrupting live users and requiring manual recovery.

Why validation matters before production

A solution upgrade can introduce the following changes in your environment:

• Newly added components that require additional setup before activation
• Removed components that may be referenced by other solutions or processes
• Edited components with changed property values that may override your existing configuration

If an upgrade fails in production, an automatic rollback attempts to restore the previous state. However, a failed rollback can leave some components in a degraded state that requires manual cleanup. Resolving issues in a test deployment before they reach production significantly reduces operational risk.

What a test deployment is

A test deployment is a deployment of the same solution package in a non-production environment — typically a separate tenant or a dedicated folder isolated from production users.

The test deployment runs the same package version as your production deployment. When a new package version is ready, you apply the upgrade to the test deployment first, verify it works correctly, and only then apply the same upgrade to production.

The test deployment does not need to replicate production data. Its purpose is to confirm that:

• The upgrade applies cleanly without component conflicts
• New components are configured correctly
• The deployment activates and runs as expected

Test-then-promote pattern

The recommended approach follows a test-then-promote sequence:

• Test deployment — The test deployment receives the target package version first. Component differences (added, removed, or modified) are reviewed and any required configuration is completed before activation.
• Validation — The test deployment is activated and the solution is verified to behave as expected.
• Production deployment — The same package version is applied to production. Issues identified during testing are already resolved, so the production upgrade proceeds with lower risk.

For step-by-step upgrade instructions, see Upgrading or downgrading a solution.

Related resources

• Up- oder Downgrades einer Lösung durchführen
• Bereitstellen einer Lösung
• Bereitstellungsstatus