The deletion worked fine but you received an error and needed to refresh. It now works properly.
This was a rare 3-way defect in production. It only happened if you were bulk editing parameters and removed parameter values that were used in requirements, and you removed more than 1 of them in a single edit.
The email and download buttons would not enable correctly if no other format type was selected and the mind map format (OPML or image) was selected directly rather than by picking the mind map checkbox first.
Given most ways you'd likely develop a test plan for this dialog, this counts as a rare 3-way defect found in production. Thanks to Scott for his eagle-eye in spotting this and generosity in reporting it.
There was an interaction between invalid pairs and requirements that effected some plans and could cause an invalidated pair to still appear in initial test cases that were satisfying created requirements.
This has been resolved. Thanks to Fabio for noticing and reporting the error.
Thanks to Scott for reporting this.
There were cases where the exported auto-script definition would not be able to be imported. These cases were cleaned up.
The example Excel input file is now much more comprehensive including sheets for everything that can be imported.
If the only thing you changed in your test plan was the parameter order, the prior generated tests were held onto and would be displayed with mismatched column headers. The computed test cache is now cleared when you reorder parameters.
Thanks to Scott for letting us know.
There were issues saving requirements where the required value contained a % sign.
Moving the top parameter "up" in the parameter order, or the bottom parameter "down" in the parameter order would cause the parameter to disappear until a page refresh. The parameter now "wraps" to the opposite side.
Thanks to Manas for reporting the bug.
In some circumstances the "Create your 3rd value expansion" achievement would not be awarded.
Thanks to "Hexawise Guru" Del for raising the issue to our attention.
There was a rare case where invalid pair creation should have been disallowed with an informative message and was instead failing with an error.
They were some cases where Hexawise would warn you about a change effecting a requirement when adding some parameter values. The warning was unfounded and was caused by different types of line terminators on the values.
Line termination (LF, CR, CR+LF, LF+CR, etc.) is an interesting thing to include in your test plans in some cases!
There was a sequence of events with expected results, requirements and auto-scripts that could result in exporting to Excel failing in some particular cases.
In the past blank Auto-Script steps were excluded from the auto-script, but now they are included if they include expected results that apply to that test case.
The "Your Achievements" screen is now streamlined and more clear about your next action to level up.
The preview would not function properly in some cases.
In the past blank auto-script steps were excluded from the auto-script, but now they are included if they include expected results that apply to that test case.
The wording in the sharing dialog for projects is now more clear about the option to share a copy of a project via a URL.
Some unescaped characters were causing the auto-script page to hang on some plans. This has been resolved.
Some users were getting an "Operation aborted" error from the IE7 browser immediately after loggin in.
Thanks to Darpan for reporting the issue.
Thanks again to master tester Pratibha for reporting this one.
Thanks to Pratibha for discovering and reporting the issue.
0 was used as the value for blank so this prevented you from selecting a parameter value that happened to actually be 0.
Thanks to Steve and Rasaiya for reporting the issue.
The main actions in the requirements interface, edit, delete, save and cancel now have tooltips to go with their icons to make the action more obvious.