Links may not function; however, this content may be relevant to outdated versions of the product.
Managing test cases separately in Deployment Manager
In Deployment Manager 4.4.x and later, you can package and deploy test cases separately on the candidate systems in the pipeline. When you configure a pipeline in Deployment Manager, you specify the details of the test package that you want to deploy, including the stage in the pipeline until which you want to deploy the package.
To use a separate test package, you must create a test application layer on the development systems in your pipeline.
- Configuring the application stack on the development or source development system
You must first configure your application stack on either the development or source development system.
- Configuring the application stack on the remote development system in a distributed, branch-based environment
If you are using a distributed, branch-based environment, you must configure the application stack on the remote development system.
- Using branches and test cases
Branches in the development application can contain rulesets that belong to the target application, test application, or both. When you start a deployment either by using the Merge Branches wizard or by publishing a branch to a repository on the main development system, the branches in both the target and test applications are merged in the pipeline.
- Configuring pipelines to use test cases
When you add or modify a pipeline, you specify whether you want to deploy test cases and then configure details for the test application, including its name and access group to which it belongs, in the Application test cases section. You also select the stage until which you want to deploy the pipeline. For more information about using Deployment Manager, see .
Previous topic Using branches with Deployment Manager Next topic Configuring the application stack on the development or source development system