iso tracker hard to find last time a daily build was tested

[Lyn Perrine]

On iso.qa.ubuntu.com if you want to say find the last time a testcase was performed for say the daily non milestone builds on an image the current only way to do this is check see removed and superseeded builds which lists all of the builds and ends up seeing many images and is diffuclt to say find the last time lubuntu-desktop-amd64 iso was tested for a live session. I would rather have a column on the iso tracker to say the last time the image was tested so if a testcase has not been done in a while volunteer testers can easily see that information and get test coverage over the testcases without having to scroll through a wall of dialy builds.

http://iso.qa.ubuntu.com/qatracker/milestones/351/builds/112146/testcases

I really would want to use http://iso.qa.ubuntu.com/qatracker/milestones/351/builds/112146/testcases to maybe show the last image tested in a column to see that last time it was done. This will make it easier to balance out test coverage for dialy builds. I don't see this being as useful for milestones as there are a few images. I wish a last time to get test coverage over time which is difficult in the current way the tracker is layed out. I don't know if this will be difficult on the backend though?

[Nicholas Skaggs (nskaggs)]

This makes sense Brendan, although I'm not sure of what sort of UI changes would make it possible. We'd need to think about how to present the information too.

[Lyn Perrine (walterorlin)]

I took a screenshot of the info in the tracker and spent a few minutes with gimp for what I was thinking this could look like and then the image of the last testcase with something like the http://iso.qa.ubuntu.com/modules/qatracker/misc/result-1.png icon next to it to see wheteher it passed or failed and my previous screenshot is what it looks like currently in Lubuntu and this is a draft of the way I want to display the information.

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

I agree this would be a great improvement for testers to know where they should focus their effort. I think the more we can focus on testing dailies rather than simply fretting when milestones come, that would make a big difference.

Additionally, having a summary would be really great for release managers. Like per flavor there could be something like
image | testcase-name | last-test-date | last-test-status | collected-bugs
but that's probably a separate bug.