Scenario tests now honor application stack settings
Valid from Pega Version 8.5
The application stack defined on the Application Quality Settings page of Dev Studio now serves as a foundation for creating, viewing, and running scenario tests.
Dev Studio will now:
- Display scenario tests based on the application stack settings on the Dev Studio landing page.
- Store scenario tests with the configured stack settings.
- Report metrics in the application quality dashboard with respect to the configured stack settings.
For more information, see Creating UI-based tests with scenario testing.
Support for nested Declare Trigger rules
Valid from Pega Version 8.5
Pega Platform™ now supports nested Declare Trigger rules so that you can conveniently create correlations between actions in your case types. Declare Triggers rules invoke an action when a specified event takes place in a case type. You can now design more complex scenarios faster by nesting more Declare Trigger rules that work in the context of running another Declare Trigger rule. For example, when a case participant changes a postal code in their personal details, a Declare Trigger rule runs and a respective customer service representative (CSR) receives an email. After the CSR receives the email, a nested Declare Trigger rule runs and your application creates a document with the updated personal details and attaches it to the case.
For more information, see Develop applications faster with nested Declare Trigger rules (8.5), Declare Trigger rules.
Enhanced reliability and stability of scenario tests
Valid from Pega Version 8.5
Several enhancements have been made to scenario tests to increase their stability and reliability. With enhanced improvements, you can now:
- Delay the execution of a step within a scenario test to add latency to a web browser and actions on a web page. This prevents tests from failing when a dynamic web page does not load all page element at once, but the test finds page elements that are immediately rendered.
- Automatically rerun failed scenario tests, which might fail because there are temporal stability issues on the environment or because the application UI is slowly renders.
- View the run history of scenario tests so that you can analyze the history of a test over time.
For more information, see the following:
- Delay the execution of a step within a test and rerun failed scenario tests for enhanced scenario test stability (8.5)
- Changing application quality metrics
- Automatically rerunning failed scenario tests
- Creating scenario tests