Test manager

From OLPC
Revision as of 12:07, 24 December 2008 by Mchua (talk | contribs) (New page: == Role == The role of a test manager is to handle QA and testing for the release they are responsible for. A test manager is responsible for being able to give the release manager answe...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Role

The role of a test manager is to handle QA and testing for the release they are responsible for.

A test manager is responsible for being able to give the release manager answers, given the input of a build to test and a set of "finish line" criteria for what the release should look like when it's done:

  • Are we done yet? How close are we to the "finish line" for the release? (Often this will be phrased as "What percentage of blocking tickets/bugs and regressions have been verified closed in the release candidate?")
  • What are the risks? If we were to release our current build today, what do we know (confirmed open bugs) and what do we know we don't know (areas of potential regression/risk that haven't been fully explored)? In particular, have there been any regressions?

Test managers

So far, test managers have been OLPC staff internally appointed to the position.

Present

Past

  • 8.2.0 - Joe Feinstein