Schedule

Differences between revisions 1 and 38 (spanning 37 versions)
⇤ ← Revision 1 as of 2007-03-18 00:45:22 →
Size: 2360
Editor: cF5A6BF51
Comment: moved from Testing/Community
← Revision 38 as of 2008-09-29 13:19:05 → ⇥
Size: 3163
Editor: cpc1-oxfd8-0-0-cust993
Comment: updated for intrepid
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Community ISO testing schedule == <<Include(Testing/Header)>>
Line 3: Line 3:
== i386, Ubuntu erase disk == ||<tablestyle="float:right; font-size: 0.9em; background:#F1F1ED; margin: 0 0 0 0;" style="padding:0.5em;"><<TableOfContents(2)>>||
Line 5: Line 5:
 * '''Primary:''' [https://launchpad.net/~stgraber stgraber], [https://launchpad.net/~alauppe alauppe]
 * '''Secondary:''' [https://launchpad.net/~mixium mixium], [https://launchpad.net/~linuturk Linuturk], [https://launchpad.net/~bryceharrington bryce], [https://launchpad.net/~michl Michl], [https://launchpad.net/~jt-jtholmes jtholmes], [https://launchpad.net/~dg10050 dg10050]		 <<Include(Testing/Header)>>
Line 8: Line 7:
== i386, Ubuntu manual partitioning == ||<tablestyle="float:right; font-size: 0.9em; background:#F1F1ED; margin: 0 0 0 0;" style="padding:0.5em;"><<TableOfContents(2)>>||
Line 10: Line 9:
 * '''Primary:''' [https://launchpad.net/~mixium mixium], [https://launchpad.net/~linuturk Linuturk], [https://launchpad.net/~bryceharrington bryce], [https://launchpad.net/~huygens-25 huygens], [https://launchpad.net/~rubenr-canada rubenr-canada], [https://launchpad.net/~jt-jtholmes jtholmes]
 * '''Secondary:''' [https://launchpad.net/~stgraber stgraber], [https://launchpad.net/~bjkemp nailBnny], [https://launchpad.net/~jwcampbell j1mc]		 Testing of the major milestones Beta, RC and Final stretches over about a week and is done in two stages, smoke and validation testing.
Line 13: Line 11:
== i386, Ubuntu auto-resize == = Intrepid ISO test schedule =
Line 15: Line 13:
 * '''Primary:''' [https://launchpad.net/~michl Michl], [https://launchpad.net/~dg10050 dg10050]
 * '''Secondary:''' [https://launchpad.net/~mixium mixium], [https://launchpad.net/~alauppe alauppe]		 ||<rowbgcolor="#cccccc"> '''Release''' || '''Task''' || '''Date''' ||
||<rowbgcolor="#FFFFCC"> Beta || Smoke testing || Sept. 25-30 ||
||<rowbgcolor="#FFFFCC"> || ISO validation testing || Sept. 30-Oct. 1 ||
||<rowbgcolor="#FFEBBB"> Release Candidate || Smoke testing || Oct. 16-21 ||
||<rowbgcolor="#FFEBBB"> || ISO validation testing || Oct. 21-22||
||<rowbgcolor="#FFCCCC"> Final || Smoke testing || Oct. 23-28 ||
||<rowbgcolor="#FFCCCC"> || ISO validation testing || Oct. 28-29 ||
Line 18: Line 21:
== i386, Kubuntu erase disk == = Testing details =
Line 20: Line 23:
 * '''Primary:''' [https://launchpad.net/~firephoto firephoto], [https://launchpad.net/~mib-mibgames mibuk], [https://launchpad.net/~abattoir abattoir]
 * '''Secondary:''' 		In the first ''smoke test'' phase we perform a wide series of tests to cover every ISO and install method but do not attempt to test every combination. The aim is to find bugs quickly so they can be addressed for the milestone. As candidate ISO images become available we test each image following the relevant test case to each ISO in order to ensure that every ISO we ship works as expected. This phase is quite labor intensive and will require the participation of 20 or more people in a short window of time.
Line 23: Line 25:
== i386, Kubuntu manual partitioning == == Smoke testing ==
Line 25: Line 27:
 * '''Primary:''' [https://launchpad.net/~bjkemp nailBnny], [https://launchpad.net/~jwcampbell j1mc], [https://launchpad.net/~huygens-25 huygens]
 * '''Secondary:''' [https://launchpad.net/~vorian Vorian], [https://launchpad.net/~firephoto firephoto]		 The first round of testing is designed to find high impact bugs in a short period of time so they can be addressed before the milestone is released. Smoke testing should occur just after the archives are frozen. Upgrade and netboot testing can start immediately; ISO testing starts after the first daily images based on the frozen archive appear. The following elements should receive coverage during smoke testing:
Line 28: Line 29:
== i386, Kubuntu auto-resize ==
 
 * '''Primary:''' [https://launchpad.net/~vorian Vorian]
 * '''Secondary:''' [https://launchpad.net/~firephoto firephoto], [https://launchpad.net/~dg10050 dg10050], [https://launchpad.net/~abattoir abattoir]		  * Core distro flavours: '''Ubuntu, Kubuntu, Edubuntu, Server'''
 * Supported architectures: '''i386, amd64, sparc'''
 * Image types: '''Live CD, Alternate, Netboot''' (not DVDs)
 * Install methods: '''erase disk, auto-resize, manual partitioning, entire disk with encryption, Netboot, Upgrade'''
 * Select features: '''Session management applet, encrypted folder, Wubi'''
Line 33: Line 35:
== WinFOSS == Testing will be coordinated in '''#ubuntu-testing''' and the results tracked on a '''[[Testing/ISO/Smoke|simple checklist]]'''. The number of tests is kept low intentionally, but they should be performed with care (e.g. there are only 3 Live CD session test in total, but they should be thorough; testing much of the default applications and installing others).
Line 35: Line 37:
 * [https://launchpad.net/~stgraber stgraber], [https://launchpad.net/~bjkemp nailBnny], [https://launchpad.net/~mixium mixium], [https://launchpad.net/~linuturk Linuturk], [https://launchpad.net/~michl Michl] == Image validation testing ==
Line 37: Line 39:
'''Note:''' ''Please do not add yourself to this page directly, but email iso.testing AT gmail.com (read by Henrik and pochu) so we can coordinate. ''

Return to [:/..:Community Testing]		 Complete validation testing of all images and test cases. If the smoke testing was effective there should not be any show-stopper bugs appearing at this stage. The broader testing is likely to reveal a large number of minor bugs though. These should be targeted at the next milestone or stable release updates. Track image validation testing at '''[[http://iso.qa.ubuntu.com/|iso.qa.ubuntu.com]]'''.

Testing of the major milestones Beta, RC and Final stretches over about a week and is done in two stages, smoke and validation testing.

Intrepid ISO test schedule

Release

Task

Date

Beta

Smoke testing

Sept. 25-30

ISO validation testing

Sept. 30-Oct. 1

Release Candidate

Smoke testing

Oct. 16-21

ISO validation testing

Oct. 21-22

Final

Smoke testing

Oct. 23-28

ISO validation testing

Oct. 28-29

Testing details

In the first smoke test phase we perform a wide series of tests to cover every ISO and install method but do not attempt to test every combination. The aim is to find bugs quickly so they can be addressed for the milestone. As candidate ISO images become available we test each image following the relevant test case to each ISO in order to ensure that every ISO we ship works as expected. This phase is quite labor intensive and will require the participation of 20 or more people in a short window of time.

Smoke testing

The first round of testing is designed to find high impact bugs in a short period of time so they can be addressed before the milestone is released. Smoke testing should occur just after the archives are frozen. Upgrade and netboot testing can start immediately; ISO testing starts after the first daily images based on the frozen archive appear. The following elements should receive coverage during smoke testing:

  • Core distro flavours: Ubuntu, Kubuntu, Edubuntu, Server

  • Supported architectures: i386, amd64, sparc

  • Image types: Live CD, Alternate, Netboot (not DVDs)

  • Install methods: erase disk, auto-resize, manual partitioning, entire disk with encryption, Netboot, Upgrade

  • Select features: Session management applet, encrypted folder, Wubi

Testing will be coordinated in #ubuntu-testing and the results tracked on a simple checklist. The number of tests is kept low intentionally, but they should be performed with care (e.g. there are only 3 Live CD session test in total, but they should be thorough; testing much of the default applications and installing others).

Image validation testing

Complete validation testing of all images and test cases. If the smoke testing was effective there should not be any show-stopper bugs appearing at this stage. The broader testing is likely to reveal a large number of minor bugs though. These should be targeted at the next milestone or stable release updates. Track image validation testing at iso.qa.ubuntu.com.

Testing/ISO/Schedule (last edited 2009-09-29 15:22:39 by 63)