Improvements for test cases and assertions
Valid from Pega Version 8.4
The process of modifying test cases and assertions has been improved. Adjusting test cases to application changes is now much easier.
You now can:
- Select a page on which to run a tested rule.
- Change the class and rule of unit test cases.
- Create assertions that validate specific error messages on pages, properties, and activities.
- Automatically update decision result assertions with property changes made to a rule.
- Modify a rule's properties directly from decision result assertions.
For more information, see:
- Updating scenario tests
- Setting up your test environment
- Configuring page assertions
- Configuring property assertions
- Configuring decision result assertions
Simulation of data pages and third-party connections
Valid from Pega Version 8.4
When configuring your unit test case environment, you can now set up simulated data for connector and data page rules, instead of connecting to external sources.
By simulating such data calls, you are not dependent on any third-party server when running your tests.
This feature supports the following rules:
- Data page
- Connect-Cassandra
- Connect-CMIS
- Connect-dotNet
- Connect-EJB
- Connect-HBase
- Connect-HTTP
- Connect-Java
- Connect-JMS
- Connect-MQ
- Connect-REST
- Connect-SAP
- Connect-SAPJCo
- Connect-SOAP
For more information about simulating third-party connections, see Simulating data pages and third-party connections.
New branch quality dashboard
Valid from Pega Version 8.4
Pega Platform™ 8.4 introduces a new branch quality dashboard that shows the following metrics:
- The branch’s guardrail compliance score and the number of guardrail violations
- The percentage and number of unit tests that passed for the branch
- The percentage and number of rules that the tests cover
- Potential merge conflicts that can be addressed directly from the branch quality dashboard
For more information about the new branch quality dashboard, see Viewing branch quality and branch contents.
Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6
Valid from Pega Version 8.6
Upgrade impact statement
On-premises upgrades of Pega Infinity release 8.4.2 and later to version 8.5.1 or later on Tomcat and PostgreSQL are completed with near-zero downtime. However, upgrading to Hazelcast 4.x requires that you shut down and restart your application server.
What is required to update the application to be compatible with this change?
Hazelcast 3.x is enabled by default. For near-zero downtime upgrades, you do not need to perform any action.
For instructions about upgrading to Hazelcast 4.x, see one of the following topics:
- For near-zero downtime upgrades from Pega Infinity release 8.4.2 or later on Tomcat and PostgreSQL, see "Optional: upgrading to Pega Platform version 8.6: Upgrading to Hazelcast 4.x" in Near-zero downtime Upgrade Guide for Pega Platform version 8.4.2 and later for Tomcat and PostgreSQL.
- For all other upgrades, see "Optional: upgrading to Hazelcast 4.x" in the appropriate upgrade guide.
Extend PegaUnit setup and cleanup capabilities using custom fixtures
Valid from Pega Version 8.6
The set up and clean up capabilities in the PegaUnit framework are now customizable through the use of custom fixtures. Custom fixtures extend the default testing functionality and allow you to define and implement specific runtime actions, such as running a specific test case during set up or sending an email after testing has completed execution.
For more information, see Setting up and cleaning the context for a test case or test suite.
Improved indexing of StringList and StringGroup property types
Valid from Pega Version 8.6
Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.
Upgrade impact
After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed.
What steps are required to update the application to be compatible with this change?
On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.
For more information, see Indexing class data.