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.
There are a set of 4 "Basic" tasks to introduce new users to Hexawise. When you complete a task, it is marked complete. You can click on a task to see how to do it.
New users get a tour of the major features of Hexawise on their first login to the tool.
Immediately after creating new invalid pairs, the hover highlighting was not correct until the plan was refreshed. This is no longer the case.
Some improvements were made to the test generation algorithm to decrease the likelihood that lots of invalid pairs will result in tests with a "no possible value" for a given parameter value.
It is always possible to chain invalid pairs in such a way that a test won't be able to provide a valid value for a particular parameter, but the point of this improvement is to be more sure that it's truly not possible to provide a value, and that the algorithm hasn't missed a value that could be possible if other changeable values were changed.
There were a few issues in the edit a plan dialog, mostly with entering special characters in a plan name in webkit (Safari, Chrome) browsers (which is a rare 3-way bug: Edit a Plan name, Chrome browser, Enter special characters).
Also resolved were some issues with moving plans between projects using the edit plan dialog on all browsers.
When given read-only access to a project ("Copy and Comment") and accessing the first plan, you are now given a clearer explanation, and a choice to create a copy of the plan or access it in read-only format.