Creating test cases with AUT
You can automate testing of rules by creating test cases for automated unit testing. Automated unit testing validates application data by comparing expected output to the actual output that is returned by running rules.
To create test cases, you must have a rule set that can store test cases. For more information, see Creating a test ruleset to store test cases.
Automated unit testing information is available on the Testing Applications landing page on Pega Community and in the automated unit testing topics in the help.
- Creating a content security policy
Create a content security rule so that browsers load resources only from authorized web sites.
- AUT test cases
Create test cases for automated unit testing to validate application data by comparing expected output to the actual output that is returned by running rules.
- Keystores
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.
- Creating a rule
To save time and ensure that your projects adhere to the unique needs of your clients, create rules and data instances using reusable elements of your application. By combining a rule type, name, class, and ruleset, you provide a unique identity for each rule that you create.
- Copying a rule or data instance
Use the Save As form to copy an existing record's functionality to a new record with unique key parts. This form is pre-populated with the original record's key parts and creates default values for the new record's context.
- Creating a specialized or circumstance rule
You can create a specialized or circumstance rule to create a variant of the rule that can be triggered only conditionally. The created rule is resolved and active only when the specified conditions are met. Create specialized or circumstance rules to address dynamic business requirements without changing the core logic every time. For information