Merge application-level test reports by using the Pega API service
Valid from Pega Version 8.5
A new REST API is now available so that you can merge test coverage reports at the application level without having to perform this task manually. This service accepts the application IDs for the test coverage reports that you want to merge and generates a consolidated report in the target application provided.
For more information about setting up your environment and making API calls with Deployment Manager, see the Documentation/readme-for-swagger.md file in the DeploymentManager04_08_0x.zip file, found in the Deployment Manager download package.
Improvements to scenario testing for increased efficiency
Valid from Pega Version 8.5
Several enhancements have been made to scenario tests for increased test efficiency. See below for a list of these improvements.
- Scenario testing now supports multiple actions per run, and all events that are configured as part of a scenario test are now triggered sequentially. Previously, only the first event was triggered, and the system ignored the rest.
- If a scenario test encounters a JavaScript error at any point during the run, the system immediately stops the tests. Refer to the logs for a detailed description of the error.
- Actions can now be configured and recorded on custom components in the scenario testing tool.
For more information, see Creating UI-based tests with scenario testing.
Improving basic access control
Valid from Pega Version 8.5
Pega Platform™ has implemented a new basic access control (BAC) to protect your application from unauthorized server calls from otherwise authenticated users.
For more information, see Access Control Checks.
Upgrade impact
After you upgrade to Pega 8.5, all the functionality in the model configurations that use auto-generated controls and actions continues to work as before. However, you must secure any customized JavaScript in your application layer that makes AJAX (server) calls by using registration or encryption mechanisms.
What steps are required to update the application to be compatible with this change?
After upgrade, to migrate custom JavaScript functionality, see Access Control Checks.