If you had a Get Satisfaction account already with the same email as your Hexawise account, but were not logged into Get Satisfaction at the time you went to Get Satisfaction from Hexawise with the feedback widget (the lightbulb or the provide feedback link) then you'd see a somewhat gorped UI screen in step 3 of submitting your feedback.
This is a 3-way interaction for those of you playing along at home:
Get Satisfaction Account: Exising, Same as Hexawise Account
Current Get Satisfaction Login: No
Get Satisfaction SSO Action: Feedback
If the values of a pair meet these two specific conditions:
1) one value is an "any value"
2) the other value is value expanded
Then Hexawise might suggest a value for the "any value" (in purple italics) that violates an invalid pair.
If you have a plan that's exhibiting this behavior you'll need to force a recalculation (test generation results are cached) by changing something innocuous in your plan.
Thanks to Neil for pointing this out!
You no longer need to register for a Get Satisfaction account to use the Hexawise support forums. Just login to Hexawise and click on the light bulb, the provide feedback link or the support link and your Hexawise ID is all you need.
If you already have a Get Satisfaction ID, you'll continue to use that.
We made it 10x easier, now the burden is on you! Provide some great feedback.
In the past you could export an OPML file which can be opened with many mind mapping tools. Now you can also export a mind map directly as an easy-to-read image file if you don't have access to any mind mapping software that can open OPML files. The generated image will be emailed to the email address of your Hexawise account.
This feature is currently in beta and only available for plans with 24 or fewer parameters. Please send us any feedback or bug reports.
Thank you Wayne for encouraging us to prioritize this tool enhancement. We're sure other Hexawise users will also find it to be a useful way to share test plan information in a clear and concise format.
The triple here was: IE 7, brand new value pair, user hovers.
Each tab is handled a bit differently and this tab did not have everything escaped properly.
So you know that it is doing something.
In this case the pair was: double quote in the existing autoscript text, editing the auto-script text
This is resolved.
Some special characters and characters that amounted to HTML tags were not properly echo'd in the auto-scripts preview.
These were no longer included when we changed the format of this tab. But now they are back in the export. Thanks to Wayne for pointing this out to us.
Thanks to Dan for letting us know about it.
Ensure the most applicable checklist (Basic or Advanced) is displayed during login in the few corner cases where this was not happening already.
The value 'Unnamed' will be provided.
An issue in the error reporting logic would obscure the true issue.
Excel doesn't like cells that start with 0 being marked as numeric. Fixed this in the Excel exports.
Thanks to David for finding and reporting this one, which was tricky to track down and replicate.
Numbers > 10^32 cause errors in Excel export because the cell was marked as a number rather than a string. Thanks again to Nitin the "Excel Error Extricator".
For those keeping track at home, depending on how you designed your tests, this could be one of those rarest of birds, a 4-way bug in the wild!
Activity is export, Format is Excel, Value is a number, Size is > 10^32
With sufficient plug-ins or extensions installed, the detection of older versions of IE could have a false positive.
Thank you to Nitin for reporting the error.
These errors are timing related, and sensitive to network latency, so it is not possible to say they are definitively resolved for all users in all cases. The problem should be much rarer now though, if it still occurs at all.
There were some circumstances where the value suggested for an any possible value (in purple italics) would violate a married pair. This has been fixed.
Gives more user feedback when applying your selections.
The feedback now stays in place rather than disappearing after a moment.