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.
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.
You can now search for parameter values in test cases.
OPML files with specific data circumstances could fail to import.
Thanks to Regina for reporting the issue.
Steps might be missing from the auto-scripts file when exporting in CSV. This is now fixed.
Thanks to Sam for reporting the issue!
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. 😄
Row hover coloring now matches test case table.
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.
Frozen test cases in the requirements and create tests user interfaces are now colored blue for easy identification.
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.
These did not trigger the saving of a revision before, now they do.
Thank you to Charity for reporting the issue via chat!
This wasn't working. Now it is. Simple as that.
It was difficult to read all the information about file formats for importing on smaller height screens. This dialog now scrolls.
Detailed explanation of the cause of the failure when importing Excel test plans were not being shown. Now they are again.
There was a remaining Auto-script saving issue that was a 2-way defect only triggered when the conditions of the expected result were blank (always expected).
A big thank you to Lakshmi for an excellent bug report on this issue.
You can now provide labels to specific meaningful revisions of your plan. Simply open the plan revisions dialog and click on the numeric revision label and replace it with a meaningful label such as "Beta 3", "Reviewed", "Approved by Doug", "1.0.13.april", or "Sell by June 3".
Whatever makes that revision special, you can label it as such.
Fixed some issues with saving Auto-script Expected Results and unsaved changes messages in the Auto-scripts UI.
The dialog informing you of auto-generated value pairs did not constrain the height, so if a very large number of value pairs were generated, the dialog would be too tall for the screen. The height is now limited and the dialog is scrollable.
Plans that will generate a minimum of tens of thousands of tests and therefore won't be computed now include the message on both top and bottom panels of the UI, rather than the message on the top and a misleading progress indicator in the bottom panel.
The header describing the columns of the data in the plan revisions dialog is now fixed as your scroll through all the revisions of your plan.
Each revision to your plan includes a verbose description of what changed with the revision. These descriptions are now searchable in the plan revision dialog.
Need to know when "Gold Medallion Level" got removed from your test plan? Now you can search and find out!
Need to know who added "N/A" as a value to the "User" parameter and when they did? It's just a quick search away.