Back Forward Designer Studio – How to unit test a rule with the Run Rule feature

  Show all 

Sridnar Avatapalli 5/25/06 The Run toolbar button (Run) opens the Run Rule window for the currently displayed rule. You provide test data and then Process Commander runs the rule and displays the results. If the results are not what you expected, modify the rule and test it again.

The appearance of the Run Rule window varies across rule types, so how you run a rule varies by its type. In general, you complete the following kinds of tasks:

The Run Rule feature uses rule resolution when running the rule. If you click the Run button but a higher version exists of the rule that you currently have open, Process Commander displays a status message stating it will run the higher version. Accordingly, to test a circumstanced or time-qualified rule, ensure that the circumstances are correct for the rule. Otherwise, the base (unqualified) rule runs instead of the one you intend to test.

Clipboard pages

After running a rule, you can open the Clipboard tool and examine the output as it appears on the resulting clipboard pages. The Run Rule operation creates the following pages:

List view and summary view rules

When you click the Run button for a list view or summary view rule, the Run Rule window does not appear. Instead, Process Commander runs the report and displays the results.

Service rules

Before testing service rules, determine how you will provide the sample data for the service to process. For information, see the Pega Developer Network document PDNTesting Services and Connectors.

Testing details

Select topics in the following list for information about how to unit test rules of specific types:

  Activity Service EJB
  Decision table Service Email
  Decision tree Service File
  Declare expression Service Java
  Flow Service JMS
  Map value Service JSR94
  Parse Delimited Service MQ
  Parse Structured Service dotNet
  Parse XML Service SOAP
    When
Definitions service

UpDesigner Studio — Using the toolbar