The URL scheme for Define Inputs is now independent, so won't continually return to the single parameter define inputs toggle. If you are using bulk edit or mind map views, those will persist as you move around the application. These views are now also URL addressable.
The text on the define inputs and bulk edit UI has been improved, and the interactions provide more feedback.
This was a fairly nasty pairwise defect that prevented some types of plan modification from succeeding (e.g. parameter deletion) in the rare case that a user overrode a suggestion from Hexawise to prevent "no possible values" when modifying their plans constraints, and thereby entered into the state with the "no possible value" warning banner displayed in the UI.
This is now resolved.
Some users had issues with the reset password form after the Hexawise website refresh.
You can now export BDD test scripts from Hexawise Automate to anyone of 24 programming language / test framework pairs by selected "Automated Test Framework" in the export dialog. This is a more direct path to automated test scripts than just exporting the Gherkin Feature file from Hexawise Automate. These exports contain the "stubs" needed to implement the Gherkin statements in the programming language and test framework you select.
Please contact us if the programming language or testing framework you're using to execute your BDD test scripts is not already in the export list.
This was a pairwise defect only impacting "wide plans" (lots of parameters) on narrow width screens
There is now a "save as" drop-down to save the test cases data from the test cases table in common formats for automated tests.
The raw coverage data that powers the coverage graph and coverage matrix is now available via "Save As" from the coverage matrix so you can do your own analysis and visualization if you so chose.
Important functionality such as save and export would not be available on very narrow screens rather than being scrollable.
An expanded parameter value used to be shown as, "value - value expansion", but the value expansion is likely the most relevant value to the test case, so the test cases UI now shows them as, "value expansion - value".
The unique part of similar parameter values tends to be at the beginning or end of the value, so the truncation of long parameter values was moved to the middle of the value in the test cases table.