As part of our efforts to address user accessibility issues, we are targeting areas of the UI that rely on color exclusively to convey information and adding non-color redundancies.
We made some very significant performance improvements across the entire application. You'll mainly notice these improvements when opening various dialogs, especially in user accounts that have a significant amount of test plans and projects.
There was different behavior when the value pair conflict confirmation dialog was closed with the "cancel" link vs. the X. These are meant to be the same.
The achievements needed to level up that are based on the number of activities performed (e.g. "Create your 10th value pair") now indicate your current count.
They are now consistently truncated.
In the plan dialog a click directly on the project acts to select the project, not the entire plan row. This is now made more clear with link underlining on hover over the project name that's distinct from the entire row hover highlighting.
These are not links in this part of the UI.
The parameter should be removed from the list of possible options when its possibilities are exhausted, but it wasn't in the case of "is not". A classic pairwise defect.
Now cancel and the close X both work the same.
Very long data is often an important testing consideration when dealing with user provided content.
The formatting and styling of the dismissable help panels throughout the application have been improved and normalized across the app.
Most users use the mind map to visualize their test plan inputs. It's also fully editable however, and there were a few regressions that had been introduced that effected editing your test plan from the mind map view in some cases.
If you used the test plan dialog to change certain aspects of a test plan, such as its name or project, and that plan also happens to be the plan that you are currently editing (2-way defects), then those aspects would be stale and would continue showing the old data until you refreshed or changed plans.
We made some upgrades to some important system software that should result in noticeable performance increases for many Hexawise operations.
This was a strange pairwise defect.
In Hexawise, plans are shared in a project. We now made it easier to share a plan into a new project. When you click the share action, there's now an option to select existing projects, or to create a new project right there.
Want to guess if this bug was a pair-wise defect? If you guessed 'yes', you're a winner!
If a user was invited to a project by someone that did not originally create the project, the invitation said that the project creator is inviting them to the project. Now it correctly identifies the inviter to the invitee in the invitation.
Fixed a regression that occurs only when exporting with no test cases. A classic pairwise defect.
The email you get when a project has been shared with you now includes a list of the test plans in the project and links to the test plans.
The requirements traceability of requirements to the test cases where they appear was only exported as a sheet in the HP QC/ALM export. It is now also exported as a sheet in the Excel export and a CSV file in the CSV exports.
Searching in the plan revisions dialog, then coming back into it kept the old search criteria, which then also caused layout issues in the dialog. This is a classic combinatorial defect caused by a sequence of specific actions.
Dismissing with the X now behaves the same as dismissing with the "cancel" link.