Thank you to Charity for reporting the issue via chat!
It was difficult to read all the information about file formats for importing on smaller height screens. This dialog now scrolls.
This wasn't working. Now it is. Simple as that.
Detailed explanation of the cause of the failure when importing Excel test plans were not being shown. Now they are again.
There was a remaining Auto-script saving issue that was a 2-way defect only triggered when the conditions of the expected result were blank (always expected).
A big thank you to Lakshmi for an excellent bug report on this issue.
You can now provide labels to specific meaningful revisions of your plan. Simply open the plan revisions dialog and click on the numeric revision label and replace it with a meaningful label such as "Beta 3", "Reviewed", "Approved by Doug", "1.0.13.april", or "Sell by June 3".
Whatever makes that revision special, you can label it as such.
The dialog informing you of auto-generated value pairs did not constrain the height, so if a very large number of value pairs were generated, the dialog would be too tall for the screen. The height is now limited and the dialog is scrollable.
The header describing the columns of the data in the plan revisions dialog is now fixed as your scroll through all the revisions of your plan.
Each revision to your plan includes a verbose description of what changed with the revision. These descriptions are now searchable in the plan revision dialog.
Need to know when "Gold Medallion Level" got removed from your test plan? Now you can search and find out!
Need to know who added "N/A" as a value to the "User" parameter and when they did? It's just a quick search away.
In addition to being able to revert to a prior version of your test plan in the Revisions dialog, you can now create a new plan as a copy of a prior revision. These options, the new create a copy from a prior revision, or the existing revert to the prior revision are available as separate action icons on each revision row in the revision dialog.
Fixed some issues with saving Auto-script Expected Results and unsaved changes messages in the Auto-scripts UI.
Plans that will generate a minimum of tens of thousands of tests and therefore won't be computed now include the message on both top and bottom panels of the UI, rather than the message on the top and a misleading progress indicator in the bottom panel.
Fixed a few UI issues with creating Auto-Script expected results.
Improved the content and presentation of information you get when opening a sample plan. Changed the default action to create a copy.
The parameter count shown in plan revisions prior to today (March 30th) will be "trailing" for plan updates that change the number of parameters in the plan (parameter additions, deletions, some bulk edits). Trailing means the revision shows the parameter count before, rather than after the update.
This issue is now resolved, and the parameter count display will no longer be trailing for newly created revisions. This issue was only with the display of the revision, not a problem with the revision itself, or with reverting back to the revision.
Mind maps are a great way to visualize the variation in your test plan. They're perfect for reviewing your plan with subject matter experts or developers that aren't very familiar with Hexawise, and they're also useful for management reports, presentations, and brainstorming sessions. Consider using a mind map anywhere you need to talk about and collaborate on your test plan.
Many of you have already been using desktop mind mapping tools and Hexawise's OPML import/export to edit and visualize your test plans as mind maps, but now it's no longer limited to people with extra tools.
Hexawise now supports interactive mind maps right in your web browser. Just click the "Mind Map" link in the center panel of the "Define Inputs" page of any plan to see your test plan as an interactive mind map. Click the black errors to make edits to your plan from within the mind map, and click the "Save" button when you are finished.
Have fun!
Copy revisions checkbox more clearly associated with the label.
Two separate issues, one with canceling a computation invoked from the analysis view, and another with changing strengths from the scorecard tab. Both are resolved.
This is no longer the case.
The performance for exports with lots of test cases has been dramatically improved.
We are proud to launch today the biggest, and most often requested single change in Hexawise since it was created, test plan versioning!
With Hexawise's new versioning, every change you (or your colleagues) make to a test plan is tracked and versioned. Click on the "Revisions" link at the top of any application page to see the revision history of the current test plan: what changed, when, and by whom. You can revert a test plan to any prior revision with a single click.
Due to the nature of how plan versioning works, versions are only available for new changes to your test plans going forward.
We're not yet done with this feature, and will soon be launching version labeling and branching (creating a copy from a prior version).
We'd love to hear your feedback on Hexawise versioning.
In most cases Hexawise provides some details about the cause when preventing the creation of a value pair that would cause a "no possible value" parameter value in a test case. However there were some cases where no details were provided, and these have been eliminated.