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.
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 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.
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".
A classic defect of the pairwise genre.
This is an unusual (though reasonable) user behavior. Just the kind of thing to include as variation in your test plans.
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.
This was a regression.
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.
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.
Hexawise now provides an option to create a sample of some parameters and parameter values in an empty test plan.
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.
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.
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.