February 6, 2017
Special character in requirement name during Excel export
This was a 3-way defect: you had to have auto-scripts in your test plan, have a less than
< character in your requirement name, and be exporting to Excel.
Thanks to Pam for reporting the issue!
January 25, 2017
Tooltips explaining “purple italics” in test case table on Auto-Scripts
The tooltips that explain “purple italics” are now also in the test case table on the Auto-Scripts page.
Truncated long parameter names were not replaced in Auto-Scripts
Instructions for achieving the “View the sample plans” achievement
November 25, 2016
Can’t specify mixed-strengths when there are more than 500 test cases
This was a classic pairwise defect that is only triggered for the pairing of multi-strength and > 500 test cases.
Can’t access “Key Concepts” links for some quizzes
November 10, 2016
Erroneous duplicate name error when using esaped colons in bulk edit
October 30, 2016
Handling very long parameter names and values in generated test case table
Very long parameter names and values are now truncated (with a tooltip to see the whole value) to save space when displaying generated test cases.
September 28, 2016
Rendering large number of test cases
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.
Existing requirements are frozen too after freezing test cases
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.
“ampersand-quot;” could be seen in some cases in expected results rather than the “ character
Escape colons in parameter names in bulk edit
You could always have a : in your parameter name in single parameter edits, but it wasn’t possible to add or edit parameters with colons in bulk edit since the colon character delimits the boundary between the parameter name and parameter values. Now you can escape an colon in a parameter name with : in bulk edit. Example:
Fruit: Apple, Pear, Banana
IP\:Address: 220.127.116.11, 18.104.22.168
Car: Datsun, Yugo
Thanks to Eva for requesting this enhancement.
Save parameter edits after a duplicate parameter name warning in mind map
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.
Rendering special characters in mind maps
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.
Keyboard inserts in HP QC / ALM export dialog
Inserting parameters into the export fields with the keyboard was not working. Now it’s fixed.
September 8, 2016
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.
UI glitches in value pair dialog
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.
Additional fields in HP QC / ALM export auto-complete
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.
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
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
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.