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.
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.
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.
This option makes sense now that expected results are relative to a particular step of an auto-script.
This allows for more expressive expected result conditions, such as: "Customer Status" is not "Platinum" and "Customer Status" is not "Gold"
There is no longer an "Expected Results" tab. Expected results are now located in the "Auto-Scripts" tab and are associated with a particular step of an auto-script.
Your existing expected results have all been preserved and moved to what we've calculated to be the appropriate step in the auto-script (the step where they would have shown up when exporting auto-scripts). If your plan didn't have an auto-script before, but did have expected results, then we've created a one-step auto-script for you.
Please let us know if you have any questions about this change. We think it's a good change that makes the expected results feature easier to understand and use.
These are in the advanced checklist and have corresponding help content.
Using them twice in the same plan makes no sense, so they are no longer shown.
The new user's feature tour has been updated and expanded.
An extra export link appears at the bottom of the list of tests when you generate more than 300 tests, this extra link was not working.
Auto-scripts page now more closely follows the style of the rest of Hexawise.
There is now a drop-down of value expansions you've used in all your other plans so you can easily reuse them.
In case your Hexawise session times out, we used to take you back to the login page. This is no good if you have a bunch of unsaved edits in progress. Instead now we show you a login dialog and once you log back in you pick right back up editing where you left off.
Married pairs get green and invalid pairs get red hover highlighting.
Congratulations! Everyone is advanced! That's just how you all roll.
Save and cancel icons stay put when editing a requirement until you are done (they used to be visible only on hover).
These are now broken out into separate columns.
Parameters with just 1 value are no longer used in the strength interaction explanation dialog since they just confuse the explanation with their 1 value.
We decided it's more sensible after create tests.