Hexawise recent updates

Hexawise recent updates

November 21, 2018
NEW
Requirement template for Excel

It's been possible to import requirements into Hexawise from Excel for some time, but it came with some substantial limitations. Only the name, description and expected results fields could be imported, not the forced inputs field.

There is now a requirements import template for Excel, customized for each specific test plan, that you can use to import requirements from Excel, including the forced inputs for each requirement. To get the template, just click on the import link in the requirements UI.

November 15, 2018
IMPROVED
Remove the possibility of double action in bulk update saving

Clicking multiple times too quickly would cause the operation to be attempted more than once.

November 12, 2018
IMPROVED
Parameter name and value truncation in the constraints UI

When parameter names and values have to be truncated in the constraints UI, there was no hover action to see the full value, like there is in the Inputs UI. Now both have the full value on hover.

November 9, 2018
FIXED
Issue requesting 1-way tests

For certain test plans aspects of the test plan prevented the 1-way test cases option (an Expert user feature) from working properly.

Irony alert: there was a pairwise (2-way) defect in selecting the option to generate 1-way (non-pairwise) test cases.

Thank you to Barby for reporting the defect.

FIXED
Plan export dialog on very narrow screens
November 7, 2018
FIXED
Broken link in auto-scripts help panel
FIXED
Incorrect link for key concepts of the "Create an auto-script" achievement
FIXED
Last modified time in plans dialog not always updated for all changes
November 6, 2018
FIXED
Implied value pair tooltip not showing

A pairwise defect led to the tooltip not activating on hover immediately after you get your first implied value pair for a plan.

IMPROVED
More room for implied value pair list

Now uses the complete panel height available.

November 5, 2018
IMPROVED
Allow requirements description and expected outcome fields to scroll if long enough
FIXED
Properly name "Expected Outcome" column in Excel export
IMPROVED
Start cursor at end of existing text when editing requirements text fields, not at the beginning
IMPROVED
Remove requirements bulk delete confirmation when only one requirement is selected
FIXED
Requirements UI properly inert for read-only test plans

Oh pairwise defects.... you are everywhere, aren't you?

IMPROVED
Requirements drag-n-drop

It's now easier to see where your drag will land, and it's now possible to drag a requirement into position as the first requirement.

FIXED
Missing tooltip explaining what "any valid value" means in test case table
IMPROVED
"By golly old chap, is that a uni-directional married pair or a reverse bi-directional married pair you've got there?"

"Uh... are you speaking English?"

We've canned the 1,000 of words in favor of simpler pictures in the married pairs constraint dialog. We hope this is much, much simpler for everyone. Please let us know if we hit the mark!

NEW
Hexawise provided implied constraints: Death to the "no possible value"!

Many months in the making, and the most exciting thing to come out since Apple reinvented the phone, Hexawise will now generate the missing constraints that the parameters inputs and constraints you've provided logically imply should exist. No more playing Russell or Wittgenstein (Confused? Wikipedia is your friend.) And, no more "no possible value".

Disclaimer: you could still run into a "no possible value" by flaunting Hexawise's helpful feedback, or because there's a bug in this new feature. If you do run into a "no possible value" still, please let us know. We'd love to look at it with you to determine what's up.

FIXED
Regression in exporting Excel file with requirements that don't have expected outcomes
November 3, 2018
FIXED
Excel export when auto-script step sequence doesn't match code's expectations
October 30, 2018
IMPROVED
Hexawise matrix chart slider styling

Now easier to read and use.

NEW
Quick jump back to 80% coverage in the Hexawise coverage matrix chart
NEW
Explanation of why the Hexawise matrix chart only works for 2-way test cases
NEW
Hexawise coverage matrix chart now indicates the number of parameter value pairs covered with each test case increment