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.

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.

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.

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.

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.

Requirement and Auto-Script delete confirmation dialogs

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

"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.

More room for requirements name and expected results

These fields could get awfully cramped in the UI. They are now more expansive.

Issue with blank HPQC exports

Certain sequence of events could result in a blank HPQC export. No longer.

Export dialog usability

You can now click on the Mind Map export radio buttons before clicking the checkbox. This is more user friendly.

Added back in the ability to download exports as well as email them

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.

Excel error opening exported file in rare cases

In case you are curious about the technical details. This was a relatively rare 3-way bug. It only occurred when:

• User is exporting to Excel
• User created value expansions with both newlines and carriage returns in them, rather than just newlines
• The value expansion value is interpretable as a number by Excel

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.

Dialog box resizing and positioning on window resize

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.

Error when erasing all parameters and values with bulk edit

This works now.

Dismiss the file import help dialog with the keyboard

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.

Wide-ranging system update to web client

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.

System messages on login

We can now talk to you with a message that pops up when you log in. Be afraid. Be very afraid.

Conditional expected result highlighting after unconditional results

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:

• First, entered an unconditional (e.g., "X should always happen after this step") Expected Result and then
• Second, entered an conditional (e.g., "only in certain situations should Y happen") Expected Result.

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!