DocumentationExperience Cloud KCS

AEM solution for skipped custom UI tests in Cloud Manager caused by incorrect Docker context archive packaging

Last update: July 6, 2026

If Cloud Manager skips Custom UI Testing even though your tests run locally, the generated UI test Docker context archive might be packaged with the required files inside a parent directory instead of at the archive root. Verifying the archive structure and updating the Maven assembly configuration restores test detection in Cloud Manager.

Description description

Environment

Adobe Experience Manager as a Cloud Service

Issue/Symptoms

This issue usually appears when Cloud Manager cannot detect the UI test opt-in files in the generated Docker context archive.

  • The Custom UI Testing step shows a message similar to The UI tests have been skipped because no tests have been found in your source code repository.
  • Your Playwright, Cypress, Selenium, or other supported UI tests run locally, but no UI test execution appears in Cloud Manager.
  • The testing.properties file exists in the repository, but Cloud Manager still skips the tests.
  • You can confirm the issue by building the UI tests module and checking where testing.properties is stored inside the generated *-ui-test-docker-context.tar.gz file. Run tar -tvf target/*-ui-test-docker-context.tar.gz | grep testing.properties. If the result shows a path such as some-folder/testing.properties instead of just testing.properties, the archive is packaged incorrectly.
  • You can also confirm the configuration by checking that testing.properties is stored next to the pom.xml file in the UI tests module and contains exactly ui-tests.version=1.

Resolution resolution

Try the following steps to solve the issue:

  1. Confirm that the pipeline is using the correct Git branch for the UI tests module. The pipeline should use the branch that contains the ui.tests module and testing.properties. Confirm this in the pipeline configuration and in the next pipeline execution summary.
  2. Check that testing.properties exists next to the UI tests module pom.xml file and contains exactly ui-tests.version=1. You should see the file in the correct module with the required value. Confirm this directly in the repository.
  3. Build the UI tests module locally so that the Docker context archive is generated. You should see a file ending in -ui-test-docker-context.tar.gz in the module target directory. Confirm that the generated archive uses the ui-test-docker-context classifier.
  4. Inspect the generated archive and check whether testing.properties is stored at the archive root by running tar -tvf target/*-ui-test-docker-context.tar.gz | grep testing.properties. You should see only testing.properties with no parent folder prefix. If the output shows a path such as some-folder/testing.properties, the archive is packaged incorrectly. Continue to the next step.
  5. Update assembly-ui-test-docker-context.xml so the Docker context is packaged at the archive root. Make sure the assembly keeps <includeBaseDirectory>false</includeBaseDirectory> and includes testing.properties with the root-level files such as Dockerfile and wait-for-grid.sh. You should see the required files stored at the top level of the archive instead of inside a wrapper directory. Confirm this by rebuilding the module and repeating the archive inspection until testing.properties appears at the root.
  6. Commit the packaging changes, push them to the branch used by the pipeline, and run the pipeline again. The Custom UI Testing step should run instead of showing a skip message. Confirm this in the pipeline execution details and check that UI test logs are available.
  7. If the tests are now detected but fail during execution, review the UI test logs from the pipeline run and correct the test or framework-specific errors. Cloud Manager should detect and run the test image successfully. Confirm this by checking that the pipeline shows an actual UI test execution rather than a skipped step.

If the following symptoms occur and the troubleshooting steps produce the following results, submit a ticket to Adobe Support: the archive shows testing.properties at the root, the pipeline is using the correct branch, and Cloud Manager still reports that no UI tests were found.

Include the archive listing, the assembly-ui-test-docker-context.xml file, the UI tests module pom.xml, and the pipeline execution URL when you contact support.

recommendation-more-help
experience-cloud-kcs-help-kbarticles