There was a defect where the save action would remain disabled after getting a warning about duplicating a parameter name when editing in the mind map view.
Special characters that are reserved in XML would cause rendering issues in the SVG mind map display (a classic type of pair-wise data variation defect). They no longer do.
When searching and sorting of generated test cases was added, we removed the prior limit of displaying 300 test cases at a time. Unfortunately as test plans get large and into the thousands of test cases, the burden on the browser JavaScript engine to parse and render all that test case data was too much for slower browsers (IE) and slower computers. We restored a limit (up to 500 now).
If you've generated more than 500 test cases (that's a lot of test cases!) you can once again see them all by exporting.
Inserting parameters into the export fields with the keyboard was not working. Now it's fixed.
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 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.
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 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.
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 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. 😄
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.