(Lessons Explaining How to Use Hexawise Features) Instructions for the Novice ➜ Practitioner AchievementsHow do I create an "Invalid Pair" to prevent impossible-to-test-for Values from appearing together?

How do I create an "Invalid Pair" to prevent impossible-to-test-for Values from appearing together?

Sometimes you might notice that Hexawise creates a combination of Values in a single test case that cannot be tested because it is impossible to have those two Values ever appear together in a real-world scenario. This lesson explains how to use the "Invalid Pair" feature of Hexawise to solve that problem.

Use the "Invalid Pairs" feature to prevent certain combinations of Values from appearing together in the same test case

In this example, Internet Explorer (IE) is not supported on Apple computers so it would be impossible for a tester to execute a test case that instructed her to launch IE from a Mac running on its native operating system. Accordingly, we do not want any tests generated by Hexawise to include pairs such as "OS X" and "IE8" in the same test case.

On the "Constraints" screen, hover over the first Value of the Invalid Pair and click on the red X that appears

Repeat for the second Value in the Invalid Pair

Problem solved!

After you enter these two Invalid Pairs, clicking on the "Test Cases" 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 Married Pair feature, keep in mind these usage tips:

Do you need to add a lot of Invalid Pairs?

  • 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 Pairs between things like "Do Not Add a Hotel" and "Hotel Chain Preference =  X". For situations like those, Hexawise's Married Pair feature will help you accomplish your constraint handling much faster.
  • If you have more than 10 or so Invalid Pairs (or Married Pairs) in your plan, you might find that it is faster to export your Hexawise plan into Excel and document your paired values in Excel. If so, make sure to both (1) add multiple paired values in Hexawise before you export into Excel (so you can copy and paste the Hexawise formatting for Invalid Pairs and/or Married Pairs), 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? (In the Married Pair explanation, for example, we would not want "Do Add a Hotel" to appear together with 'Hotel Chain Preference = Not Applicable')
  • Especially watch out for situations where you have multiple related "Not Applicable" values in a plan. Would it make sense to create a "Married Pair" between 'Hotel Chain Preference = Not Applicable' and 'Type of Room' = Not Applicable'? In the Married Pair explanation, for example, it would make sense to add that Married Pair.