You can now click on the Mind Map export radio buttons before clicking the checkbox. This is more user friendly.
In most cases you'll want to directly d/l exports. Do note that if the plan is extremely complex and the export takes so long that your browser client times-out, you may have to use the email option, which is not subject to browser timeout limitations.
In case you are curious about the technical details. This was a relatively rare 3-way bug. It only occurred when:
These the variables together caused there to be a number cell with a carriage return in it, which Excel is distinctly unhappy about.
Thank you to Mary for finding and reporting the issue.
If you happen to resize the browser window with a Hexawise modal dialog box open, it'll now respond much better in keeping the modal dialog roughly where it should be.
This works now.
This dialog is too big for tiny screens and both the OK button and X could be obscured leaving you no way to dismiss the dialog other than to refresh the page. You can now dismiss the dialog with enter or ESC.
We've swapped out the JavaScript plumbing that powers the Web UI for Hexawise, so if you see any issues on your configuration, please let us know.
We can now talk to you with a message that pops up when you log in. Be afraid. Be very afraid.
In our Auto-Script screen, we want to make it easy for testers to determine when the Expected Results they've entered will appear and when they won't. So we've color coded them. When users create Expected Results and then highlight test scripts on the bottom of their screen, the color of the Expected Result is supposed to change from green (in tests that contain the Expected Result) to red (where the Expected Result does not appear). In one weird case, this wasn't working.
It turned out to be a pairwise bug. Specifically, it wasn't working properly when a user:
Incidentally, we're classifying this one as a "grapefruit juice bug" (blog post coming soon) because our lead developer wrote this:
"Justin, The fix is in place. Unsurprisingly it was a pairwise issue. The kind that developers would tell a tester 'that can't exist.'
Cheers, Sean"
Thank you Prathiba for bringing this issue to our attention!
This possibility of auto-creating this logical tautology was removed and the DB was swept of any cases where this had occurred.
Some of the text in the tour was improved to be more clear for new users.
Two cases of level 1 value pairs that can be logically implied but were missed and were not auto-created for you are now created properly.
Thank you Rick for bringing this issue to our attention!
The great resources at help.hexawise.com and hexawise.tv are now mentioned in the support page.
Hexawise's ability to present the value pairs in the most logical, top to bottom, left to right, order is much improved after some defects in ordering were resolved.
The exporting of mind map files is now allowed regardless of whether the user first deselects the option to export Excel files.
Thank you, Pratibha!
Hexawise now analyzes the logic of your value pairs (invalid pairs and married pairs) to determine if other value pairs are necessary to avoid having "no possible values" in your test cases. If additional value pairs are needed, Hexawise creates them and lets you know what that it did.
The analysis is thorough, it will create the needed value pairs in all 24 possible scenarios where they are necessary. Here are two examples:
Existing: when A is A1 then B is B1
New: when B is B1 then C is C1
Logically implied and added: when A is A1 then C is C1
Existing: A is A1 never B is B1
New: C is C1 always A is A1
Logically implied and added: B is B1 never C is C1
But the analysis is only 1 level deep. it won't find value pairs necessitated by multi-level relationships that may exist, and so it's still possible to have "no possible values" in test cases. Here's an example of a 2-level logical necessity it won't find for you automatically:
Existing: when A is A1 then B is B1
Existing: when C is C1 then D is D1
New: when B is B1 then C is C1
Logically implied and added: when A is A1 then C is C1
Logically implied and added: when B is B1 then D is D1
Logically implied but NOT added: when A is A1 then D is D1
NOTE: This only works while creating new value pairs, so it won't help you eliminate "no possible values" in existing test plans caused by already existing value pairs (unless you delete your value pairs and recreate them).
The order of the created uni-directional married pair would be reversed in certain cases. This is now fixed.
This change addresses an issue when exporting very large plans. The HTTP request/response cycle could time out before the export had been completely generated in some cases.
If you preferred our old export option, please let us know by emailing us at support@hexawise.com. Thank you.
This is addressed and expected results export as expected now.
Thanks to Justin G. for pointing out this issue.
Some isolated issues exporting involving certain Unicode characters in certain positions in the plan have been addressed.
If you have lots of expected results on a step, and you click to add more, you could easily not notice that the form for adding new expected results is now shown since it would be out of sight. Hexawise now scrolls to the form when you click the link.
Value pairs in the side panel are now sorted in Param (primary) Param Value (secondary) order rather than in the order they are created. This makes scanning down the list of value pairs to ensure you have all the pairings you need much easier.
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.