Do you need to add a lot of Invalid Constraints?

• Imagine you had an application that asked, “Would you like to add a hotel to your travel reservation?” Any scenarios with “Do Not Add a hotel” would require many, many different Invalid Constraints between things like “Do Not Add a Hotel” and “Hotel Chain Preference = X”. For situations like those, the Bound Constraint feature will help you accomplish your constraint handling much faster.
• If you have more than 10 or so Invalid Constraints (or Bound Constraints) in your plan, you might find that it is faster to export your plan into Excel and document your paired values in Excel. If so, make sure to both (1) add multiple paired values in Xray Test Case Designer before you export into Excel (so you can copy and paste the Xray Test Case Designer formatting for Invalid Constraints and/or Bound Constraints), and (2) ensure that you use the exact spelling of Values (e.g., ‘cutting and pasting’ Values will usually be safer than typing)
  
  

Watch out for “Not Applicable” Values.

• Do you need to add some of them to your plan? Do you need to invalidate the combination of “Not Applicable” with other specific Values?
• Especially watch out for situations where you have multiple related “Not Applicable” values in a plan. Would it make sense to create a “Bound Constraint” between ‘Hotel Chain Preference = Not Applicable’ and ‘Type of Room’ = Not Applicable’?