This example involves testing scenarios that might or might not include end-user selections depending upon the optional products or services.

Many test scripts exported from Hexawise look like these...

Note that each and every one of these test scripts has the same number of steps.  

But what would happen if someone didn't want to rent a car in this example? We would NOT want our tests to look like these:

The wording in red is problematic.  If a scenario includes "do NOT select 'Rent a car.' " then that scenario should not include any Values for either (a) Rental Car Brand or (b) Rental Car Transmission Type.  

To address this problem, you should first go to the "Parameters" screen and create a Value labeled "N/A" (Not Applicable) for both "Rental Car Brand" and "Car Transmission Type".

Next, create two Constraints...

Mutually Bound Constraint # 1 : "do Not select Rent a Car" must always appear with Rental Car Brand = N/A (and vice-versa).

Mutually Bound Constraint # 2 : "do Not select Rent a Car" must always appear with Rental Car Transmission Type = N/A (and vice-versa).

Other constraints (like mutually bound Rental Car Brand = N/A must always appear with Rental Car Transmission Type = N/A) are automatically created by the Hexawise tool and are displayed under "Implied".

For more information about how to use the Mutually Bound Constraint feature, please see this help file.


  1. There is no "magic" behind "N/A" value name, feel free to use "Not displayed", "Not applicable", "Ignore and skip this" or any other wording that works better in your script. The important part is having an explicit value tied to the conditional appearance of the parameter.

  2. Advanced Constraints enable the "skip" functionality without additional values. Feel free to reach out to us at to request access and learn how to use them.

Now, your Hexawise-generated tests will read properly. Some tests will have 7 Values to enter per test script. Other tests will have 5 per test script

Did this answer your question?