Hexawise recent updates

Hexawise recent updates

February 27, 2019
NEW
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.

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

February 11, 2019
FIXED
UI scrolling glitch with No Possible Values banner
February 7, 2019
FIXED
Plan name validation during plan rename
February 1, 2019
NEW
Revisions dialog indicates which revisions contained "no possible values"
IMPROVED
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.

FIXED
No tooltip for truncated values in test cases UI
IMPROVED
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".

January 31, 2019
FIXED
Expected Outcome column missing from Gherkin Data Table export
January 25, 2019
FIXED
Auto-scripts UI doesn't properly preview parameter values containing quote special characters
FIXED
Excel warning exporting plan with Auto-script steps, but not value for the "Start" step

A classic defect of the pairwise genre.

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

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

January 2, 2019
FIXED
Certain plan edits would not clear the cached generated test cases

This was a regression.

December 27, 2018
IMPROVED
More descriptive and accurate error text when editing parameter names
FIXED
Can't scroll parameter name auto-complete suggestions in auto-scripts UI
December 26, 2018
NEW
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.

December 20, 2018
IMPROVED
Hexawise Automate: Expected Outcome from requirement in Scenario

Adding in your Automate Scenario Outline will include any expected outcome from requirements. This only worked for Scenario Outlines, and did not work for Scenarios. It now does.

IMPROVED
Better information is provided when exceeding 200 parameters in a test plan
December 18, 2018
IMPROVED
Exporting out-of-date Automate script

Unless you visit the Automate script view, you may not have an up-to-date script that matches your most recent test plan changes available to export. Hexawise used to allow you to export the out-of-date Automate script, but this is rarely what you want to do. Instead now Hexawise prevents an out-of-date script from being exported.

NEW
Sample parameters for an empty test plan

Hexawise now provides an option to create a sample of some parameters and parameter values in an empty test plan.

December 12, 2018
IMPROVED
"Stickier" Automate

If your test plan only has Automate test scripts, and no manual testing auto-scripts, then Automate will be active by default when you navigate to the Auto-scripts tab.

NEW
Define new parameters and parameter values during requirements definition

This is an exciting productivity enhancer! When defining required scenarios, you'll often find that the scenario contains a testing idea, either a parameter or a parameter value, that your test plan does not yet account for. Before, this would mean breaking your flow of inputting required scenarios and opening the inputs tab to define a new parameter or parameter value. Now you can make these additions directly in the requirements UI.

December 8, 2018
FIXED
Defect when adding a large number of parameters via bulk edit
December 6, 2018
IMPROVED
"Smarter", more flexible requirements importing

The requirements import used to assume the first 3 columns in the import file were the designated name, description and expected outcome columns. It now looks at the column headers.