The requirements import used to assume the first 3 columns in the import file were the designated name, description and expected outcome columns. It now looks at the column headers.
An unusual scenario involving two browser tabs editing the same test plan could result in a blank Hexawise UI after attempting to export. Not any more.
These are now escaped appropriately so Excel doesn't see the cells as formulas.
Thanks to Vikramjeet for reporting the issue.
Fixed a regression where the delete all constraints action actually deleted nothing.
“Tired, tired with nothing, tired with everything, tired with the world’s weight he had never chosen to bear.” ― F. Scott Fitzgerald
Hexawise now ensures your parameter inputs and constraint logic are always working well together through the use of the generated implied value pairs (constraints). This keeps you from having any "no possible value" scenarios in your generated test cases.
There are however certain bulk modifications you can make to your test plan in bulk edit where Hexawise knows you are going to end up with "no possible value" scenarios, but we don't want to simply prohibit those changes when you want to make them. Instead now, with this new addition, Hexawise will present a warning, and if the warning isn't heeded the test plan will contain a banner indicating it's in a state where some of the values in the generated test cases will contain "no possible value". Once the inputs and constraints are brought back in sync to be logically consistent (Hexawise still helps with this where it can) the banner will clear out on its own.
When we moved to the new graphical married pair creation dialog we stopped using the order in which parameter values were clicked to layout the dialog. We got feedback that even though the constraint can be expressed regardless of the order, it's less confusing if the click order is used for the layout. We now use click order in the dialog again.
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.
The internal revision format was recently modified and this caused a regression in specific cases when reverting or copying old revisions.
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.
Now uses the complete panel height available.
A pairwise defect led to the tooltip not activating on hover immediately after you get your first implied value pair for a plan.
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.
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.
Oh pairwise defects.... you are everywhere, aren't you?