Hexawise recent updates

Hexawise recent updates

February 18, 2020
IMPROVED
Network test UI

Small user experience improvements in the network test.

FIXED
Project name truncation in manage plans dialog

Long project names were not properly truncated.

January 31, 2020
NEW
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.

January 29, 2020
FIXED
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.

FIXED
Hexawise Automate: Error exporting feature file with commented out Gherkin statements that include parameters or paramater values
January 23, 2020
FIXED
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.

January 20, 2020
NEW
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.

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

January 7, 2020
FIXED
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.

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

December 28, 2019
NEW
New user guided video tour

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

December 20, 2019
FIXED
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.

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

December 18, 2019
FIXED
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.

FIXED
"Please compute first" link in the Coverage Matrix

This link now takes you to the right place.

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

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

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

December 10, 2019
IMPROVED
Commas are now used in number formatting in the coverage matrix chart
FIXED
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.

December 6, 2019
IMPROVED
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.

November 22, 2019
NEW
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.

November 18, 2019
REMOVED
Comma seperated parameter value entry in the single parameter edit dialog
NEW
Placeholder text to explain the data entry format in the single parameter edit dialog
NEW
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.