Excel scenario files

After you generate an Excel scenario file, you must add the scenario data that is used to validate your rules in tests or simulations.

An Excel scenario file can contain the following sheets:
  • Scenarios: Contains the input data for scenarios. Both testing and simulation scenario files have this sheet.
  • Data entry: Regroups information that is used in other sheets.
  • Expected Results: Holds the results that you expect from tests.
  • Expected Execution Details: Holds the execution details that you expect from tests.
Important:

Never modify the column structure of the sheets.

Completing sheets with data

You can enter literal values such as a number or a string, formulas, values from domains, lists of values, and values from other Excel sheets. The type of data that you can enter depends on how the column was defined.

The generated tables contain visual aids to help you enter data:
  • Red triangle: When shown in a column header, it indicates the presence of a comment that explains the type of values to be entered, such as text, numbers, dates, or true or false. Hover over a triangle to display a comment as follows:

    Image shows a comment that is displayed by hovering over a red triangle.
  • Dark green triangle: When shown in a cell, it suggests a better format for the cell. For example, if you enter a numerical value in a text cell, Excel suggests that you format the cell for numerical values. To make sure that the scenario runs correctly, ignore this suggestion.
  • Arrow: When shown before a column name, it indicates that the values must correspond to entries that are specified in a separate data entry sheet.

If the expected value is a number, you can enter a formula.

To enter a value from a domain, select the cell and click the arrow beside it to see the available values:

Image shows an Excel file with a list of values.

When you test for a list of values, you enter each item in the corresponding cell on a separate row:

Image shows an Excel file with a list of values.

You do not have to duplicate the Scenario ID for each row because the last ID entered is used.

Scenarios sheet

Each row in the Scenarios sheet represents one scenario. Each scenario must contain all the information needed to process a transaction.

Image shows the table on Scenarios sheet.
The columns indicate the information that you must provide for each scenario:

  • Scenario ID: The name identifies the scenario and must be unique.

  • description: A free text cell to describe the scenario.

  • business terms: Values for the scenarios. Bold columns or subcolumns are mandatory.

Note:

The reduced rows between the column headers and the first scenario contain information that might be useful to developers. Never edit these rows.

Data entry sheets

You create data entry sheets when you generate a scenario file. Data entry sheets regroup data to be used in other sheets.

The name of each data sheet serves as the type of data that is expected in the column of the other sheet that uses the data. For example, in the following figure, the address sheet  1  contains different addresses that are used in the addresses column  2  of the Scenarios sheet.

Image shows an address data entry sheet and its column in the Scenarios sheet.
Note:

A column that uses values from a data entry sheet has an arrow in its column header.

You create an entry in a data entry sheet by completing a row that includes a unique name to identify the entry in the other sheets.

Expected Results sheet

The Expected Results sheet contains the results that you expect to obtain when you run tests that use the scenarios.

You can test many aspects of a set of rules, but the Expected Results sheet contains only the tests that you specified when you generated the scenario file. For example:

Image shows the Expected Results sheet of the scenario file.

Each blue column in the Expected Results sheet corresponds to a test. If you do not enter a value in a column, the corresponding test is skipped.

Tip:

You cannot create a new column in Excel. However, you can generate another empty scenario file template, and then copy and paste a column from it.

You link the sheets that contain the scenarios and their expected results by entering names in their respective Scenario ID columns. In addition to making sure that the names match between the two sheets, it is good practice to keep the scenarios and their expected results in the same order.

When you test for a list of values, you enter each item in the corresponding cell on a separate row. You do not have to duplicate the Scenario ID for each row.

Expected Execution Details sheet

The Expected Execution Details sheet contains the execution details that you expect to obtain when you run tests that use the scenarios.

The following are examples of execution details:
  • List of rules fired
  • List of executed ruleflow tasks
  • Duration of execution

You can test many aspects of a run, but the Expected Execution Details sheet contains only the tests that you specified when you generated the scenario file. Each green column in the Expected Execution Details sheet corresponds to a test.

You link the sheets that contain the scenarios and expected execution details by entering names in their respective Scenario ID columns.