Error reporting an invalid export

Some attempts to export a test plan that were not going to work failed to report a friendly user message, but instead resulted in an application error.

Error exporting test plan after updating value expansions

Updating value expansions results in a partial cache invalidation. Immediately exporting afterward results in attempt to export off an incomplete cache. This was resolved.

New user guided video tour

New Hexawise users now get a guided tour of the product.

Scrolling when there are numerous constraints

There are three areas of the screen, the test plan inputs, the list of constraints, and the list of implied constraints. There was some scroll interaction between the three that made it more difficult and tedious to work with heavily constrained plans. These three areas now have better scroll behavior.

Hexawise Automate: Pairwise defect in selecting scenario examples

Hexawise Automate scenario examples that are constrained by parameter value would be missing test cases where the same parameter value is value expanded or range expanded in the generated test case.

UI/UX on login, register and reset password

The styling and validation behavior on these has been cleaned up and improved to provide more consistent behavior and feedback.

"Hide this" link in the mixed-strength warning panel

When attempting to apply new mixed-strength settings that are invalid, an explanation warning panel appears. The "hide this" link on the panel did not work properly.

"Please compute first" link in the Coverage Matrix

This link now takes you to the right place.

Hexawise Automate: The language and framework pair listing in Automated Test Framework export

The list of language and framework pairs was inconsistent and jumbled. Sometimes with the language first, sometimes with the framework first, and sometimes with only the framework and the language implied. This has now been made completely consistent for easier scanning of the list.

Switching test plan strength in Hexawise Automate

The test plan strength switcher in Hexawise Automate was subject to some caching issues and other defect cases. These have been resolved.

Cancel bulik edit changes after a warning

When you make a change in Bulk Edit, and click "Save", then get a warning message, upon clicking "Cancel" subsequently the "cancel unsaved changes" link couldn't be clicked.

Commas are now used in number formatting in the coverage matrix chart

Hexawise Automate: Auto-complete of parameter value names

After typing { in a Hexawise Automate Scenario or Scenario Outline, the subsequent auto-completion of parameter value names is much more capable and less persnickety when finding matches.

Hexawise Automate: Differentiate used and unused parameters

The drop down list of parameter names that appears in Hexawise Automate when you type < in a Scenario or Scenario Outline now differentiates parameters that you've already referenced in Hexawise Automate from those that you have not yet refereneced.

Comma seperated parameter value entry 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.

Placeholder text to explain the data entry format in the single parameter edit dialog

Error opening export file in Excel when the Excel export contains blank requirement names

A combinatorial defect with value expansions, OPML export and duplicate parameter values

Value expansions in mind map (OPML) exports

They are no longer prefixed with the parameter name, which made little sense in this particular format.

These here recent updates...

They got a splash of new paint. Fancy, huh?

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: 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: 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.