QA workflow for integrating partner team components

Registered by Martin Pitt on 2009-11-04

The desktop team closely works together with parner teams such as DX and OLS. Discuss the previous two cycles, identify problems, and how to avoid them in the future.

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Pedro Villavicencio
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Completed by
Martin Pitt on 2012-05-15

Related branches

Sprints

Whiteboard

[rickspencer3] removing from series goals as there are no related work items

[dbarth] - 2009-12-03: can we revive this blueprint to define and track the flow of test plans produced as part of developments, and the flow of test results that we can expect at each integration milestones (monthly + a-2, a-3, b-2 i suppose)?

Suggested /v/ork items for alpha-2: (to avoid being tracked right now)
identify test plans for the set of development targets (i suppose 1 bp <=> 1 test plan): TODO
collect test plans: TODO
publish test plans for crowd sourcing: TODO
estimate how much can be run (automation is out of scope if it has not already been defined in other bp), ie scope which testplans the QA team can run at each milestone: TODO
run test plans: TODO
report bugs and results: TODO

for alpha-3:
run test plans: TODO
report bugs and results: TODO

for beta-2:
run test plans: TODO
report bugs and results: TODO

WDYT?

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.