Table of Contents

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 main development system

Configure the application stack according to one of the following scenarios:

  • If you are using a distributed, branch-based environment, complete the following steps on the remote development system.
  • If you are using a branch-based environment, complete the following steps on the development system.
  • If you are not using branches, complete the following steps on the development system.

Configure the application stack by performing the following steps:

  1. Create the target application.
  2. Create a test application, which contains the test rulesets that you want to separately deploy, that is built on the target application.
  3. Create a development application that is built on top of the test application, which developers can log in to to create and work in branches, .
  4. Lock both the target and test applications

Configuring the application stack on the remote development system in a distributed, branch-based environment

If you are using a distributed, branch-based environment, complete the following steps on the remote development system:

  1. Create the target application.
  2. Create a test application, which contains the test rulesets that you want to separately deploy, that is built on the target application.
  3. Lock both the target and test applications.
  4. Lock both the target and test application rulesets.

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 the Using Deployment Manager article on Pega Community for your version of Deployment Manager.

    When you use separate product rules for test cases and run a pipeline, the Run Pega unit tests, Enable test coverage, and Validate test coverage tasks are run for the access group that is specified in the Application test cases section.

    You must also perform the following steps on the candidate system on which you are running tests:

    1. Log in to the test application.
    2. in Dev Studio, click Configure > Application > Quality > Settings.
    3. Select the Include built-on applications radio button, and then click Save.

    For the Run Pega scenario tests task, the user name that you provide should belong to the access group that is associated with the test application.

     


    Related Content

    Have a question? Get answers now.

    Visit the Pega Support Community to ask questions, engage in discussions, and help others.