There was no new step and add step link after initial save of step 1 in Auto-Scripts

Another classic pair-wise defect, it had to be the first step, and it had to be the initial save for the defect to be triggered.

Thanks to Pratibha again for discovering and reporting the issue.

Auto-Scripts preview would disappear after it was collapsed in some plans

This is now fixed. Thanks to Fabio for reporting the issue.

Issue with the blank first step disappearing in Auto-Scripts if editing is canceled before an initial save

A classic pair-wise defect, it had to be the first step, and the user had to cancel w/o editing.

Thanks to Pratibha for discovering and reporting the issue.

Issue getting to the married pair link on the last parameter value of long parameter value lists

This has been resolved. Thanks to Alicia for reporting it.

Don't show Auto-Scripts preview panel when it can't be used

There is one case where the preview can't be used, that's in a read-only plan with no generated tests. In this uncommon case the preview panel is no longer shown.

Excel export issue in IE7

Some plans would not successfully export on IE7 only. This has been resolved.

Value Expansions now include the Parameter Value

Previously a Value Expansion of the Parameter Value "fruit" to "Apple", "Banana" and "Pear" would result in values in the test case of "Apple", "Banana" and "Pear". Now we include the Parameter Value too, with a dash separator, so the values are "Fruit - Apple", "Fruit - Banana" and "Fruit - Pear".

No horizontal scroll bar to get to top right menus on smaller browser windows

If the browser window is too small horizontally, a horizontal scroll bar is now provided to ensure you can reach all the right top menus.

Attack of the Frogs!

Hexawise now features an achievement roadmap that guides you on your journey from pair-wise novice to combinatorial guru.

The path from novice to practitioner, on to expert, and ultimately to being a guru involves taking advantage of increasingly sophisticated Hexawise features and showing your mastery of pair-wise test design techniques.

Send us your feedback and have fun learning!

Vertical window resizing on the Auto-Scripts tab

As the window height decreased, space would no be apportioned properly like the other tabs. This is fixed.

Acting on a deleted plan in an old tab

Now redirects you to the initial app start location rather than to the error page.

Support and Logout link overlapping on some resolutions of IE8

A pairwise defect, only affecting IE8 at specific screen resolutions.

Thanks to Amanda for reporting the defect.

Graphical glitch in table border in Create Tests and Requirements

A small graphical glitch has been fixed.

Requirement and Auto-Script delete confirmation dialogs

Fixed a graphical glitch and allow the dialogs to be dismissed with the enter key.

Export of HP QC and Excel at the same time

Exporting these at the same time would result in both files containing the HP QC export. Either worked fine singly, so this is a classic pairwise defect.

Exporting plans that contain XML/HTML in parameter names, parameter values, auto-script steps, expected results, etc.

HTML/XML content is now escaped before exporting to Excel or any of the Excel based export formats (like HPQC).

Thanks to Cortney and Wayne for reporting this issue.

Blank title bar on the pop-up for notes that contain just 1 line

These notes now don't have a title bar.

Flexibility in admin's setup of HP QC Export

Administrators for paying customers can custom configure the HP QC export for their own HP QC instance. This now includes the ability to provide alternative names for the fields that are always present in the export.

"How To" instructions provided to help you use the Married Pair feature

We've just added help file instructions for using the Married Pairs feature (together with a worked example that explains WHEN and WHY you will want to use it.

This information about how to use Hexawise's Married Pairs feature is available here

Value pair highlighting could get stuck on pair removal

If you dismissed the pair removal confirmation dialog with the keyboard rather than the mouse (a truly classic pairwise defect) the highlighting of the pair in the parameter/values table would get stuck until a refresh. No longer is this the case.

Invalid pair and married pair order in Excel exports

They used to be in created at order, but they now match the value pair ordering in the UI (which is in what we call, "plan order").

Suggested "Copy..." plan name

We will no longer suggest any plan name for your copied plan (defaults to: Copy of plan name) that will conflict with a plan you (or the project) already has.

If you do something really tricky, such as simultaneously move the copy to a project that has a plan with the name that we suggest. If you do that, then you are on your own, and you get what you deserve (a scolding warning message) you sneaky devil.

Expected result condition parameters not getting copied on plan copy

Copying a plan could result in the new copy not having the expected result paramater names selected for the conditions. This is now resolved.

Uni-directional value pairs would get their parameters improperly re-ordered

Parameters are now put in "plan order" in invalid pairs and bi-directional married pairs, where the ordering is inconsequential, but uni-directional married pairs were similarly re-ordered, which changes their semantics. No longer.

Problem inserting parameters into auto-script steps on IE

Resolved.