Improve application test coverage by running multiple sessions
Valid from Pega Version 8.1
You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see the Test Coverage landing page.
Use repositories as sources for File data sets
Valid from Pega Version 8.1
You can configure remote repositories, such as Amazon S3 or JFrog Artifactory, or a local repository, as data sources for File data sets. By referencing an external repository from a File data set, you enable a parallel load from multiple CSV or JSON files, which removes the need for a relational database for transferring data to Pega Platform™ in the cloud.
For more information, see Creating a File data set record for files on repositories and Configuring a remote repository as a source for a File data set.
Define a taxonomy by using the Prediction Studio interface
Valid from Pega Version 8.1
Create a topic hierarchy and define keywords for each topic in Prediction Studio faster and more intuitively than by editing a CSV file. If you have already defined a taxonomy in a CSV file, you can import that file and modify existing topics and keywords by using the Prediction Studio interface.
For more information, see Creating-keyword-based topics for discovering keywords and Tutorial: Configuring a topic detection model for discovering keywords.
Pega unit test suites are now modular
Valid from Pega Version 8.1
It is now possible to include test cases and test suites inside test suites. This feature makes test suites modular and improves the management of cases while creating, modifying, and executing them for regression testing.
For more information, see Pega unit test suites.
REST API now fetches the latest version of Application Quality metrics
Valid from Pega Version 8.1
When you request Application Quality metrics by using the REST service, the service requests a refresh of the metrics. This means that you always get the latest version of the metrics and can decide whether your application is ready for deployment based on that information.
For more information, see Pega API.
Parameter page is automatically removed after each Pega unit test run
Valid from Pega Version 8.1
The parameter page is automatically removed after each Pega unit test run. The reliability of subsequent tests is increased because they are not influenced by leftover parameter values that were set by the previous test.
For more information, see Cleaning up your test environment.
Start and stop a coverage session by using the REST API
Valid from Pega Version 8.1
You can now start and stop application-level test coverage by using REST services. You can use the results of the coverage session for gating purposes in a release pipeline.
For more information, see Pega API.
Improved performance of decision strategies
Valid from Pega Version 8.1
Strategy rule performance has been improved through the implementation of a new engine. You can perform single and batch test runs to analyze strategy performance, locate and prevent potential issues, and optimize strategy components. Test runs now support data sets and data flows with multiple key properties. The redesigned Test run panel improves the display of information and highlights the most immediately relevant details.
For more information, see Configuring a single case runs and Configuring a batch case runs.
Extract summaries from the analyzed text
Valid from Pega Version 8.1
You can now configure a Text Analyzer rule to extract information-rich blocks of text from the analyzed content and combine them into a comprehensive and coherent summary. By summarizing large documents, such as emails, you can facilitate making business decisions without having to read an entire document. In Text Analyzer rules, you can combine summarization with other types of text analysis, such as topic or entity detection, to extract the full context from a message.
For more information, see Configuring text extraction analysis and Tutorial: Extracting email context with Text Analyzer rules.
More quality metrics on the Application Quality dashboard
Valid from Pega Version 8.1
On the Application Quality dashboard, for each case type you can now view quality metrics such as guardrail score, test coverage percentage, unit test pass rate, list of guardrail of warnings, uncovered rules, and failed Pega unit tests. These metrics are also available for rules that are used in the application but that are not a part of any case type. To access these metrics, on the Application Quality dashboard list of case types, click Find issues.
For more information, see Application Quality landing page.