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.

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

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.

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

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.

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

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

Properly name "Expected Outcome" column in Excel export

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

Remove requirements bulk delete confirmation when only one requirement is selected

Requirements UI properly inert for read-only test plans

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

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

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

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

Hexawise matrix chart slider styling

Now easier to read and use.

Quick jump back to 80% coverage in the Hexawise coverage matrix chart

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.

Regression in HP QC/ALM export

Thank you to Maria for reporting the issue.

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

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.

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

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

Changing test plan strength while viewing scripts in Hexawise Automate

Better @tagging support in Gherkin in Hexawise Automate

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