Here you enter the variation ideas that you'll be testing. This is the screen where you'll be able to:

  • Add or edit your Parameters and Values (in Standard or Bulk modes)

  • Add or edit Value Expansions


Clicking on the "Scenarios" tab on the left navigation menu will take you here.  You'll notice that Hexawise automatically presents you with a set of 2-way ("pairwise" or "all pairs") test conditions whenever you arrive on this screen. That choice can be changed using the highlighted dropdown.


The Analysis screen provides two (2) options to better understand your test plan: 

  1. Coverage Matrix: See the specific pairs of interactions covered by your Hexawise model, scenario by scenario

  2. Coverage Graph: See the additional coverage achieved with each single scenario

Rules - Constraints

Constraints allow to specify the interaction rules between values and to make sure there are no invalid/impossible/unnecessary scenarios in your model. The Advanced version (toggle in the top left) is in beta stage and can be enabled per request.

Rules - Forced Interactions

At the "Forced Interactions" screen, you will be able to add specific combinations of test conditions/parameters & values to the scenarios that Hexawise generates. Tracing requirements to specific test scripts can be challenging, particularly as requirements change and sets of regression tests age.  You'll find this feature helpful for making requirements traceability easier and less error-prone.

Expected Outcome

You can add expected outcomes to the scenarios & scripts you generate. This can be done on the "Forced Interactions" screen (above) or on the "Manual Auto-Scripts" screen (below).

If Hexawise is the first test generation tool you've used, you might take this for granted. If you've used other test generation tools before finding Hexawise though, you might feel compelled to publicly declare your love of Hexawise and/or send gifts to the engineers and designers at Hexawise who created this great feature. We believe it's a feature unique to Hexawise, and should save you huge amounts of time when you create test scripts.


The primary advantage at the documentation stage comes from the one-to-many relationship - a single template script written in Hexawise will export into as many scenarios as are relevant given the parameter/value selections.

Manual Auto-Scripts

You can create detailed steps & expected results for testers to follow during execution. This option is geared towards ALM-like export.


Hexawise Automate allows you to create Gherkin feature files as behaviors for your Hexawise generated test cases. You can create as many Gherkin feature files as you need for your test plan (one per tab) in either Scenario or Scenario Outline format. This option is geared towards Automation Framework export, but can be compatible with Excel as well.

Did this answer your question?