How to Unit Test a Decision Table Rule

The Run Rule feature enables you to test a decision table individually before testing it in the context of the application you are developing. You specify a test page for the rule to use, provide sample data as the input, run the rule, and examine the results.

If you have the AutomatedTesting privilege (through an access role), you can use the features of Automated Unit Testing such as saved test cases and unit test suites for testing your decision table. See About Automated Unit Testing and Working with the Test Cases tab for more information.

Before you begin

Before you begin, determine how you will provide the sample data to use when testing the rule. Can you enter all the data in the Run Rule window? Or does the rule need specific pages to be on the clipboard to return a decision?

• Examine the rule. Review the Applies To key part, Table tab and Pages & Classes tab of the rule, to identify the classes of the pages it uses for input and the properties involved in the decision.
• The Run Rule feature can create or copy a page to use as the test page, as appropriate for the rule you are testing. The page class of the test page is the Applies To class of the rule. If necessary, you can create a data transform to set initial values for the page.
• If the rule requires input from several pages, determine how to mimic the processing that creates them so the clipboard has the initial context you need to run the rule. For example, you can run an activity that creates the pages or start a flow and stop it at the appropriate point.

For general information about the Run Rule feature, including a list of the clipboard pages generated when a rule runs, see How to test a rule with the Run Rule feature.

Run the rule

To run the rule, complete the following steps:

1. Save the rule.
2. Complete any preprocessing necessary to create the appropriate clipboard context and, if the rule is circumstanced or time-qualified, to set the conditions you want to test.
3. Click Run. The Run Rule window appears.
4. In the Test Page section, specify which page to use as the main page: select Create or Reset Test page and in the Apply field, select the data transform to use for the test page or leave the default. Click Reset Page to clear any prior test data from the Results section of the window.

   If you have the AutomatedTesting privilege, the Auto-generate Test Cases and Run Against a Saved Test Case choices are available:

   • To have the system generate all test cases for this decision table by iterating through the conditions in the table, select Auto-generate Test Cases and click the Generate Test Cases button. For more information, see the articles in the Testing Applications category of the PDN.
   • If saved test cases exist for this rule, you can run the rule and see how its behavior compares to that in the saved test cases by selecting a choice for the Run Against a Saved Test Case field. You can choose to unit test against a specific test case, all test cases, or all auto-generated test cases.

     After making your selection, click Run Test Case. If differences are found between results of running the current state of the rule and the saved test case, they are displayed and you have the options of overwriting the saved test case, viewing the rule history, and saving the results.

5. If you are not auto-generating test cases or running against a saved test case, specify the test data in the lower section of the Run Rule window, and click Run Again. The system runs the decision table and displays the results.

   If you have the AutomatedTesting privilege and you want to save this run as a test case, click Save Test Case.

6. Optional. Click the Result Decision Paths link to go directly to the row on the Table tab that produced the test result. If the Evaluate All Rows option on the Results tab is selected, all the rows that are true are highlighted.
7. Optional. Click Show Clipboard to open the Clipboard and examine the pages. Click Hide Clipboard to close the tool. For information about the clipboard pages that are generated, see How to test a rule with the Run Rule feature.
8. Repeat as necessary, selecting other data transforms or providing other input values.

Debugging decision tables with the Tracer

If your decision table rule does not give you the results you expect and you cannot determine the problem by running the rule and examining the clipboard pages, run the Tracer tool. With the Tracer, you can watch each step in the evaluation of a decision table as it occurs.

Complete the following steps:

1. Click Tracer on the developer toolbar in Designer Studio.
2. In the Tracer window, click Settings .
3. In the Event Types to Trace section, select Decision Table.
4. Select the ruleset that contains the rule to be traced. Clear the other rulesets to avoid memory usage from tracing events occurring in other rulesets.
5. Click OK.
6. Return to the main portal and run the decision table.
7. Watch the Tracer output as the rule runs.

About Decision Tables

Open topic with navigation