When you have more than 1 scenario outline, and you collapse one and work on the other, and then you add a var < to the other so that it renders the example table, it un-collapsed the one that you weren't working on. No longer does.
This could be disorienting. It no longer does this.
Like the McRib sandwich, it's back!
Unlike the McRib, downloadable mind map images are greatly improved from before with support for plans that are larger than 25 parameters, and the option to download a bitmap (PNG) or vector-based (SVG) file.
In addition to the Gherkin Examples data-table driven Scenario Outline sections, Hexawise Automate will now generate a Scenario outline for every test case in the exported feature file whenever any step in the Scenario references the test cases with either the parameter syntax:
<Parameter name>
or the parameter value syntax:
{[Parameter name]Parameter value}
The syntax is:
<Expected Outcome>
Anywhere in your test script steps.
Fixed by no longer being resizable.
Certain special characters such as < and & would result in corrupted Excel export files in some cases.
Pairwise regression when plan is copied and selection is to not choose or create a project for the copy, the copy didn't complete.
This pairwise defect only occurred when editing the parameter value's name directly by clicking on it on the Constraints screen. Editing the parameter values or bulk editing all the parameters didn't trigger the issue.
Bolding of the current plan's name in the Your Test Plans dialog was missing, and the redirect out of the plan when deleting the currently active plan was also broken.
For a situation in your auto-scripts like the following:
Step 2: Select Audit Schedule Type as {Audit Schedule Type}
Expected result: When Audit Schedule Type is Premium Reports Then Additional fields are not hidden and user should fill them as follows: Payment Plan Code should be {Payment Plan Code} select “{Schedule Basis}” from the Schedule Basis dropdown
Without the ability to include a parameter replacement such as {Schedule Basis} and {Payment Plan Code} in the expected result, creating the desired auto-script was not as easy and straight forward as it should be.
An 8th test to make sure browser settings are ready for effective use of Hexawise.
Error in specific cases when opening the "Your Plans" dialog without a plan already open.
Most of our user support has moved to Test Design Expert chat so we discontinued the support forums due to lack of use.
New minimum browser versions are:
In addition to the improved visuals, Hexawise's export capabilities received all new plumbing under the covers to better support customer specific custom export options, and to set the stage for additional export formats that are being worked on.