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.
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.
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!
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.
Go to /network-test on Hexawise (type it into the URL bar of your browser) to perform a quick network test to see if your corporate network is blocking any important types of network requests to Hexawise.
There is a new "Your Plans" dialog with important new capabilities:
Let us know if you have any trouble with the new dialog, and enjoy!
As Expected Result value could return to original setting during editing subsequent expected result values in some cases.
Special thanks to Mohanned for reporting the problem.
Removing a parameter that is used in a requirement with bulk edit could result in the parameter not being removed from the requirement in some cases (after continuing through the warning dialog).
Only the first parameter to newly exceed 8 parameter values would get mentioned in the warning. Now it mentions all parameters that newly exceed 8 parameter values during a bulk add or edit.
There were issues round tripping plans through export and import with special characters (such as < & > " etc.) used in Auto-Script Expected Results.
A very classic pair-wise defect of specific set of user actions paired with unusual data. Neither caused an issue without the other.