Testing your applications
Developers and quality assurance engineers are responsible for testing RuleApps and client applications. They use testing tools and standard Java™ testing frameworks to ensure these applications run correctly and efficiently.
In most cases, by the time you create a RuleApp, you have tested its rulesets to some extent in Rule Designer and, if possible, through testing and simulation. By testing and simulating the execution of a ruleset, you can validate usage scenarios. You run such tests to ensure the correctness of a ruleset and to observe how changes to rules might affect execution results.
After you create your RuleApps and client application, make sure that they execute as expected. By debugging your rulesets, you find and remove defects in the rule project and client application.
- Create a launch configuration that specifies the type of session that you want to start.
- Establish a connection between the debugger client and the rule project that you are opening.
- Start a rule project in debug mode on your workstation locally.
- Test a remote Java application that executes the rules of a rule project.
You can store the results of your executed rulesets in Decision Warehouse. Decision Warehouse is an additional facility in Rule Execution Server to store, filter, and view rule execution activity. The execution traces form a decision history which you can use to audit the ruleset. For more information, see Setting up ruleset execution traces.
For more formalized test and performance testing, use standard Java testing tools and frameworks.