DocumentationExperience Cloud KCS

Configure Cypress tests in AEM Cloud Manager for QA without enforcing in production

Last update: October 6, 2026

This article explains how to configure Adobe Experience Manager Cloud Manager pipelines to run Cypress UI tests in QA environments without enforcing them as a deployment gate in production.

Description description

Environment

Adobe Experience Manager (AEM) as a Cloud Service (all versions)

Issue/Symptoms

  • Cypress automation tests are needed in QA (non-production) environments but should not block deployments in production.
  • Adding test/cypress in pom.xml causes Cypress tests to be enforced in all environments, including production.
  • Cypress tests should be optional in QA/non-production pipelines.
  • Cypress test failures should not halt production deployments.

Cause

Cloud Manager enforces Custom UI Testing as a required quality gate in production pipelines when enabled, but allows it to be optional in non-production pipelines. There is no current feature to allow test failures to be ignored in production deployments.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Enable Cypress testing in non-production pipelines (QA/Dev) by configuring the pipeline to include the Custom UI Testing step.
  2. Refer to the official Adobe Experience Manager Cloud Manager documentation for guidance on configuring non-production pipelines.
  3. Do not enable the Custom UI Testing step in production pipelines if Cypress test failures should not block deployments.
  4. If Cypress tests must remain in the codebase, ensure that the Custom UI Testing step is not enabled for the production pipeline.
  5. Verify that Cypress tests run in non-production pipelines and do not block production deployments.
recommendation-more-help
experience-cloud-kcs-help-kbarticles