Excel doesn't like cells that start with 0 being marked as numeric. Fixed this in the Excel exports.
Thanks to David for finding and reporting this one, which was tricky to track down and replicate.
Numbers > 10^32 cause errors in Excel export because the cell was marked as a number rather than a string. Thanks again to Nitin the "Excel Error Extricator".
For those keeping track at home, depending on how you designed your tests, this could be one of those rarest of birds, a 4-way bug in the wild!
Activity is export, Format is Excel, Value is a number, Size is > 10^32
These errors are timing related, and sensitive to network latency, so it is not possible to say they are definitively resolved for all users in all cases. The problem should be much rarer now though, if it still occurs at all.
With sufficient plug-ins or extensions installed, the detection of older versions of IE could have a false positive.
Thank you to Nitin for reporting the error.
There were some circumstances where the value suggested for an any possible value (in purple italics) would violate a married pair. This has been fixed.
The feedback now stays in place rather than disappearing after a moment.
The suggestion on how to introduce an "N/A" value is now more clear.
There is now a new way to pair parameter values. In addition to marking a pair of values as invalid to ever be paired together, you can mark a pair of values as "married." They can be married in just one direction, where value A always has to be tested together with value B, or in both directions where in addition, value B always has to be tested with value A.
Gives more user feedback when applying your selections.
You can now use the left and right arrow keys to scroll through the content of these.
The drop down could wrap into 2 lines for some people.
Very few users have the vertical screen real estate to make this configuration useful, so we now auto-collapse the top or the bottom when you expand the other to save you the clicks.
In some circumstances, users could be shown the new user tour more than just at their first login.
Warning to brand new Hexawise users that are using IE7 now does not conflict with the new user tour.
When Hexawise does not need a value from a parameter to provide coverage for a specific pair (or triple, etc.) in a test, the test value specified for that parameter in the test is marked in purple italics and a sample possible value is provided for what could be any value. In the case that the sample value itself was subject to a value expansion, the sample value was not expanded. Now it is.
Pairwise error: new user, no @ in provided email address.
Many of them used to start with "Do not reply to this message..." This was silly cargo culting by us. We want you to reply whenever you have anything to say to us!
Part of ongoing work to make this powerful feature easier to understand. We're not done yet.
PC users of Excel see a warning dialog when opening Hexawise exports since these have a .xls file extension rather than a .xml extension. We do this to make sure Excel is used to open the file since a lot of technical users (you!) will have the .xml file extension configured to open in some other application. The text just explains that the warning from Excel is innocuous and what to do about it.
The progress checklist is no longer shown to users that are not trying to complete it. How do we detect disinterest? Apathetic mouse clicks of course.