Procedure

1. In Business Central, go to Menu → Design → Projects and click the project name.
2. Click Add Asset → Data Object.

3. Enter a unique Data Object name and select the Package where you want the data object to be available for other rule assets. Data objects with the same name cannot exist in the same package. In the specified DRL file, you can import a data object from any package.

   Importing data objects from other packages

   You can import an existing data object from another package directly into the asset designer. Select the relevant rule asset within the project and in the asset designer, go to Data Objects → New item to select the object to be imported.

4. To make your data object persistable, select the Persistable checkbox. Persistable data objects are able to be stored in a database according to the JPA specification. The default JPA is Hibernate.
5. Click Ok.

6. In the data object designer, click add field to add a field to the object with the attributes Id, Label, and Type. Required attributes are marked with an asterisk (*).

   • Id: Enter the unique ID of the field.
   • Label: (Optional) Enter a label for the field.
   • Type: Enter the data type of the field.

   • List: Select this check box to enable the field to hold multiple items for the specified type.

     Figure 2.1. Add data fields to a data object

     

7. Click Create to add the new field, or click Create and continue to add the new field and continue adding other fields.

   Note

   To edit a field, select the field row and use the general properties on the right side of the screen.

Procedure

1. Open the test scenario in the Test Scenario designer.
2. Enter a description of the test scenario and fill in required values in each cell of the row.

3. Use the contextual menu to add or remove rows as required.

   Double click a cell to start inline editing. To skip a particular cell from test evaluation, leave it empty.

Procedure

1. Set the column type first (use a field whose type is a list or a map).
2. Double click a cell in the column to input a value.
3. In the collection editor popup, click Add new item.
4. Enter the required value and click the check icon to save each collection item that you add.

5. Click Save.

   To delete an item from the collection, click the bin icon in the collection popup editor. Click Remove to delete the collection itself.

Procedure

1. At the top of the Test Scenario designer, click Run Test icon.
2. The Test Report panel pops out from the right of the designer and displays the test result overview and the scenario status.
3. After the tests are executed, click View Alerts to open the Alerts panel at the bottom of the designer for the error messages.

4. In case the tests fails, review the error messages. Messages with a red cross indicate test failures where as those with a green check mark indicate successful tests.

   In the designer, erroneous rows or cells are highlighted in red.

5. Make the necessary changes and run the test again till the scenario passes.

Procedure

1. In Business Central, go to Menu → Design → Projects and click the project name.
2. On the Project’s home page, select the Settings tab.
3. Select git URL and click the Clipboard to copy the git url.
4. Open a command terminal and navigate to the directory where you want to clone the git project.

5. From your project’s directory run the following command:

   git clone your_git_project_url

   Replace your_git_project_url with relevant data like git://localhost:9418/MySpace/ProjectTestScenarios.

6. Once the project is successfully cloned, navigate to the git project directory and execute the following command:

   mvn clean test

   Your project’s build information and the test results (such as, the number of tests run and whether the test run was a success or not) are displayed in the command terminal. In case of errors, correct them and run the command again.

Procedure

1. In Business Central, go to Menu → Design → Projects and click Mortgages.
2. If the project is not listed under Projects, from MySpace, click the three dots ( ) in the upper-right corner of the page.

3. Click Try Samples → Mortgages → OK.

   The Assets window appears.

4. Click Add Asset → Test Scenario.

5. Enter scenario_pricing_loans as the Test Scenario name and select the default mortgages.mortgages package from the Package drop-down list.

   The package you select must contain all the required rule assets.

6. Click Ok to create and open the test scenario in the Test Scenario designer.

7. Expand Project Explorer and verify the following:

   • Applicant, Bankruptcy, IncomeSource, and LoanApplication data objects exist.
   • Pricing loans guide decision table exists.
   • Verify that the new test scenario is listed under Test Scenario

8. After verifying that everything is in place, return to the Model tab of the test scenarios designer and define the GIVEN and EXPECT data for the scenario, based on the available data objects.

   Figure 3.1. A blank Test Scenario designer

   

9. Define the GIVEN column details,

   1. Click the cell named INSTANCE 1 under the GIVEN column header.
   2. From Test Tools → Test Editor, select LoanApplication data object.
   3. Click Add.
10. To create properties of the data object, right-click the property cell and select Insert column right or Insert column left as required. For this example, you need to create two more property cells under the GIVEN column.

11. Click the first property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click amount and then Add to map the data object field to the property cell.

12. Click the second property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click deposit and then Add.

13. Click the third property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click lengthYears and then Add.
14. Right-click LoanApplication header cell and select Insert column right. A new GIVEN column to the right is created.

15. Click the new header cell,

    1. From Test Tools → Test Editor, select the IncomeSource data object.
    2. Click Add to map the data object to the header cell.

