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!
Now you receive a helpful message before a round trip to the server is attempted.
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.
This was a temporary regression which is now fixed.
This was fixed for a specific case with a more generalized fix to follow.
This was a temporary regression which is now fixed.
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.
For new plans, the majority of the screen is portioned to the top panel with the auto-script steps rather than the bottom preview panel.
The step and expected result text areas in auto-scripts are now resizable on all browsers except Internet Explorer to give you a bit more room to type and edit when you need it.
The list of value expansions could get cut off when importing from an Excel file. This is now resolved.
If you are editing your auto-scripts outside the tool in Excel, the expected results conditions for a a step used to be marked with bolding. This proved to be brittle to different versions of Excel representing bolding in different ways, so this has been replaced with the curly bracket { } syntax used elsewhere throughout the Excel file format.
To see an example of this, look at the sample Excel import file linked from the "Create New Test Plan" dialog, or export an Excel export of a plan that has at least one auto-script step with an expected result condition, then look at the "Auto-Script Definitions" tab.
If your login to Hexawise times out, we prompt you to log back in. Not a big disruption. But what if you timed out just before submitting a big edit to your plan, or you just completed showing your competency by answering some questions to level up? In some of these scenarios, the action you were trying to take would be lost.
We've done a lot of work to try to eliminate these cases and ensure that you'll never lose what you were trying to do to a timed out login. It's not perfect yet, but it's much, much better.
This link, located in the header bar of the Auto-Script panel anytime you have more than 2 steps in your Auto-Scripts was low contrast. Now it isn't.
If you had plans with a very large number of parameters and very large number of generated test values the export dialog would take a long time to load. While the export will take a while in this case, the export dialog should not.
In rare cases, the latter of numerous requirements could be ignored and not included in the generated tests.
Thanks to Andrew for reporting the issue.
Once there were enough value pairs to force a scroll bar and if the parameter names were long enough, not enough space was reserved for the delete icon forcing Chrome to resize it into a tiny, Alice in Wonderland icon. This was a 3-way bug if you are keeping track: Chrome, lots of value pairs, long parameter names and values.
This one has been around for a couple years now. We've seen it pop up once a month or so in our automated bug reporting system, but could never replicate it. That's because the interactions it requires to trigger the defect are of the "those could never interact variety". It required a specific browser, specific data, and a specific sequence of events including an action that you wouldn't suspect has any relation to the data.
Andrew "Sherlock Holmes" Shindyapin finally tracked it down:
If you are in Internet Explorer, AND you create a new plan, AND you enter a plan name that contains unicode characters into the dialog, AND you then click on the "what kind of files" link, then you got an error.
Now you don't.
In Internet Explorer, when selecting a parameter from the parameter name drop down to reuse it from another plan, the parameter values would all be on one line rather than newline delimited. This is fixed.