Auto-Auto-Scripts

If you have a lot of parameters in your plan, creating an auto-script can be tedious if the vast majority of the steps have the exact same format.

Relax! Auto-Auto-Scripts are here to take away the tedium.

If you add the parameter name and parameter value replacement (use the insert drop down in the top right of the step) of the very first parameter in your plan to the first and only step of your auto-script, a new button appears that lets your automatically generate your auto-scripts based on the pattern you used in the first step for the first paramater.

Additional steps are created for each additional parameter in your test plan, and these new steps follow the same pattern of language as your first step. Then you can delete any steps that don't apply.

Thanks to Amit for the idea and for testing and feedback on the initial version.

Clicking a test case row in "Create Tests" is no longer sticky

You can click a test case row to highlight it (for contemplation or discussion), but this highlighting was unintentionally "sticky". Now clicking another row will result in just 1 highlight.

"No possible value" now includes an explanatory tooltip

There is a tooltip on "No possible value" test case values that explains, in a generic fashion, why there is no possible value. An upcoming enhancement will make this explanation more specific.

Plan import when specified expected results are not valid

Hexawise would silently skip auto-script expected results that did not correspond to the parameters and parameter values specified in the imported plan or otherwise had invalid syntax. Now Hexawise does not allow the import and notifies you exactly where the problem occurred in the import file.

Cyrillic characters in requirements not properly encoded

Plan import when specified value pairs are not valid

Hexawise would silently skip invalid and married pairs that did not correspond to the parameters and parameter values specified in the imported plan. Now Hexawise does not allow the import and notifies you exactly where the problem occurred in the import file.

Issue with saving % in requirements and auto-scripts

There was an interesting pair-wise bug where saving a requirement name or expected result with a % in it, or an auto-script step or expected result with a % in it was broken, but only when saving via the warning dialog that informs you of unsaved changes.

Performance of initial rendering of large sets of generated tests

A large set of tests (a couple thousand) would take a minute or more to render the final sets of parameter values once the tests had been generated (they are generated as parameter indexes). In many cases this was actually a fairly significant portion of the total computation time. This rendering time has been reduced about 6x.

This won't be noticeable on typical sets of generated tests (dozens to a couple hundred), but once you get beyond 500 or so generated tests there should be a noticeable improvement.

Frequency and accuracy of the computation completion percentage

Now with 2% more accuracy. (That was a self-referential joke.)

Export -> import issue

Fixed a problem importing exported plans that contained certain special characters. Thanks to Chris for finding this issue and reporting it.

Unable to add value pairs until after a refresh after adds in a specific case

If you had just 1 parameter in a plan, then add more with bulk add, you would not be able to make invalid and married pairs with the original parameter until after a refresh.

Thanks to Scott for finding this one and pointing it out.

Reset password message

If you have already used a reset password link and click it again in your email, the wording of the message is now a bit more helpful.

There was an unintentional decay in how often requests were checked which meant that very often larger compute requests were completed but the the user interface still indicated they were in progress.

There was an unintentional decay in how often requests were checked which meant that very often larger compute requests were completed but the the user interface still indicated they were in progress.

Clicking edit on parameters

There is now a spinner indicating the edit activity is occurring, and the top panel is expanded if it was collapsed, and increased in size if it was sized very small, so that you can see where the editing will occur.

Error when deleting the project containing the currently displayed plan

The deletion worked fine but you received an error and needed to refresh. It now works properly.

Bulk update editing multiple required paramaters

This was a rare 3-way defect in production. It only happened if you were bulk editing parameters and removed parameter values that were used in requirements, and you removed more than 1 of them in a single edit.

Export UI glitch

The email and download buttons would not enable correctly if no other format type was selected and the mind map format (OPML or image) was selected directly rather than by picking the mind map checkbox first.

Given most ways you'd likely develop a test plan for this dialog, this counts as a rare 3-way defect found in production. Thanks to Scott for his eagle-eye in spotting this and generosity in reporting it.

Invalid pairs in your test cases that exist to satisfy requirements

There was an interaction between invalid pairs and requirements that effected some plans and could cause an invalidated pair to still appear in initial test cases that were satisfying created requirements.

This has been resolved. Thanks to Fabio for noticing and reporting the error.

Emailing two mind map image exports each time it's requested

Thanks to Scott for reporting this.

Import and export of auto-script definitions

There were cases where the exported auto-script definition would not be able to be imported. These cases were cleaned up.

Example Excel input file

The example Excel input file is now much more comprehensive including sheets for everything that can be imported.

Parameter order changes did not clear the generated test cache

If the only thing you changed in your test plan was the parameter order, the prior generated tests were held onto and would be displayed with mismatched column headers. The computed test cache is now cleared when you reorder parameters.

Thanks to Scott for letting us know.

% in requirement value

There were issues saving requirements where the required value contained a % sign.

Moving parameters at the boundaries

Moving the top parameter "up" in the parameter order, or the bottom parameter "down" in the parameter order would cause the parameter to disappear until a page refresh. The parameter now "wraps" to the opposite side.

Thanks to Manas for reporting the bug.

Value expansion achievement

In some circumstances the "Create your 3rd value expansion" achievement would not be awarded.

Thanks to "Hexawise Guru" Del for raising the issue to our attention.