Thanks to Justin G. for pointing out this issue.
Some isolated issues exporting involving certain Unicode characters in certain positions in the plan have been addressed.
If you have lots of expected results on a step, and you click to add more, you could easily not notice that the form for adding new expected results is now shown since it would be out of sight. Hexawise now scrolls to the form when you click the link.
Value pairs in the side panel are now sorted in Param (primary) Param Value (secondary) order rather than in the order they are created. This makes scanning down the list of value pairs to ensure you have all the pairings you need much easier.
The test that's selected in the auto-scripts preview will drive color coding (red and green) of the expected result to show wether that test will trigger the expected result or not.
There was a case where bi-directionally marrying a pair where the 1st value of the new pair matched the 2nd value of an existing pair would not be allowed and a (non-existent) conflict would be reported. This is a pairwise defect for those keeping track at home.
Before it wasn't visible until a plan was selected.
This is valid, but wasn't previously allowed.
Parameter values that are ranges that also overlap with other values of the same parameter could be very confusing. You couldn't be certain which value was being tested in a specific test and it could make it appear as if value pairs aren't being respected.
Hexawise now detects range values which overlap with another range value or value of the same parameter and doesn't expand them (they stay their literal value "1-100" rather than some expansion, "59").
Corresponds to how expected results now work in auto-scripts.
Now takes you directly to the tutorial rather than to an interstitial link.
Removing parameters (completely or by changing their name) during bulk edit operation now warns you if the operation will result in expected results getting changed or removed.
You can update a parameter name without affecting the expected results by using the single, rather than bulk, update.
Thanks to Harmony for reporting the issue.
This only occurred if the value was long enough to need truncated, the special character was early enough in the value to be before the truncation, and the value was used in a value pair. The rare 3-way defect caught in the wild!
The warning that appears when an insufficient number of parameters are selected for mixed-strength testing is now much more apparent and hard to miss and it indicates which columns have the additional, but insufficiently selected strength.
Value pair highlighting (red and green) is now more reliable immediately after value pair creation, before the page is refreshed.
There were issues when selecting same parameter that already had an "is not" criteria.
The drop down list for value expansions is changed back to how it used to behave and only shows the parameter values that exist in the plan. The list was changed to show other parameter values when the improvement was made to allow prior value expansions to be reused.
An expected result with no condition is always triggered for the auto-script step. This simplifies things and allowed us to remove the "any value" value from the expected results condition.
Highlights are now always red or green (invalid and married respectively), even over the hover'd value, unless there are both invalid and married pairs associated with the hovered value in which case it's highlighted in orange.
If you canceled the married pair creation dialog with the dialog close icon rather than the cancel link the selection remained. It no longer does.
Now mentions some more of the training assets that are available to help you learn how to use Hexawise.
The dialog that warns you when you make changes to parameters that will impact your requirements, value pairs, auto-scripts, expected results or HPQC exports had a series of fixes to the cases it properly detects and also some fixed typos in the warning language.
This issue is now resolved.