Validating and testing decision model services

With a decision model service, you can validate your decision model during development. You can also create more complete usage scenarios that you use in test suites and simulations, just like regular decision services.

Each time that you save a new version of your decision model, Decision Center compiles the content of your decision model and displays any errors or warnings that you must fix.

Decision Center also provides a Validate feature for decision model services, to rapidly try out your decision model when you are defining it. At each step, you provide data to ensure that your model returns the results you expect. Decision Center runs your data on a local embedded engine. You provide the data in a friendly form or in its underlying JSON format.

Test suites and simulations

Decision model services behave the same way as regular decision services for test suites and simulations.

Testing sets of rules in the Business console describes how to setup test suites that run rules, on an execution environment, against usage scenarios. You setup test suites after your decision model is complete, for regression testing.
Simulating business application results describes how to create simulations to see how changes to rules or data affect the results of your decision model service, based on key performance indicators.

There are some differences to consider, because the decision model is considered as one artifact:

You run test suites or simulations on the entire decision model, because you cannot create a decision operation that defines a subset of rules.
When you configure a test suite or generate a scenario file, the only execution detail that can be included in the report is the duration of execution.