Launchpad Entry: qa-maverick-improve-iso-tracker
Several activities require improvements to the ISO tracker. This specification is an umbrella for all those requirements.
During UDS Maverick, several users of the QA tracker recommended a set of improvements to the tracker in order to be able to better perform this activities.
- Charlie is a regular contributor to ISO testing. Sometimes he mark a test as Started, and then realizes that it wasn't the one he wanted to start. There is no way to unmark a test.
For 436450 we need a very basic interface. To begin with, it would be enough to have the ability to add new images and new testcases. The deletion and modification is currently out of scope and could be added in the future.
579155: In the result page, there is need of a new button "Delete result" to delete the user's result for that particular testcase.
291089: A new filter "Not Completed" needs to be added to the web UI.
579155: A "delete result" method needs to be added.
578349: A small fix to trim spaces needs to be added.
524368: A script needs to be written to generate the data.
291089: qatracker_buildlist function needs to be changed to filter by "not completed"
507950: qatracker_buildstat needs to distinguish between started and not started. The started ones need to be shown somehow.
495373: The report needs to be updated to the new images and reflect optional testcases.
582180: A small change in the database is needed. Filters are data based.
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.