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.
Clicking multiple times too quickly would cause the operation to be attempted more than once.
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.
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.
A pairwise defect led to the tooltip not activating on hover immediately after you get your first implied value pair for a plan.
Now uses the complete panel height available.
Oh pairwise defects.... you are everywhere, aren't you?
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.
"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!
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.
Now easier to read and use.