16. Click the property cell below IncomeSource,

    1. From Test Tools → Test Editor, select and expand the IncomeSource data object.

    2. Click type and then Add to map the data object field to the property cell.

       You have now defined all the GIVEN column cells.

17. Next, define the EXPECT column details,

    1. Click the cell named INSTANCE 2 under the EXPECT column header.
    2. From Test Tools → Test Editor, select LoanApplication data object.
    3. Click Add.
18. To create properties of the data object, right-click the property cell and select Insert column right or Insert column left as required. Create two more property cells under the EXPECT column.

19. Click the first property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click approved and then Add to map the data object field to the property cell.

20. Click the second property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click insuranceCost and then Add.

21. Click the third property cell,

    1. From Test Tools → Test Editor, select and expand the LoanApplication data object.
    2. Click approvedRate and then Add.

22. Now for defining the test scenario, enter the following data in the first row:

    • Enter Row 1 test scenario as the Scenario Description, 150000 as the amount, 19000 as the deposit, 30 as the lenghtYears, and Asset as the type for the GIVEN column values.
    • Enter true as approved and 0 as the insuranceCost for the EXPECT column values.

23. Next enter the following data in the second row:

    • Enter Row 2 test scenario as the Scenario Description, 100002 as the amount, 2999 as the deposit, 20 as the lenghtYears, and Job as the type for the GIVEN column values.
    • Enter true as approved and 10 as the insuranceCost for the EXPECT column values.
24. After you have defined all GIVEN, EXPECT, and other data for the scenario, click Save in the test scenarios designer to save your work.

25. Click Run Test in the upper-right corner to run the .scesim file.

    The test result is displayed in the Test Report panel. Click View Alerts to display messages from the Alerts section. If a test fails, refer to the messages in the Alerts section at the bottom of the window, review and correct all components in the scenario, and try again to validate the scenario until the scenario passes.

26. Click Save in the test scenarios designer to save your work after you have made all necessary changes.

Procedure

1. In Business Central, go to Menu → Design → Projects and click the project name.
2. Click Add Asset → Test Scenario (Legacy).
3. Enter an informative Test Scenario name and select the appropriate Package. The package that you specify must be the same package where the required rule assets have been assigned or will be assigned. You can import data objects from any package into the asset’s designer.

4. Click Ok to create the test scenario.

   The new test scenario is now listed in the Test Scenarios panel of the Project Explorer,

5. Click the Data Objects tab to verify that all data objects required for the rules that you want to test are listed. If not, click New item to import the needed data objects from other packages, or create data objects within your package.

6. After all data objects are in place, return to the Model tab of the test scenarios designer and define the GIVEN and EXPECT data for the scenario, based on the available data objects.

   Figure 4.1. The test scenarios designer

   

   The GIVEN section defines the input facts for the test. For example, if an Underage rule in the project declines loan applications for applicants under the age of 21, then the GIVEN facts in the test scenario could be Applicant with age set to some integer less than 21.

   The EXPECT section defines the expected results based on the GIVEN input facts. That is, GIVEN the input facts, EXPECT these other facts to be valid or entire rules to be activated. For example, with the given facts of an applicant under the age of 21 in the scenario, the EXPECT results could be LoanApplication with approved set to false (as a result of the underage applicant), or could be the activation of the Underage rule as a whole.

7. Optionally, add a CALL METHOD and any globals to the test scenario:

   • CALL METHOD: Use this to invoke a method from another fact when the rule execution is initiated. Click CALL METHOD, select a fact, and click to select the method to invoke. You can invoke any Java class methods (such as methods from an ArrayList) from the Java library or from a JAR that was imported for the project (if applicable).
   • globals: Use this to add any global variables in the project that you want to validate in the test scenario. Click globals to select the variable to be validated, and then in the test scenarios designer, click the global name and define field values to be applied to the global variable. If no global variables are available, then they must be created as new assets in Business Central. Global variables are named objects that are visible to the decision engine but are different from the objects for facts. Changes in the object of a global do not trigger the re-evaluation of rules.
8. Click More at the bottom of the test scenarios designer to add other data blocks to the same scenario file as needed.
9. After you have defined all GIVEN, EXPECT, and other data for the scenario, click Save in the test scenarios designer to save your work.

10. Click Run scenario in the upper-right corner to run this .scenario file, or click Run all scenarios to run all saved .scenario files in the project package (if there are multiple). Although the Run scenario option does not require the individual .scenario file to be saved, the Run all scenarios option does require all .scenario files to be saved.

    If the test fails, address any problems described in the Alerts message at the bottom of the window, review all components in the scenario, and try again to validate the scenario until the scenario passes.

11. Click Save in the test scenarios designer to save your work after all changes are complete.