Improving the testing experience for contributors

Registered by Nicholas Skaggs on 2013-04-29

Let's talk about the user experience for a contributor to ubuntu quality. How can we improve on the overall testing experience?

Blueprint information

Status:
Not started
Approver:
Jono Bacon
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Nicholas Skaggs
Definition:
New
Series goal:
Accepted for saucy
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Discussion points
What does the feedback loop look like for someone who submits a test result?
What does the feedback loop look like for someone who submits a testcase? (via, https://launchpad.net/ubuntu-autopilot-tests/ or https://launchpad.net/ubuntu-manual-tests/)
Weaknesses raised:
It's hard to file bugs
  how can we know if we found a duplicate or not?
  duplicate bug
duplicates of private bugs
people don't realise that they need to report results and bugs on the iso tracker.
Ideas:
way to give visibility to
better show duplicate bugs inside qatracker
Generate list of bugs filed by the team?
    intend to follow-up and confirm them?
why don't people report things via the tracker?
    difficult if machine isn't working so well
add the 'contribute an manual|automatic testcase' to the ubuntu accomplishment system
offline bug reporting
reporitng a bug from a broken machine
reporting a bug from a vm
which package to file a bug against
LINKS:
https://wiki.ubuntu.com/Testing/QATracker
https://wiki.ubuntu.com/QATeam/ContributingTestcases
https://wiki.ubuntu.com/Accomplishments

(?)

Work Items

Work items for ubuntu-13.07:
[nskaggs] Investigate generating a filtered buglist for use on the tracker (maybe use only team bugs, only recent bugs, only "common" bugs, only high heat bugs, etc): POSTPONED

Work items for ubuntu-13.06:
[nskaggs] publicize resources availible (blog, mailing list, etc): DONE
[nskaggs] Look at adding the help links/docs to the tracker: DONE
[nskaggs] Hold classroom session on searching and filing bugs: DONE
[nskaggs] colloborate with bug squad on bug reporting for the list below -- do docs exist, can we add to or make them availible to everyone on the QA team -- offline bug reporting, reporitng a bug from a broken machine, reporting a bug from a vm, which package to file a bug against: DONE
[nskaggs] send out survey on qatracker usage; do you test, do you use it, why or why not?: DONE
[phillw] add an extra classroom sesssion for using guestfish to pull files from a KVM virtual machine.: INPROGRESS
[phillw] hold the revised classroom sessions on KVM and Virtual Box to feed into testdrive.: INPROGRESS

Work items:
[javier-lopez] add the 'contribute an manual|automatic testcase' to the ubuntu accomplishment system: DONE
[philipballew] add the 'contribute an manual|automatic testcase' to the ubuntu accomplishment system: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.