We decided it makes more sense to show all requirements as frozen after freezing test cases rather than leaving existing requirements as unfrozen, since existing requirements are usually modified during freezing.
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.
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.
The rest of the fields in the insert drop down (plan name, test #, etc) that are not parameter names are now available via text auto-complete in the HP QC / ALM export dialog.
Helps explain the significance of purple italics in resulting 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.
This should improve getting key information about tests at a quick glance.
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.
This option doesn't make sense when copying a plan.
An interesting pairwise defect.
This annoying defect which only affected later steps (pairwise defect!) has been fixed.
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
You can now search for parameter values in test cases.
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.
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. 😄
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.