Value name truncation in MS Edge browser

A pairwise defect with the MS Edge browser caused long value names not to be truncated in the Define Inputs UI.

Parameter names and parameter value names with angle brackets in explanatory dialog

Parameter names and parameter value names written like <this> or <that> were rendered incorrectly in the explanatory modal for "2-way interactions means...".

Drawing glitch in coverage matrix chart

With larger test plans some columns in the matrix chart would lose their column divider.

Hexawise Automate: De-duplicate example data table and generated scenarios

If a Scenario or Scenario Outline includes a (small) subset of the plan's parameters, then it often results in some completely duplicate example data table rows or generated scenarios since the subset of the test case scenario included likely won't be unique (even though each generated test case is unique).

Hexawise Automate now eliminates these duplicates. You can see this most clearly by including <Test Number> and <Test Case> in your Scenario or Scenario Outline. The former will always be sequential, while the latter will skip both generated test cases that don't apply (that don't include selected parameter values) as well as test cases that would be duplicates based on the included parameters.

Large improvement in coverage matrix slider and animation performance

Entering password into Hexawise login session timeout dialog to reestablish session

This wasn't working and brought you to the full login page. It's now working.

Constraint dialog order reverses after error

If you attempted to create an married pair constraint that violates existing constraints, an error dialog explaining the issue is shown. Upon returning from the dialog back to the married pair constraint creation dialog, the order of the parameters could reverse from the order in which you clicked them. This has been resolved.

Network test UI

Small user experience improvements in the network test.

Project name truncation in manage plans dialog

Long project names were not properly truncated.

Hexawise Automate: New test automation export of language of TypeScript, and test framework of Cucumber using Cucumber Expressions

This was a specific customer request. Always eager to hear what language / test framework pairings will be helpful to add to Hexawise Automate.

Stuck progress spinner after large parameter warning in mind map view

When adding or editing parameters in the mind map view, the warning dialog for large parameters wouldn't dismiss after you OK'd the large parameter.

Hexawise Automate: Error exporting feature file with commented out Gherkin statements that include parameters or paramater values

Clicking cancel during parameter length warning adding or editing parameters

Clicking cancel during parameter length warning when adding or editing parameters would result in a full dismissal of the prior dialog and a lose of the addition or edits. It now returns to the dialog upon clicking cancel.

Issue with forced return to large test case generation request

After requesting a long-running test case generation (5-way or 6-way) and then instead selecting a lesser strength, refreshing or navigating would return to the larger strength request.

Thanks to Zachary for reporting the issue.

Hexawise Automate: <Test Case> Gherkin expression for Scenario and Scenario Outline sections

Hexawise Automate has had the <Test Number> expression that can be used in Scenario and Scenario Outline sections to include a sequential number for each included test case, either in the Examples table in the Scenario Outline or in the sequence of generated Scenario, one for each test case.

In addition, there is now a <Test Case> expression that provides the (potentially non-sequential) number of the generated test case for the row of the Examples table or the generated Scenario.

If your Scenario or Scenario Outline doesn't have any {[Parameter] Parameter value} selector(s) then there will be no difference in the values provided by <Test Number> and <Test Case>, but if it does, then the <Test Number> will increment from 1 sequentially, while the <Test Case> will reflect the number of hde generated test case for the Examples table row or generated Scenario.

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.

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.

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.

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.

"Please compute first" link in the Coverage Matrix

This link now takes you to the right place.

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.

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.

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