Addressed an error in a small number of cases.
Should result in some minor performance improvements.
Some browser specific content layout and loading issues.
Updated the HP QC / ALM extension so they don't clash if you export them both, and so they are easier to tell apart at a glance without having to open the file.
Thanks to Katie for the suggestion.
If you're typing out your auto-script and enter the curly bracket { character there is an auto-complete menu to select the parameter name. You can type the start of the parameter name or arrow to the parameter you want and press the enter key to select it. Your hands never need to leave the keyboard. Zoom, zoom!
Thanks to Eric for the bug report.
This makes spotting the variation inserted into the test scripts extra easy.
Invalid pair could be included in requirement cases of test plans in very rare cases (3-way cause) with sparse requirements.
Thank you to Dora and Kevin for finding and reporting this error.
Should result in minor (<~10%) performance improvements.
Multiple clicks could result in loading confirmation multiple times.
The test plan notes were no longer on the Define Inputs header after editing a parameter until you navigated away or refreshed. This has been resolved.
The notes for a test plan are now in the top header of each plan screen, rather than in the sidebar of the Define Inputs screen. This means they are available in every screen.
There is a counter on them letting you know how many notes there are. If the plan is shared with multiple people, and it has notes, then the notes dialog is shown when the plan is opened to decrease the likelihood that an important note is missed.
2 additional non-obvious "no possible value" scenarios with constraints in test plans are now prevented when the value pair add is attempted.
A thorough audit of height and width handling in the matrix codebase (see above) uncovered an additional defect which caused rows further down the matrix chart to be rendered without the white divider lines for each column.
A matrix chart that is longer than it is wide (first parameter is the largest) would be cut off by as many rows as the 1st parameter was larger than the next largest parameter. An odd sounding defect (height and width were switched in one place in the code) but actually a fairly simple pairwise defect with some variation you'd be unlikely to identify (make the 1st parameter the largest).
Thanks to Vinay for pointing out this issue!
Is more aesthetically pleasing.
They are now all standardized with a reference to the plan name. Before some referenced the plan name and some didn't. The context is more important now that the active plan isn't always visible in a side panel.