Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Running Pega unit tests by adding the Run Pega unit tests task

Updated on February 4, 2021

If you use Pega unit tests to validate application data, add the Pega unit testing task on the pipeline stage where you want to run it. For example, you can run Pega unit tests on a QA system.

When you use separate product rules for test cases and run a pipeline, the Pega unit testing task is run for the access group that is specified in the Application test cases section, which you configure when you add or modify a pipeline.

To run Pega unit tests for either the pipeline application or for an application that is associated with an access group, do the following steps:
  1. Do one of the following actions:
    • Click a task, click the More icon, and then click either Add task above or Add task below.
    • Click Add task in the stage.
  2. In the task list, click Pega unit testing.
  3. Do one of the following actions:
    • To run all the Pega unit tests that are in a Pega unit suite for the pipeline application, in the Test Suite ID field, enter the pxInsName of the test suite.

      You can find this value in the XML document that comprises the test suite by clicking, in Dev Studio, ActionsXML on the Edit Test Suite form. If you do not specify a test suite, all the Pega unit tests for the pipeline application are run.

    • To run all the Pega unit tests for an application that is associated with an access group, in the Access Group field, enter the access group.

      For more information about creating Pega unit tests, see Creating Pega unit test cases.

  4. Click Submit.
  5. Continue configuring your pipeline. For more information, see one of the following topics:

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us