Hexawise Recent Updates

September 8, 2016


Can’t revert to initial (blank) test plan

There was a defect (classic pair-wise defect) that you could not revert to the first revision of a test plan if that first revision was completely blank. Now you can.



Use an expected result achievement via requirements expected result

The achievement of using an expected result can now come from using an expected result on a requirement instead of just an expected result in auto-scripts.


September 3, 2016


Explanation of purple italics popup on hover for each occurrence

Helps explain the significance of purple italics in resulting test cases.



No possible value popup not shown on subsequent viewings of test cases

The popup was only in place initially after test cases were generated, but coming back to the same test cases later, they did not have popups explaining the significance of “no possible value”. Now it does.



Moved the most critical generated test count information out of the title bar and info popup

This should improve getting key information about tests at a quick glance.


August 24, 2016


Keyboard triggered auto-complete in HP-QC / ALM export

In the test name and test description fields of the HP QC / ALM export dialog, you can now insert parameter values using keyboard autocomplete (similar to how it works in auto-script step fields) by typing the { character.



Import file field from copy plan dialog

This option doesn’t make sense when copying a plan.



Spurious change warning messages appeared when bulk editing parameter values that contain commas

An interesting pairwise defect.



Moved “Back to Plans” navigation in project permissions dialog to the top left to be more prominent and noticeable



Missing highlight on the “Create Tests” navigation when creating mixed-strength tests.



Initiating editing on an auto-script field causing it to scroll out of view

This annoying defect which only affected later steps (pairwise defect!) has been fixed.



Maximum parameter values for coverage matrix

The maximum number of parameter values your test plan can have and still use the coverage matrix visualization has been increased for users of Chrome and Firefox browsers. The new limits are:

Chrome: 100 parameter values Firefox: 85 parameter values IE: 75 parameter values


August 17, 2016


Search in test cases

You can now search for parameter values in test cases.



Total possible number of parameter value interactions

After creating tests you can see the total possible number of parameter value interactions your test cases are covering. This takes into account your value pair constraints. Hover over the information icon in the purple header bar when viewing test cases.



Sort, secondary sort and tertiary sort test cases

You can now sort test cases by the values of a specific parameter by clicking on the table heading for that parameter. Click it again to sort descending. You can also use shift-click to apply a secondary sort parameter, and even shift-click again to apply a tertiary sort parameter.


August 11, 2016


OPML Import

OPML files with specific data circumstances could fail to import.

Thanks to Regina for reporting the issue.


July 27, 2016


CSV Auto-scripts Export

Steps might be missing from the auto-scripts file when exporting in CSV. This is now fixed.

Thanks to Sam for reporting the issue!


July 20, 2016


Error when saving requirements after navigation prompt

Fixed a recent regression where choosing to save requirements after navigating away from the requirements page caused an error instead.

Thanks to our automated error reporting system for reporting this bug. 😄


July 19, 2016


Parameter change warning dialog

The dialog warning you of changes to value pairs and requirements caused by changes to parameters now has better wording and bolding for increased readability.



Freeze / thaw as versioned events

These did not trigger the saving of a revision before, now they do.



Requirements table UI coloring

Row hover coloring now matches test case table.



Freeze required test cases user interface

Freezing Hexawise generated test cases as required test cases now has full UI support.

We’ve had the freeze feature to lock in generated test cases for some time, but you had to know the secret handshake to use it. Freezing generated tests as required test cases isn’t usually necessary. It’s helpful when you invest a lot of effort in a specific set of Hexawise generated tests (such as automating them in a hard coded way, or determining the expected results of the test cases in a laborious manner) and don’t want subsequent minor additions to the test plan to result in an entirely new set of test cases.

Unless you have this unusual circumstance though, you should not freeze test cases as it doesn’t allow Hexawise to generate the most efficient set of tests as your test plan evolves.



Color indication for frozen test cases and required test cases

Frozen test cases in the requirements and create tests user interfaces are now colored blue for easy identification.


July 7, 2016


Very rare data issue that could prevent auto-script page from fully loading

Thank you to Charity for reporting the issue via chat!


June 22, 2016


Clearing Auto-scripts

This wasn’t working. Now it is. Simple as that.