Considerable improvements and fixes in how defining auto-scripts works, particularly in the area of fast and efficient defaults and keyboard handling.
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).
Extra blank rows in this sheet would cause an import failure. Thanks to Ed for finding and reporting this issue.
Sometimes additional parameter values were bolded.
They used to be added only the first time the requirement was satisfied.
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.
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.
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.
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.
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.
Some additional cases of reserved XML characters causing Excel format problems. Thanks to Justin G. for pointing out the issue.
'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 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.
Thanks to Justin G. for the suggestion.
Tooltips tell you where each Expected Result came from.
Works now. Thanks to Justin G. for pointing out the issue.
Test case numbering starts with a leading 0 to match HP QC's expectations. Thanks to Justin G. for the suggestion.
Can no longer go to advanced tabs (Expected Results, Requirements and Auto-Scripts) without at least 2 parameters defined to avoid confusion.
No longer occurs.
Expected results with very long values are now truncated in the test previews to prevent very long load/parse times in the browser.
This used to return a 500.
We are using a new and better system for providing in app help content.
Sample Test Plans are now up to date for everyone as they change and evolve over time and new samples are added. This means if you want to modify a sample test plan you need to copy it first as they are now read-only.