Conditions and Rules

For this example, use the data-driven test from the previous steps in this workflow. This time, ypu want to insert only female staff members into the database of the Ranorex Studio Demo Application.

In summary:

• Normally, 8 staff members are inserted into the database.
• You want to modify the test case so that it enters only female staff members into the database.
• You want to accomplish this with a condition.

Keep these constraints in mind:

• You can add a condition to test cases or smart folders only.
• You can define one condition per test container.
• A condition contains one or more rules.

• The workflow is the same for test cases and smart folders.

To add a condition:

1. In the test suite, right-click the test case or smart folder where you want to add the condition.
2. Click Condition…
   
3. In the Condition tab, click Add rule.
   

1.  
   1. The Condition tab of the test container properties dialog.
   2. The inactive condition has no rules defined below it yet.

Conditions are defined by rules. You can add up to 10 rules to a condition. Each rule checks whether a data source or parameter value is equal or not equal to a control value.

Define a rule from left to right, then click OK.

1. Data source/Parameter: Select whether the value you want to check is in a data source or a parameter.
2. Specific data source/parameter: Select the specific data source or whether it is a local/global parameter that contains the value.
3. Column/row: Select the column (data sources) or the row (parameters) that contains the value.
4. Operator: Select whether the value you want to check must be equal or not equal to the control value.
5. Control value: Select a possible control value from the data source/parameter.

Result

If you defined the rule just as above, you now have a condition with one complete rule. In the test suite view, this is indicated as follows:

1. Conditional test case.
2. Indicator showing that the test case has an active, defined condition.

1. Activation checkbox: Quickly switch between active/inactive conditions. Do not delete any defined rules.
2. Condition operator: Sets when the condition is met and the test container is run.
3. Incomplete rule indicator: Appears wherever a rule is missing information.
4. Rule completeness indicator: Shows whether the rule is complete or incomplete.

Depending on their completeness and activation status, conditions are indicated by three different symbols in the test suite view:

1. Active condition with one or more complete rules.
2. Active condition with one or more incomplete rules.
3. Inactive condition with one or more complete or incomplete rules.

The condition is complete and ready to use. Run the test from the test suite view as usual.

Expected results

• In the Demo Application, the database shows only female staff members inserted.

• In the report, iterations where the condition is not met are marked as blocked.
  (Image: report showing blocked iterations)