More 'no possible values' than was warranted

This only affected tests cases with more than one any possible value (marked by purple italics) where those same values were involved in value pair rules. The algorithm that ensured that selected values replacing any values did not violate value pair rules was a one-pass algorithm, so it was not able to adjust other any value replacements, if those values were the cause of there being 'no possible value' that could be used. The algorithm now takes multiple passes, each pass with variability in the order it attempts to replace values, to ensure if there is a set of any value replacements that can work, it will be found.

Thanks to many users for pointing this issue out over the last few months, but special thanks to Cortney for identifying and isolating a clean cut case that led us to a definitive fix.

Clearing prompt text when inserting a parameter into a blank step

Before this action did not clear the prompt text. Now it does.

Auto-Script User interactions

Many additional, subtle improvements to the Auto-Scripts UI around step re-ordering, handling of the scroll position when adding steps, and auto-advancing the next parameter to be inserted.

Auto-Script step gaps

There were some rare corner cases that would result in gaps in step number ordering or having a 'Step 0'. These have been resolved.

Compute higher-strength tests when you have requirements

The presence of requirements no longer limits you to computing just 2-way tests.

Show requirements as satisfied in the Create Tests screen

You'll now see an indication that a requirement is satisfied by a test case in the Create Tests screen, not just in exports.

Over-applied Expected Results

In some cases of any's, and nones and compound expected results, the expected result would be applied when it shouldn't be. This was not the expected result.

Reworked Auto-Scripts UI interaction

Considerable improvements and fixes in how defining auto-scripts works, particularly in the area of fast and efficient defaults and keyboard handling.

Issue with ranged values and expected results and requirements

A classic pair-wise defect only triggered by the interaction of ranged values (a rarely used feature) and expected results or requirements that included that value (an advanced feature).

Excel import with blank rows in the Value Pair sheet

Extra blank rows in this sheet would cause an import failure. Thanks to Ed for finding and reporting this issue.

Bolding of parameter values that triggered a requirement to be satisfied

Sometimes additional parameter values were bolded.

Expected results of Requirements are now added every time the Requirement is satisfied

They used to be added only the first time the requirement was satisfied.

Computation issue when Requirements are Present

If a plan has enough requirements and a small enough number of values on a parameter to get an any value for that parameter in the requirement then the computed test data was failing to parse and causing the completed computation to appear to take forever.

This was a classic pair-wise failure, only triggered by relatively high number of requirements and an unusually low number of values in an early parameter.

Importing an "any" value expected result from Excel

This is now working properly.

This was a classic pair-wise failure where "any" value expected results work fine and importing expected results from Excel works fine, but the combination of the two resulted in a defect.

Spurious Expected Result deletion warning

Any modification to a parameter involved in an "any" expected result would give an expected result deletion warning. These warnings were not accurate as nothing short of removing the parameter will invalidate an "any" expected result.

Import Expected Results

Expected results from the expected results sheet in the Hexawise Excel file are now imported when importing a plan from Excel. Export a plan with expected results to see the format of the expected result sheet.

Import Requirements

Requirements from the requirements sheet in the Hexawise Excel file are now imported when importing a plan from Excel. Export a plan with requirements to Excel to see the format of the expected result sheet.

Excel expert with reserved XML characters

Some additional cases of reserved XML characters causing Excel format problems. Thanks to Justin G. for pointing out the issue.

'Any value' parameter value replacement in HP QC export fields

'Any value' paramater values used in test case title and description in HP QC exports now show their selected value rather than 'Any value'. Thanks to Justin G. for pointing out the issue.

Parameter value bolding of values in ranges

Parameter values that contribute to a requirement or expected result being met are bolded by Hexawise. When the value was in a defined numeric range, the value bolding was omitted. Now it's not.

Defined fields in HP QC export don't repeat for each test step

Thanks to Justin G. for the suggestion.

Expected Result column tooltips in Create Tests tab

Tooltips tell you where each Expected Result came from.

HP QC export when expected results contain certain reserved XML characters

Works now. Thanks to Justin G. for pointing out the issue.

HPQC Export test case numbering

Test case numbering starts with a leading 0 to match HP QC's expectations. Thanks to Justin G. for the suggestion.

Limits on navigation without a defined plan

Can no longer go to advanced tabs (Expected Results, Requirements and Auto-Scripts) without at least 2 parameters defined to avoid confusion.