Applying Ubuntu QA tools and practices to upstream

Registered by Nicholas Skaggs

It would be useful to discuss where the Ubuntu QA team is moving with its focus on tools and practices and how it applies to upstream projects. It would be especially interesting to see how these tools can benefit upstream projects with regard to cross-platform Linux distributions support.

Blueprint information

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

Related branches

Sprints

Whiteboard

Product Strategy
using google test for CI
jenkins for merge proposals and automated testing
autopilot
qa integration testing
original purpose was unity oriented
being expanded to support all QT applications
testability driver
decided against using tool
written in ruby
like python more
seems unmaintained
Autopilot
can it be used to test applications?
Needs app to expose itself to dbus
QT apps do this by default
GTK support is no priority ATM
will be in quantal archive shortly
Canonical QA Team
UATH harness
provision, deploy, test, and extract results
integrates with jenkins
proof of concept is complete
will be migrating tests to new harness
Upstreams
How can we get our tests upstream?
we want all to benefit
we want them to maintain and expand
would like to be able to run tests without having to build package, change system, etc

LINKS:
    UATH
        https://launchpad.net/ubuntu-automation-test-harness
    AutoPilot
        https://launchpad.net/autopilot

(?)

Work Items

Work items:
[nskaggs] Document and open up the process surrounding the automatic testcases running on jenkins. Allow community invovlement and engagement to propose new tests and help manage the tests that are running.: POSTPONED
[hggdh2] Document and open up the process surrounding the automatic testcases running on jenkins. Allow community invovlement and engagement to propose new tests and help manage the tests that are running.: TODO
[nskaggs] How can we engage upstreams based upon the testing we are doing?: POSTPONED
[nskaggs] contact upstreams from list of critical packages we utilize in ubuntu. Help community also engage upstreams they care about.: POSTPONED
[hggdh2] contact upstreams from list of critical packages we utilize in ubuntu. Help community also engage upstreams they care about.: TODO
[nskaggs] talk to pitti: DONE

This blueprint contains Public information 
Everyone can see this information.