Page History
...
In specific scenarios, system allows user to define what parameter values can never be tested together or in the other hand, scenarios where parameter values can only be tested together.
For that, user can apply constraints to support these cases.
So that the model can understand the requirements, you have the option to define invalid constraints (values that can never be tested together), and/or bound constraints (values that can only be tested together) to train the model.
Invalid constraints
Invalid constraints restrict parameter values that can never be tested together.
...
On the Rules ->Constraints screen, you will need to click on two red X’s. Hover over the first Value of the Invalid Pair and click on the red X that appears
Find the second Value that can never appear together with the first one, hover over it, and click on the red X to create your “Invalid Pair”
As you enter your Constraints, you will see them listed to the left:
After you enter these two Invalid Pairs, clicking on the “Scenarios” button will create a completely new set of test cases that excludes those two pairs of Values (and only those two pairs of Values). Each test with ‘OS X’ as the operating system will have a browser other than IE.
As you use the Invalid Pair feature and the related Bound Pair one, keep in mind these usage tips:
| Tip |
|---|
Do you need to add a lot of Invalid Constraints?
|
...
|
...
Watch out for “Not Applicable” Values.
|
Bound constraints
Bound constraints restrict parameter values that can only be tested together.
...
Consider these parameters & values:
You will have the following issue when you click on the “Scenarios” button:
...
When you add a Bound Pair, Xray Enterprise Test Case Designer will constrain the first value chosen against all the other values in the parameter of the second value chosen. In the example above, creating a bound constraint of ‘Do Not Add Hotel’ and ‘Hotel Chain Preference’ = ‘Not Applicable’ means you are really invalidating these options:
...
We would like to exclude combinations like ‘Breed of Animal = Shiba Inu’ and ‘Type of Animal = Cat’ from the generated scenarios. We have 2 breeds for each of the first 2 types of animals. Therefore, we can set up 4 one-way bound pairs from "Breed of Animal" to "Type of Animal":
You can check your logic by reading the statement at the bottom of the dialog.
...
First, navigate to Rules→ Constraints. Next, click the toggle to change to Advanced Mode – that is the only way to implement "Skip" constraints:
Once in Advanced Mode, we use the following syntax for "Skip" constraints:
...
The final component of "Skip" constraints is the ‘skip to end’ capability. In this case, we can tell Xray Enterprise Test Case Designer that for some parameters values, skip all parameters listed later (below) on the “Parameters” page.
...
Lastly, you can do a quick review of available options & syntax by clicking the “Usage” button in top-right section of the Advanced Mode:
View a Constraint
| UI Steps | ||||
|---|---|---|---|---|
| ||||
|
Edit a Constraint
To edit a constraint, you need to change view to "bulk" . Then you can edit the constrain type selecting the corresponding operator. 
It is not possible to edit a constrain at the Standard View. In the Standard View you are only allowed to delete and create a new constrain.
Delete a Constraint
To delete a constraint, hover the constraint and select the delete option:
Another option is to, on bulk view mode, delete the desired constraint line: