The "Relax" auto-generate auto-scripts button would appear as soon as you had a step 1 that met the criteria, but the button didn't actually work until you saved the step. Now it works to save the step if it wasn't saved before.
The pair-wise coverage percentages are now floored to 1 decimal of precision rather than rounded so you won't have multiple tests that show 100.0% coverage in a large plan.
Thanks to Robin for pointing out how this could be confusing.
The practicum quizzes answers on security settings now match the new security setting labels.
This was a pairwise defect in the caching logic. Hexawise tries to be smart and show you existing cached n-way tests if it has them and you ask for mixed-strength tests with all the same strength. There was a defect when this all the same strength was not 2-way though.
Thanks to Vikramjit and Vikas for reporting this issue.
If you accidentally create a value expansion that doesn't correspond to a parameter value, or you edit or update a parameter value that has a corresponding value expansion, orphaning it, you know get an informative message letting you know.
Was newly empty except for a spinner in some cases. No longer.
There were graphical glitches if the browser window was sized very small.
Thanks to Melissa for letting us know about the issue.
When using the bulk add feature with some parameters that had greater than 8 values, a partial update would be applied before the handy warning dialog. Canceling the add would leave you with some (the small) parameters bulk added, and bypassing the warning would leave you with some parameters added in duplicate.
This is a classic pair-wise defect. To trigger it requires you to have params with > 8 values that occur after your smaller params in the plan, and to perform your adds using bulk add rather than single add.
This demonstrates that pairwise designed tests are only as good as the variability that's been identified. This is probably the most heavily tested part of Hexawise, with a strong battery of tests that have been automated, but the order of the large parameters compared to the small ones was never identified as a variation.
The bottom of the explanatory modal dialog was cut off leaving no white space. White space is back.
There is now a setting in the export dialog to pick your specific version of Microsoft Excel for Excel and HP QC exports so that any line breaks you have in your expected results or auto-scripts will be respected by Excel.
Thanks to Robin and Yue for nearly concurrent prompting in the forums asking for this feature.
Our automated error reporting alerted us to some uncommon but recurring errors being experienced in the requirements page and these were addressed.
Continuing the theme from last week, we revisited the sharing dialog itself and spruced up the UI to be more pleasing to the eye and changed the wording to be easier to understand.
Words more good. Me happy.
Some users of up to date version of the Firefox browser have experienced warning dialogs for the last couple weeks. These are resolved.
Thanks to John for alerting us to this issue.
Sharing plans in Hexawise has always been project based, and while that's not changing, we did make it much easier to share your plans. There is now a share link in the UI that takes you directly to the project sharing options, or if you're in a private plan, gives you the option to make a project for the plan.
A couple of the achievements on the path to Hexawise Guru were not ticking off properly. Thanks to Ed for pointing this out in the forums.
Hexawise.com is sporting a brand new website. Check out the new look!
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.
Improved the performance rendering plans with lots of value pairs.
A return on investment calculator is now available at http://app.hexawise.com/hexawise-roi.