Hexawise Recent Updates Feed 5bb406880f456fd0fe4858a482696abeaede4262fdc29053346c5fdc92d5d216

May 14, 2016


Saving Auto-script expected results with no conditions

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.


May 10, 2016


Label plan revisions

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.


May 8, 2016


Search prior plan revisions

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.



Copy plan from a revision

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.



Various minor defects with Auto-scripts UI

Fixed some issues with saving Auto-script Expected Results and unsaved changes messages in the Auto-scripts UI.



Issue when selecting an un-cached plan strength from the analysis tab



Scrolling auto-generated value pairs dialog

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.



Issue importing plans with very names



Clearer about plans too large to compute

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 header in the plan revisions dialog

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.


April 20, 2016


Sample plan pop-up information

Improved the content and presentation of information you get when opening a sample plan. Changed the default action to create a copy.



Auto-Script Expected Result editing

Fixed a few UI issues with creating Auto-Script expected results.


March 30, 2016


Parameter count in revisions

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.



In app Mind Mapping!

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!


March 22, 2016


Plan copy dialog UI

Copy revisions checkbox more clearly associated with the label.



Changing plan strength to an uncomputed strength in the Analysis view

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.



Error’d plan import has blank page behind explanatory dialog

This is no longer the case.


March 15, 2016



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.



Export performance

The performance for exports with lots of test cases has been dramatically improved.


March 7, 2016


Browser and network test

The Hexawise Browser and Network Test (available at /network-test) has proven very useful in supporting users dealing with browser or network configuration issues so we improved the styling and usability considerably and linked to it from the login screen (where browser and network issues are usually first surfaced).



Eliminate “no possible value” warnings without details

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.



Auto-Script behavior when moving steps and adding expected results

Fixed some edge cases around moving the last step down or first step up. Also fixed the scrolling and focus behavior after clicking to add an expected result to a step.


February 5, 2016


Overly aggressive “no possible value” prevention logic

There is extensive logic in Hexawise to prevent many of the simpler cases of overly constrained test plans that would otherwise result in tests with a “no possible value” for a parameter value. This logic in some cases generates implied constraints that are needed, and in other cases disallows the creation of the paired value constraint that would cause the “no possible value”.

There was a defect in this logic that could cause the order the constraints were created in to matter, and that could cause the type of constraint to matter (so a married pair and its logically equivalent set of invalid pairs weren’t treated the same).

These issues have been addressed.



Parameter re-use drop down

There is an auto-completion feature to the parameter name drop down combo box that lets you type the name of a parameter used in another plan, select it, and reuse the parameters and values in your new plan. Unfortunately this only worked if you started typing the parameter name from the beginning. Now you it will match anywhere in the parameter name, e.g. typing “master” will match both “Master Record”, “Record Master”, and “Platinum mastercard”.



Mixed-strength 1-way/2-way tests for large plans

Mixed-strength was not an option for very large test plans that only support generating 2-way tests. Unfortunately this also meant the option to select 1-way strength for some parameters was missing. This has been addressed, so now you can select mixed-strength and 1-way parameters for very large test plans.