Hexawise recent updates
Hexawise recent updates
Comma seperated parameter value entry in the single parameter edit dialog
Placeholder text to explain the data entry format in the single parameter edit dialog
Hexawise Automate: Test case number in exported Gherkin Scenarios in a Gherkin feature file export
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.
Error opening export file in Excel when the Excel export contains blank requirement names
Value expansions in mind map (OPML) exports
They are no longer prefixed with the parameter name, which made little sense in this particular format.
A combinatorial defect with value expansions, OPML export and duplicate parameter values
These here recent updates...
They got a splash of new paint. Fancy, huh?
Hexawise Automate: Issues changing a scenario outline into a scenario
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.
Hexawise Automate: Pairwise defect with scenario outline data table generation
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.
Hexawise Automate: Don't highlight an angle bracket in the Background section of a Gherkin feature file
The background section is not data-driven so shouldn't make it appear like angle brackets will pull in data values.
Pairwise defect with Parameter insertion
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.
The oddest of pairwise defects...
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.
More informative test case count in Your Plans and Revisions dialogs
These two dialogs now display the strength at which the test cases were generated.
Rare error during plan export
Fixed a race condition on plan export that would very rarely cause the plan export to fail with an error.
Pairwise defect exporting test plan when there are generated test cases and requirements with no names
This is what we mean when we say all defects are pairwise defects.
🚀 Performance when saving test cases as data formats (JSON, CSV, XML, etc.)
There were some inefficient queries during this process that were heavily optimized.
Test plan sorting by test case count when some plans have no generated test cases
Having no test cases at all messed up the sort in the test plan management dialog. It no longer does.
Saving test cases as JSON when they contain an "no possible value" causes a 404 response
A classic pairwise issue; it's now resolved.
Clicking disabled options in plan export dialog causes errors
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.
Faster constraint creation
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.
Clicking disabled import button in requirements import dialog causes errors
The import button was visibly disabled, but was still able to be clicked. Now it is not.
Adding a new parameter in the mind map UI resulted in only grey mind map lines for the new parameter
Adding a new parameter in the mind map UI with no parameter values error'd
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.
Gherkin Feature file, Gherkin data table, and Guage data table exports are streamlined
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.