Customizable New Application wizard
Valid from Pega Version 7.2.2
The redesigned New Application wizard streamlines the process of creating and configuring applications, and introduces customizable application templates. When you create an application from an application template, the template defines the wizard steps that gather the information that is needed to configure your new application based on the template. After you specify the required information in the wizard, the system creates an application with the required case types, data types, access groups, and operators. You can create multiple templates, depending on the needs of your business. Sample template types are provided.
For more information, see New Application wizard.
Identify Pega unit test cases associated with inactive or deleted rules
Valid from Pega Version 8.2
From the Application: Unit testing landing page, you can view a list of all Pega unit test cases that are associated with inactive or deleted rules in the currently included applications. You cannot use these test cases because they will always fail.
Either remove such test cases, or reactivate the rules that they are associated with.
For more information, see Application: Unit testing landing page.
Merged test-coverage report improves overview of application quality
Valid from Pega Version 8.2
You can now merge multiple application-level test coverage reports from built-on apps into a single report. This single test-coverage report provides an overview of your application's quality, and eliminates the need to manually collate data from multiple reports.
For more information, see Generating a merged coverage report.
Updates to creating and cleaning the test data for automated tests
Valid from Pega Version 8.2
Creating test data for automated tests is now easier and more customizable. During test case or suite creation, you can now create objects, load work and data objects, and add user pages from the clipboard. These objects and pages can be further configured and will be available in the clipboard when you run the test.
For test cases, you can now define a separate set of actions to perform after the tested rule is run, such as applying a data transform, loading a data page or object, or running an activity,
You can also prevent test data from being removed from the clipboard after a test is run so that subsequent tests can use the same test data.
For more information, see Setting up your test environment and Cleaning up your test environment.