"Jitters" in the define inputs page on narrow screens or windows

Color-coding on expected results to show if they apply to the selected test

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.

Tooltips on long notes could expand to the left rather than the right and so be off the screen

Married pair creation improperly disallowed

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.

Show the how-to progress checklist immediately after login

Before it wasn't visible until a plan was selected.

Allow more than 2 "is not" conditions on the same parameter in expected results

This is valid, but wasn't previously allowed.

Range expansion when ranges overlap

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").

Expected results content in how-to progress checklist is updated

Corresponds to how expected results now work in auto-scripts.

Requirements and Auto-Script tutorial notice

Now takes you directly to the tutorial rather than to an interstitial link.

No warning about deleting expected results during bulk edit

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.

Encoding issues with special characters in value pair values

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!

More apparent when mixed-strength is incorrectly used

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

Value pair highlighting (red and green) is now more reliable immediately after value pair creation, before the page is refreshed.

Issues with validation logic in expected results criteria selection

There were issues when selecting same parameter that already had an "is not" criteria.

Value expansion drop down list

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.

Expected Results can have no conditions (always triggered)

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.

Value pair highlighting

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.

Canceling married pair creation

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.

Available help portion of the new user tour

Now mentions some more of the training assets that are available to help you learn how to use Hexawise.

Parameter update warning dialog

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.

Issue with expected result from a requirement not appearing when the requirement contained a range value

This issue is now resolved.

Expected results can have no condition and always be true

This option makes sense now that expected results are relative to a particular step of an auto-script.

Multiple "is not" conditions are allowed on the same parameter in an expected result

This allows for more expressive expected result conditions, such as: "Customer Status" is not "Platinum" and "Customer Status" is not "Gold"

Expected results are moved into auto-scripts

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.

How-To Progress Checklist items for required test cases and expected results

These are in the advanced checklist and have corresponding help content.