The test case # column would lose alignment with long parameter names on Firefox (pairwise defect).
This is both an improved user experience (there are no longer 2 primary buttons competing for your attention) and addresses a bug where the button goes away with a certain sequence of user actions.
Added a step to the new user email validation process to prevent early activation by aggressive email monitoring systems that access the link.
Fixed a pairwise defect in the new feature of showing the project the plan belongs to when opening the "Your Test Plans" dialog for the first time. If you happen to be in a read-only sample plan, the "Your Sample Test Plans" project wouldn't be found in the list of your projects, and the dialog would hang.
The same useful feedback from an unsuccessful import wasn't available when importing into an existing plan, but now it is.
This was an interesting 3-way defect involving a certain type of data, "(?)" in the name, a certain operation, updates, and a certain mode of the operation, bulk edit.
For the curious, "(?)" proved problematic as it interfered with a regular expression being used to handle the edit request.
After creating a new project, you're now brought to the share dialog as the next step, rather than the "Your plans" dialog.
When working on a test plan in a project, the "Your plans" dialog now opens to that project by default, rather than to "Your plans".
The # of interactions tooltip shows "null" when there are no "any valid values" (purple italics) in the generated test. It's rare to have none, but quite possible. A classic of the pairwise defect genre.
This warning had stopped working as a regression.
A parameter length warning dialog that appears when parameters are created with eight or more values.
The first issue was that the word 'parameters' was always pluralized, even if there was only one parameter listed.
The second issue was that we were showing the actual array (as in "[OS, Browser]") instead of a list of the array's elements in the dialog.
This prevents Hexawise from continually loading a test combination strength you aren't interested in. Before Hexawise used last computed strength rather than last viewed/used.
Are there any defects that aren't pairwise? Oh, so very few.
A true classic of a pair-wise defect. Put this one in the dictionary as a canonical example of the term.
Editing the name of the project that owns that plan you're in from the Edit Project dialog would make the share link on the plan's page stale.