Setting up your test environment
Configure which actions you want to run and which objects and pages you want to view on the clipboard before, during, and after the test is run.
To set up the environment and conditions that are required before running this test case, copy or create clipboard pages, apply data transforms, load data pages, execute activities, and create and load objects. Then, define the connections to data pages or third-party databases to simulate during the test. Finally, after running the test case, set up the environment and conditions that are required by applying data transforms, loading data pages, executing activities, and creating and loading objects.
Click the Setup & Cleanup tab.
To make specific conditions available during test execution, expand the Before rule execution section, and then configure the conditions:
To define simulation settings for the test, expand the Simulation section, and then configure the simulations.
For more information, see Simulating data pages and third-party connections.
To make specific conditions available after test execution, expand the After rule execution section, and then add additional clipboard data.
For more information, see Adding additional clipboard data.You can set up actions after rule execution for test cases only.
To run the rule under on a page and avoid copying the entire page to RunRecordPrimaryPage, in the Advanced section, enter the page under which you want to run the rule.
- Copying and creating clipboard pages in setup
When setting up your test environment, you can set to copy or create clipboard pages before the test runs.
- Adding additional clipboard data
When setting up your test environment, you can add additional clipboad data before or after the test runs. You can create apply data transforms, load data pages, execute activities, load objects, create data objects, and create work objects.
- Simulating data pages and third-party connections
When setting up your test environment, you can simulate data pages and third-party connections. Such simulations let you run your tests without depending on the availability of third-party servers.
- Clipboard tool
Every connected Pega Platform requestor (including browser-based users, even unauthenticated guest users) has an associated temporary memory area on the server known as the clipboard. The clipboard has a hierarchical structure, consisting of nodes known as pages, most of which have a name and an associated class. Pages act as buffers or temporary
- Converting unit tests to test cases
- Data pages
A data page defines the contents of a clipboard page and enables the system to access data from a range of sources on demand.
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.
- Data Transforms
A data transform defines how to convert data that is in one format and class (the source) into data of another format and class (the target). The supported formats are clipboard and JSON. Using a data transform instead of an activity to set property values speeds up development and makes application maintenance easier.