Conditions and rules

For this example, use the data-driven test of the previous chapters. Only this time, insert just the female staff members into the database of the Ranorex Studio Demo Application.

In summary:

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

• You can add a condition to test cases or smart folders only.
• Only one condition per test container.
• Conditions can contain and are defined by one or more rules.
• The entire process is the same for both types of test containers.

To add a condition:

1. Right-click the smart folder or test case if you want to add the condition.

2. Click Condition…
   
   

3. Click Add rule to define a rule for this condition.
   

1. 1. The Condition tab of the test container properties dialog.

   2. The inactive condition, with no rules defined below it yet.

Conditions are defined by rules. You can add up to 10 rules to a condition. Rules always follow the same pattern and check whether a data source or parameter value is equal or not equal to a control value.

Define a rule from left to right by selecting the required details and click OK when you’re done.

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 will be 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 completed and are ready to run the test. Run the test from the test suite view as usual. You will notice the database in the Ranorex Studio Demo Application only contains female staff members. The report will also reflect the condition, with iterations where the condition wasn’t met marked as blocked: