Chrome specific, so a 2-way defect.
A relatively rare 3-way defect in production. To trigger the issue you needed a test case with any "any value" that was then replaced with a value that happened to cause a value pair constraint violation so was then replaced with a value that happened to be a range. In this case, the range stayed as is and was not changed to a value within the numeric range.
If you have some requirements, then freeze your test cases, and later need to thaw the test cases, your required test cases are preserved. Your prior required test cases will then contain a value for all parameters, but they will no longer be removed completely when you thaw.
Getting started, intermediate and advanced user guides are available in the Hexawise help.
Improve disabled disabled state and disabled message when HP ALM and Gherkin export are disabled.
You can export your Hexawise generated test cases in the data-driven Gherkin examples format for use in scenario outlines in your Gherkin, BDD automated tests.
This was a recent regression.
This message didn't match the web plan scorecard and the web plan scorecard was correct.
Thanks to new intern Scott for this, his first bug fix of the summer!
It's true the requirement is still duplicated, but the second warning is difficult to understand since all you doing is changing the name or expected result.
A classic pairwise defect, only happened when there was both special characters in the tooltip and a tooltip long enough note for truncation. Either case on its own worked with no problem.
If a mixed-strength test case generation was requested with the re-apply button and an insufficient number of parameters were selected for the highest selected strength (3 for 3-way or 4 for 4-way, etc.) then the error message was missing and instead there was a blank panel.
This was a regression that started when we added the enhanced, searchable and sortable test case table.
Thanks to Ryan for reporting this bug via chat.
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!
The tooltips that explain "purple italics" are now also in the test case table on the Auto-Scripts page.
This was a classic pairwise defect that is only triggered for the pairing of multi-strength and > 500 test cases.
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.
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.
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: 192.10.1.1, 208.55.76.11
Car: Datsun, Yugo
Thanks to Eva for requesting this enhancement.