Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring expected run-time assertions

Updated on April 8, 2022

You can create an assertion for the expected run time of the rule. The expected run-time assertion is less than or equal to an amount of time that you specify, in seconds.

An actual run time that is significantly longer than the expected run time can indicate an issue. For example, if you are using a report definition to obtain initial values for a data page from a database, there might be a connectivity issue between the application and the database.

By default, after you create a Pega unit test case for a data page, the system generates the expected run-time assertion. The default value of the expected run time is the time that is taken by the rule to fetch results when the test was first run. The system compares that time against future run-time tests.

You can change the default value and configure expected run time assertions for all rule types.

Before you begin: Open the unit test case. For more information, see Opening a unit test case.
  1. On the bottom of the Definition tab, click Add expected result.
  2. From the Assertion type list, select Expected run time.
  3. In the Value field, enter a value, in seconds, that specifies the amount of time within which the execution of the rule should be completed.
  4. Optional: If you want the test case to fail when the rule is not run within the specified time, select the Fail the test case when this validation fails check box.
  5. Optional: To add a comment, click the Add comment icon, enter a comment, and click OK.
  6. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us