Issues resetting password
Some users had issues with the reset password form after the Hexawise website refresh.
Consistent save keyboard shortcut between Hexawise (bulk edit) and Hexawise Automate
Hexawise Automate test script export to programming language / test framework pairs
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.
New “Save as” feature in test cases hidden for some plans displayed on narrow screens
This was a pairwise defect only impacting “wide plans” (lots of parameters) on narrow width screens
Hexawise Sample plans now include Hexawise Automate BDD test scripts
Broken links in sample plan dialogs
Create an auto-script achievement is now satisfied by a manual auto-script or a Hexawise Automate BDD script
Hexawise Automate header panel on very narrow screens
Important functionality such as save and export would not be available on very narrow screens rather than being scrollable.
Quickly and easily save test cases as JSON, CSV, XML, and Gherkin or Gauge data tables
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.
Save the raw coverage data as JSON or XML for your own analysis or visualization
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.
UI scrolling glitch with No Possible Values banner
Plan name validation during plan rename
Test cases use middle truncation
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.
Revisions dialog indicates which revisions contained “no possible values”
Changed the order of value expansion / value when displaying test cases in the UI
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”.
No tooltip for truncated values in test cases UI
Expected Outcome column missing from Gherkin Data Table export
Excel warning exporting plan with Auto-script steps, but not value for the “Start” step
A classic defect of the pairwise genre.
Auto-scripts UI doesn’t properly preview parameter values containing quote special characters
Errors editing parameters of an imported test plan that contains pure integer parameter values
This was an interesting 3-way defect involving a prior action (importing a test plan), specific data variation (pure integer parameter values), and a later action (editing one of the parameters that contained pure integers and saving the edit). By themselves, none of these 3 actions caused any issues. All 3 together combined to create a defect.
Automate Gherkin parsing breaks when entering a new line from the very beginning of the prior line
This is an unusual (though reasonable) user behavior. Just the kind of thing to include as variation in your test plans.
Certain plan edits would not clear the cached generated test cases
This was a regression.
Can’t scroll parameter name auto-complete suggestions in auto-scripts UI
More descriptive and accurate error text when editing parameter names
Define new parameters and parameter values during requirements import
Now when you are importing requirements, the import can contain new parameters and new parameter values that are not currently defined in your test plan. If new parameters or parameter values exist in your requirements import, they will be added to your test plan for you.