Starting test coverage by adding the Enable test coverage task
Add the Enable test coverage task to start test coverage. Starting and stopping test coverage generates a report that identifies the executable rules in your application that are either covered or not covered by tests. As a best practice, to ensure application quality, you should test all the rules in your application for which testing is supported.
For more information about application-level coverage reports, see Generating an application-level test coverage report.When you use separate product rules for test cases and run a pipeline, the Enable test coverage 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 add this task, complete the following steps:
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.
In the Task list, click Enable test coverage.
Select the Start a new session check box to start a test coverage session every time that the pipeline runs the deployment. If you do not select this check box, if a test coverage session is already running, the pipeline pauses and returns an error.
Continue configuring your pipeline. For more information, see one of the following topics:
- Adding a pipeline on premises
When you add a pipeline on premises, you define all the stages and tasks that you want to do on each system. For example, if you are using branches, you can start a build when a branch is merged. If you are using a QA system, you can run test tasks to validate application data.
- Adding a pipeline on Pega Cloud Services
If you are using Pega Cloud Services, when you add a pipeline, you specify details such as the application name and version for the pipeline. Many fields are populated by default, such as the URL of your development system and product rule name and version.
- Modifying application details
You can modify application details, such as the product rule that defines the content of the application that moves through the pipeline.