Use most recently generated strength when navigating to test cases

The most recently generated strength wasn't shown first by default if 2-way strength test cases also existed. 2-way test cases were shown instead until another strength was selected.

Test plan strength drop down in Auto-scripts

The test plan strength picker in the Auto-scripts preview panel did not reflect the selected new strength after you used it.

Auto-script expected result application

Fixed some 2-way, 3-way and even 4-way defects found in production with determining if expected results from auto-script steps apply to a test case or not. These defects involved parameter values that have been value expanded (2-way), value expanded and condition with "is not" (3-way), and value expanded and condition with "is not" and the other values that it "is not" are also value expanded (4-way)

"Hexawise 3.0", Part 1

Today marks a big new release of some functionality that has been in beta testing for quite a few months. We started calling this set of functionality "Hexawise 3.0" internally. Specifically,

There's too much to list everything, but some important highlights are:

• Significantly improved performance while navigating around in a test plan. Only opening a different test plan loads a full page now.
• Full page for viewing and editing test plan inputs, one at a time and in bulk edit
• Full page for viewing and entering parameter value constraints.
• Counters to quickly see which parameter values are the most constrained
• Ability to insert parameter values in a specific spot in the parameter order, rather than only as the last parameter and moving them later
• Ability to import requirements into an existing test plan
• Bulk delete of requirements
• Requirement expected results apply to any test case that matches the requirement, not just to the test case that was forced by the requirement
• Requirements traceability sheet in HP ALM export
• Value expansions are now per specific parameter value, not per "string match" across the whole plan.
• Localization of the majority of the Hexawise application into Japanese. こんにちは
• Localization of the majority of the Hexawise application into Esperanto. Nedankinde.

We are calling this "Part 1" as there are other substantial improvements under the "Hexawise 3.0" umbrella that have not yet been rolled out.

We hope you enjoy the vastly improved Hexawise experience and are very appreciative of the customers that have been beta testing this with us for the past few months.

Drop us a note or a chat message to let us know what you think!

Special characters in parameter name replacement in HP QC / ALM export

Parameter name→value replacement in test case name and test case description fields of the HP QC / ALM export was not working properly if the parameter name contained certain special characters (a classic pairwise defect).

Thanks to Kavya for reporting the issue.

Issues with reviewing passed quizzes on Chrome

A 2-way error, browser specific.

Issue where export dialog allowed an export request exporting without a file format selected

Numeric range values that are replacements for conflicting any values choices were not expanding

A relatively rare 3-way defect in production. To trigger the issue you needed a test case with any "any value" that was then replaced with a value that happened to cause a value pair constraint violation so was then replaced with a value that happened to be a range. In this case, the range stayed as is and was not changed to a value within the numeric range.

Another issue with quiz images

Unable to move between questions when reviewing a prior quiz that you passed.

Chrome specific, so a 2-way defect.

Thawing test cases preserver prior requirements

If you have some requirements, then freeze your test cases, and later need to thaw the test cases, your required test cases are preserved. Your prior required test cases will then contain a value for all parameters, but they will no longer be removed completely when you thaw.

Disabled export styling and text

Improve disabled disabled state and disabled message when HP ALM and Gherkin export are disabled.

Hexawise help contains links to new user guides

Getting started, intermediate and advanced user guides are available in the Hexawise help.

Gherkin data table exports

You can export your Hexawise generated test cases in the data-driven Gherkin examples format for use in scenario outlines in your Gherkin, BDD automated tests.

Error when completing quizzes

This was a recent regression.

Autoscript parameter name auto-completion is now case insensitive

Duplicate requirement warning repeated when changing requirement name or expected result

It's true the requirement is still duplicated, but the second warning is difficult to understand since all you doing is changing the name or expected result.

Missing hint images in quizzes

Overly constrained message in Excel export plan scorecard

This message didn't match the web plan scorecard and the web plan scorecard was correct.

Thanks to new intern Scott for this, his first bug fix of the summer!

Special characters in truncated notes and value expansion tooltips

A classic pairwise defect, only happened when there was both special characters in the tooltip and a tooltip long enough note for truncation. Either case on its own worked with no problem.

Missing message w/ invalid mixed-strength tests

If a mixed-strength test case generation was requested with the re-apply button and an insufficient number of parameters were selected for the highest selected strength (3 for 3-way or 4 for 4-way, etc.) then the error message was missing and instead there was a blank panel.

This was a regression that started when we added the enhanced, searchable and sortable test case table.

Thanks to Ryan for reporting this bug via chat.

Special character in requirement name during Excel export

This was a 3-way defect: you had to have auto-scripts in your test plan, have a less than < character in your requirement name, and be exporting to Excel.

Thanks to Pam for reporting the issue!

Truncated long parameter names were not replaced in Auto-Scripts

Instructions for achieving the "View the sample plans" achievement

Tooltips explaining "purple italics" in test case table on Auto-Scripts

The tooltips that explain "purple italics" are now also in the test case table on the Auto-Scripts page.