You can now update a parameter name (change only the parameter name in the single parameter update, not using bulk update) and it will update the parameter reference in any requirements, value pairs and auto-scripts, rather than warning you and then deleting them.
After making a bulk edit with the only change being the order of the parameters, cached generated test cases would be displayed with the wrong parameter headers.
Thanks to Mary for reporting the bug.
A return on investment calculator is now available at http://app.hexawise.com/hexawise-roi.
Improved the performance rendering plans with lots of value pairs.
The project permissions dialog had some weird behavior when mousing around it in Internet Explorer. Classic pair-wise defect.
Thanks to Ravinder for the bug report.
In some cases after doing a bulk edit the parameters would be shown out of order until the browser was refreshed.
This was a classic regression after performance improvements were made to bulk editing. Parameter order wasn't checked in the test cases.
There is now a drop down list in the header of the Auto-Scripts preview test selection panel that allows you to use tests other than 2-way to preview your Auto-Scripts.
When updating your password, there is now a checklist of password requirements to be fulfilled.
Doing a bulk parameter edit on a very large plan is now about 10x faster.
If you were not very relaxed when you using the "Relax" button, you might have noticed the button wasn't disabled and there was no spinner while the system was relaxing. Now there is.
Fixed a rare case where submitting a quiz would fail. It was an unusual 2-way pairing that triggered the defect. Submit a quiz with one a more answers blank, and you have a previous unsuccessful attempt at passing the quiz.
The moral of this defect, consider "history" when designing your test inputs.
Error messages about issues with a plan import file are now more helpful and descriptive, especially with value expansions.
When creating initial password at registration, there is now a checklist of password requirements to be fulfilled.
Fixed a generic error page when importing certain types of invalid requirements sheets in an Excel file import.
Line breaks in Auto-Script steps and expected results are now exported into Excel and HP QC as functioning line breaks.
More general fix for all other cases and sheets.
Oooohh.... pretty!
This was a temporary regression which is now fixed.
You are now warned when creating a new value pair that conflicts with an existing requirement, or when creating a new requirement that conflicts with an existing value pair.
Requirements and value pairs are allowed to conflict (the requirement takes precedence), but this is generally not what you want so the warning is usually quite helpful.
Thanks to Amit for the suggestion.
Now you receive a helpful message before a round trip to the server is attempted.
This was a temporary regression which is now fixed.
This was fixed for a specific case with a more generalized fix to follow.
You can now import using the edit plan dialog (click the pencil icon by the plan name). Importing into an existing plan is a shortcut for deleting the plan and starting it anew with a new plan via import. The plan is completely replaced by the contents of the import.
There was an issue with the z-order that could cause the value expansions drop down combo text box list of prior value expansions to be hidden. Thanks to Kevin and Rathiv for reporting the issue.
If you use one of a few different parameter names that are often used to describe expected results, Hexawise will show a suggestion that you shouldn't enter expected results as test inputs.