November 29, 2018
Delete all constraints
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
November 28, 2018
Hexawise flags a test plan when you allow it to temporarily contain the conditions for a “no possible value”
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.
November 26, 2018
Married pair order follows click order
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.
Graphical glitch with very large parameter names and values in the requirements UI
November 21, 2018
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.
Issue reverting a plan to an old version or creating a copy from an old version in some cases
The internal revision format was recently modified and this caused a regression in specific cases when reverting or copying old revisions.
November 15, 2018
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
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
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.
Plan export dialog on very narrow screens
November 7, 2018
Incorrect link for key concepts of the “Create an auto-script” achievement
Last modified time in plans dialog not always updated for all changes
Broken link in auto-scripts help panel
November 6, 2018
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.
More room for implied value pair list
Now uses the complete panel height available.
November 5, 2018
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.
Missing tooltip explaining what “any valid value” means in test case table
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.
Requirements UI properly inert for read-only test plans
Oh pairwise defects…. you are everywhere, aren’t you?
Remove requirements bulk delete confirmation when only one requirement is selected
Start cursor at end of existing text when editing requirements text fields, not at the beginning
Properly name “Expected Outcome” column in Excel export
Allow requirements description and expected outcome fields to scroll if long enough
Regression in exporting Excel file with requirements that don’t have expected outcomes
“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!