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.
The confirmation page is now more clear about the next step to take to confirm your email address. Also you no longer have to login after confirming your email.
This was a triple mode fault where a higher latency connection, browser of IE 7 or IE 8 and creating tests would intermittently cause a partial page render.
Thank you to Sreenuraj for this request.
Added two new items to the Basic How-To Progress Checklist:
There is a new, Advanced, How-To Progress Checklist with explanations of how-to do these six things with Hexawise:
The project sharing dialog is now more user friendly. If you add a users email, but forget to click the add user button before leaving the dialog, it now asks if you want to add the user.
In some rare cases, generated tests could display an empty parameter value rather than an expanded value when using biased value expansions with a small number of values and a higher test strength. In the unlikely event that you have this case in one of your plans, you may need to force test regeneration by making some innocuous change in your test definition.
Thanks to Tanmay for bringing this issue to our attention.
Due to popular demand, we are now using a slightly modified version of the HP Quality Center export as the AutoScripts worksheet of the Excel export. Thanks to the users that requested this change. We like it too.
These instructions (permissible file formats) are in the Table of Contents worksheet of the export.
After some recent changes to handle illegal XML characters, the bolding was coming through as HTML. This is now resolved. Special thanks to Bryan for alerting us to this error.
Now resolved.
After some recent changes to handle illegal XML characters, a small number of customer plans would not export. This is now resolved.
Some graphical glitches (mis-sized fields, overlapping panels, etc.) were introduced in an upgrade last week. These issues are now resolved.
A few illegal XML characters were not being properly escaped for the spreadsheet importing and exporting. This is now resolved.
The strength of the tests you will export are now in strength order (rather than the order of when you created them) in the export dialog.
Should result in some modest performance improvements of the server-side processing.
Now resolved.
Should result in some modest performance improvements of the server-side processing.