Fixed a very rare case where an exported plan could have duplicated columns. This was a pairwise defect related to the current state of the data in the database and the system configuration.
The wording and formatting was improved to be more clear.
Using the up arrow on the topmost parameter or the down arrow on the bottommost parameter didn't "wrap" the parameter as you would intuit. Now it does.
The "Bulk Add" feature was functionally redundant with the "Bulk Edit" feature and so has been removed to reduce code and UI complexity.
This is a 2 or 3-way defect (depending on how you model the problem) when using bulk edit to make a parameter newly over 8 values, then canceling after receiving the parameter length warning.
Resolved.
Thanks to Vishal for pointing out the inconsistency.
If you have 4 or fewer parameters there is now a warning in the Plan Scorecard.
In very rare cases the generated tests table could have a row with misaligned columns due to this bug in IE 9. A work around is now in place.
Thanks to Khurram for reporting the issue.
A blank parameter value in comma separated parameter values during a bulk edit would error out the edit with a vague error message.
Blank values are now ignored in bulk edits.
Thanks to Zach who pointed out how vague the error message was.
This has been resolved.
This change emphasizes that you still need to chose a value that satisfies the plan's constraints.
Fixed styling when a plan is shared in a project, has no requirements, and you have "Copy and Comment" access to the project (Note the combinatorial cause).
This is the first work done by our new development intern Scott. Congratulations!
Comprehensive error messages are shown when a plan fails to import due to internal consistency issues when creating a new plan but were not shown when re-importing a plan (classic 2-way defect). Now they are shown in both cases.
This should avoid many hard to spot value mismatches.
Auto-script expected results were triggered by a numeric range value even when out of the range.
When importing a plan that has an invalid format or invalid data, Hexawise will now provide additional info on the name of the Excel tab that has the invalid data.
Thanks to Vikas for pointing out the omission.
Selecting a drop down value with the mouse rather than the keyboard was broken in some cases in the IE 9 browser. A relatively rare 3-way defect found in production for those keeping track.
Thanks to Vikas for finding and reporting the issue!
A rare case during plan import caused invalid pair validation to fail and abort the import. This has been fixed.
This "order of operations" defect is now fixed.
We're using a new system for live test design support for customers that pay for live support. The new system has a "memory" of your discussions so you can refer back to them and more seamlessly blends live and asynchronous discussions. We're excited about the improvements!
On some screen sizes and resolutions. Also addressed overly wide dialog.