Rule Testing
Validate rules with saved Test cases and repeatable Test Suites.
Rule Testing lets you verify rule behavior against saved scenarios. Each scenario uses fixed input and expected output. You can rerun the same checks after any change.
Main benefits
Validate rule changes before release.
Catch unwanted side effects early.
Recheck rules after a DecisionRules update.
Understand rule behavior faster with real examples.
Core concepts
Test
A Test is the smallest testing unit.
A Test stores:
Name
Rule (it is linked to a rule by rule alias and rule version)
Rule strategy
Input
Expected output
Ignored output properties (optional)
Each Test always belongs to a Test Suite. Ignored outputs are useful for non-deterministic values. For example: current date, timestamp, or generated IDs.
Test Suite
A Test Suite is a collection of Tests. You can think of it as a folder for related scenarios.
A Test Suite is linked to a rule by:
Rule alias
Rule version
This makes the Test Suite specific to one rule version.
In rare cases, a Test Suite can point to a rule that no longer exists. These Tests are marked as Orphaned Tests.
Test Runs
After execution starts, Test Run is created with state Waiting. During processing, it can also be Running.
Finished Test Runs can end as:
Passed
Failed
Error
Canceled
What users can do
Rule Testing covers three main areas:
Rule-level Test management
Space-level Test management
Test Bench integration
Rule-level Tests tab
Rule Testing adds a Tests tab next to Model and Designer.
This tab is the main place to manage Tests for the opened rule. It shows all Test Suites and Tests linked to that rule.
Main actions
Users can:
Create a new Test / Edit a Test
Create a new Test Suite / Edit a Test Suite
Filter by name
Run all
Run selected
If nothing is selected, the run action offers Run all. If the user selects one or more items, it also offers Run selected.
Test Detail
User can modify test. There are 2 actions available: Run Test and Load to Test Bench.
Run Test
Test Run is created for selected Test.
Load to Test Bench
Users can copy test input directly into Test Bench. This makes failed tests easier to debug.
Rule-level Test Runs overview
The left-side Test Runs panel focuses on execution results and debugging. Panel shows all Test Runs belongs to current rule. If user clicked on one Test Run, detail is shown.
Test Run detail
Test Suites are collapsed by default. Users can expand a Test Suite to see its Tests.
Users can expand a test to inspect:
Input data
Expected output
Received output
Differences in received output are highlighted.
Available actions
From the left panel, users can:
Open Test details
Inspect Test in Test Bench
Space-level Tests menu
Rule Testing also includes a space-wide overview. This menu can be found at Space. It is the central place to manage all tests across the space.
Structure and selection
The overview uses an expandable structure. Users can inspect rules, Test Suites, and Tests. Selection uses checkboxes. Selecting a parent also selects its descendants.
Move and copy
Move and copy actions let users reassign tests to another rule. The target rule is selected in a dialog. This is useful when a test belongs to the wrong rule or should be reused elsewhere.
Test Runs
Test Run rows can include:
Tested at
Resource
Run by
Execution time
Status
Number of passed suites
Number of failed suites
Number of errors
If a run contains Test Suites from one rule only, the resource links to that rule. Otherwise, the resource is shown as Multiple Rules.
Opening a Test Run shows its details.
Test Bench integration
Rule Testing integrates directly with Test Bench. Thera are few possibilities that can be shown.
Save as test
After running a rule in Test Bench, users can choose Save as Test. This opens dialog with the current input and output already available. The user then fills in:
target Test Suite
name
Existing test match
If the current Test Bench input matches an existing test, the interface shows it. It also shows whether the current output matches the expected output. If multiple tests match the same input, infoo is shown
Updating expected output
If the input matches a saved test but the output differs, the user can update the test.This action ask for confirmation before replacing the expected output.
Import and export
Tests and Test Suite can be exported as JSON. This export is separate from rule export.
Exporting a rule does not include tests
Tests can also be imported to space, rule or Test Suite.
Orphaned Tests
Orphaned Tests exist when the stored alias and version do not match any existing rule. Orphaned Tests can be shown in the space-level menu. Users can then move those tests to an existing rule.
Rule Testing vs. Test Bench
Test Bench is best for ad-hoc checks while editing a rule. Rule Testing is best for saved and repeatable validation. Use Test Bench to explore. Use Rule Testing to verify.
Automation
If you want to run tests programmatically, use the Rule Testing API.
Last updated
Was this helpful?