Discipline: Rule Validation |  |
Validation will involve testing the rules and get Subject Matter Expert feedbacks to improve the quality of the rules. A set of tools are available in high end BRMS platform to do some rule conflict analysis, testing, and executing complex queries to understand how rules are impacting others rules result. The tasks are following a TDD approach, where data scenarios are defined as early as the rule discovery, and tests are developed to integrate the data definition to trigger rule execution in the context of the rule set deployed.
Relationships
Tasks | Define Rule Testing Approach Define Data Scenarios to Test Rule Execute Rule Set Functional Tests Get Rule Set Reports Get SME Feedback Test Analysis
Main Description
Rule Testing allows developers to: Validate each rule in the context of its rule set: Control the rule set quality. Impact analysis: to define at the execution if rules are in conflict. Define Data scenarios and test cases to complete the rule approach. Develop a powerful framework to support this goal. Helps to have non-regression tests. Helps to have simulation platform. The objective of testing is to: Allow policy managers and business analysts to ensure that the rules are consistent with the intended policy. Provide a sandbox environment for policy experimentation. We distinguish three types: Unit Testing : The process of testing a specific rule. End-to-End Testing : The process of testing a (larger) set of rules, a whole ruleflow or an entire rule service. Simulation and Impact Analysis : The process of testing a policy change on a sample set of real data, to predict the impact this would have on the business.
More Information
Guidelines | Delta-Testing
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. EPF Copyright.