The number of the generated test case is now included in a comment above the generated Scenario for the test case when exporting Gherkin feature files.
They are no longer prefixed with the parameter name, which made little sense in this particular format.
They got a splash of new paint. Fancy, huh?
There was a pairwise defect when navigating from the coverage graph to a Hexawise Automate script containing a scenario outline with a data table after editing test plan inputs. In this sequence of events the generated examples data table would be empty.
The background section is not data-driven so shouldn't make it appear like angle brackets will pull in data values.
When changing an existing scenario outline with a generated example data table into a scenario, the generated data table would not be removed and a Gherkin syntax error warning would be shown.
Adding a parameter above an existing parameter worked fine, unless the parameter being added had 8 or more parameter values, triggering the warning dialog. In that case, the parameter would be added at the bottom of the parameter list if the warning was bypassed.
Fixed a race condition on plan export that would very rarely cause the plan export to fail with an error.
These two dialogs now display the strength at which the test cases were generated.
In the unlikely case that your user ID (a sequential database ID) and the test plan ID (a sequential database ID) happened to match, use of the plan became broken.
This is what we mean when we say all defects are pairwise defects.
There were some inefficient queries during this process that were heavily optimized.
Having no test cases at all messed up the sort in the test plan management dialog. It no longer does.
A classic pairwise issue; it's now resolved.
The options were visibly disabled, but were still able to be clicked. We kept them clickable, but added a helpful message now as to why they are disabled.
When the creation of a constraint is denied, since it will cause a "no possible value" to appear, it now returns you to the constraint creation dialog so you can modify the constraint type, rather than returning you all the way back to the inputs screen.
The import button was visibly disabled, but was still able to be clicked. Now it is not.
In other parts of the Hexawise, adding a parameter with no parameter values results in a parameter with one value called
none. The same now happens for entering parameters in the mind map UI.
When exporting a Gherkin Feature file from Hexawise Automate, or when saving generated test cases as a Gherkin or Gague data table, for parameter values with value expansions, we no longer include both the parameter value and the expanded value for the value of a parameter with a delimiter in a specific test case, we only include the expanded value.
Thanks to Tim for the suggested improvement.
The new name is more clear about the purpose of this field, which is used internally by Hexawise to flag that a parameter value has been included more than once (for weighting purposes).
Not every plan revision has test cases generated for it, but for those revisions that do, Hexawise will now display how many test cases existed for that revision in the test plan revisions dialog.