Chapter 78. Feature comparison of legacy and new test scenario designer Red Hat Process Automation Manager supports both the new test scenario designer and the former test scenario (Legacy) designer. The default designer is the new test scenario designer, which supports testing of both rules and DMN models, and provides an enhanced overall user experience with test scenarios. You can continue to use the legacy test scenario designer, which only supports rule-based test scenarios. Important The new test scenario designer has an improved layout and feature set and continues to be developed. However, the legacy test scenario designer is deprecated with Red Hat Process Automation Manager 7.3.0 and will be removed in a future Red Hat Process Automation Manager release. The following table highlights the main features of legacy and new test scenario designer, which are supported in Red Hat Process Automation Manager to help you decide a suitable test scenario designer in your project. + indicates that the feature is present in the test scenario designer. - indicates that the feature is not present in the test scenario designer. Table 78.1. Main features of legacy and new test scenario designer Feature & highlights New designer Legacy designer Documentation Creating and running a test scenario You can create test scenarios in Business Central to test the functionality of business rule data before deployment. A basic test scenario must have at least a related data objects, GIVEN facts, and EXPECT results. You can run the tests to validate your business rules and data. + + For more information about creating rule and DMN-based test scenarios, see Chapter 65, Test scenario template . For more information about running the test scenarios, see Chapter 71, Running the test scenarios . For more information about creating and running test scenarios (legacy), see Section 77.1, "Creating and running a test scenario (legacy)" . Adding GIVEN facts in test scenarios You can insert and verify the GIVEN facts for the test. + + For more information about adding GIVEN facts in new test scenario designer, see Chapter 65, Test scenario template . For more information about adding GIVEN facts in test scenarios (legacy), see Section 77.1.1, "Adding GIVEN facts in test scenarios (legacy)" . Adding EXPECT results in test scenarios The EXPECT section defines the expected results based on the GIVEN input facts. It represents the objects and their fields whose exact values are checked based on the provided information. + + For more information about adding EXPECT results in new test scenario designer, see Chapter 65, Test scenario template . For more information about adding EXPECT results in test scenarios (legacy), see Section 77.1.2, "Adding EXPECT results in test scenarios (legacy)" . KIE session You can set KIE session on test scenario level settings. + + NA KIE base on test scenario level You can set KIE base on test scenario level settings. - + NA KIE base on project level You can set KIE base on project level settings. + + NA Simulated date and time You can set a simulated date and time for the legacy test scenario designer. - + NA Rule flow group You can specify a rule flow group to be activated to test all the rules within that group. + + For more information about setting rule flow group in new test scenarios, see Section 64.9.1, "Configuring global settings for rule-based test scenarios" . For more information about setting rule flow group in test scenarios (legacy), Section 77.1.1, "Adding GIVEN facts in test scenarios (legacy)" . Global variables Global variables are named objects that are visible to the decision engine but are different from the objects for facts. Setting global variables for new test scenario is deprecated . In case you want to reuse data sets for different scenarios, you can use the Background instance. - + For more information about Background instance in new test scenarios, see Chapter 68, Background instance in test scenarios . For more information about global variables in test scenarios (legacy), see Section 77.1, "Creating and running a test scenario (legacy)" . Call method You can use this to invoke a method from another fact when the rule execution is initiated. You can invoke any Java class methods from the Java library or from a JAR that was imported for the project. + + For more information about calling a method in new test scenarios, see Chapter 70, Expression syntax in test scenarios . For more information about calling a method in test scenarios (legacy), see Section 77.1, "Creating and running a test scenario (legacy)" . Modify an existing fact You can modify a previously inserted fact in the decision engine between executions of the scenario. - + For more information about modifying an existing fact in test scenarios (legacy), see Section 77.1.1, "Adding GIVEN facts in test scenarios (legacy)" . Bound variable You can set the value of a field to the fact bound to a selected variable. In the new test scenario designer, you can not define a variable inside a test scenario grid and reuse it inside GIVEN or EXPECTED cells. - + For more information about how to set bound variables in test scenarios (legacy), see Section 77.1.1, "Adding GIVEN facts in test scenarios (legacy)" .

Commands: