Hexawise Recent Updates

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

Fixed

Regression in exporting Excel file with requirements that don’t have expected outcomes

 
 

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

Requirements UI properly inert for read-only test plans

Oh pairwise defects…. you are everywhere, aren’t you?

 

Improved

Remove requirements bulk delete confirmation when only one requirement is selected

 
 

Improved

Start cursor at end of existing text when editing requirements text fields, not at the beginning

 
 

Fixed

Properly name “Expected Outcome” column in Excel export

 
 

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.

 

Improved

Allow requirements description and expected outcome fields to scroll if long enough

 
 

Fixed

Missing tooltip explaining what “any valid value” means in test case table

 
 

November 3, 2018

Fixed

Excel export when auto-script step sequence doesn’t match code’s expectations

 
 

October 30, 2018

New

Hexawise coverage matrix chart now indicates the number of parameter value pairs covered with each test case increment

 
 

New

Explanation of why the Hexawise matrix chart only works for 2-way test cases

 
 

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

 
 

October 19, 2018

Improved

Hexawise Excel exports now use a modern Excel file format

They will no longer trigger an Excel warning about an incorrect file extension or a warning when saving the file after making changes.

 

October 18, 2018

Fixed

Regression in HP QC/ALM export

Thank you to Maria for reporting the issue.

 

October 11, 2018

Fixed

Issue with copied plans and test cases not initially appearing in Hexawise Automate

 
 

October 1, 2018

Improved

HP QC/ALM exports (which is an Excel file format) are now a modern Excel file format

They will no longer trigger an Excel warning about an incorrect file extension or a warning when saving the file after making changes.

 

September 28, 2018

Fixed

Special characters in plan names aren’t escaped for the export dialog

 
 

Improved

Exporting mind map PNG or SVG completes the mind map export achievement, not just exporting OPML

 
 

September 18, 2018

Improved

Better @tagging support in Gherkin in Hexawise Automate

 
 

New

Restricting test cases included in a feature file in the script’s Background section

Including {[Parameter]Parameter Value} text in the scripts background section limits the entire feature file to test cases that match the selection(s).