On 13 August 2013 15:26, Stevan Radaković <email address hidden> wrote:
> Wrt selected tests, we include default behavior to be only those that have latest builds, and remember any other user selection.
> So if you change selected tests once, thet selection will be remembered for next time you visit the page.
> The main reason for this is that there are some reports that have very large amount of tests where some of which are outdated and not necessary; the other reason being it was the part of QA TL wishlist during design.
To resolve the use case "large amount of outdated tests", filters
should be used properly:
test case filtering feature, a filter can be limited to test runs with
particular values for particular attributes.
Wrt the 2nd reason, I haven't been involved in the design hence I
can't comment on Miloswz's wishlist.
It seems to me that the page has still a usability issue if we keep
current behavior.
On 13 August 2013 15:26, Stevan Radaković <email address hidden> wrote:
> Wrt selected tests, we include default behavior to be only those that have latest builds, and remember any other user selection.
> So if you change selected tests once, thet selection will be remembered for next time you visit the page.
> The main reason for this is that there are some reports that have very large amount of tests where some of which are outdated and not necessary; the other reason being it was the part of QA TL wishlist during design.
To resolve the use case "large amount of outdated tests", filters
should be used properly:
test case filtering feature, a filter can be limited to test runs with
particular values for particular attributes.
Wrt the 2nd reason, I haven't been involved in the design hence I
can't comment on Miloswz's wishlist.
It seems to me that the page has still a usability issue if we keep
current behavior.