Schedule
|
Size: 3723
Comment: converted to 1.6 markup
|
← Revision 42 as of 2009-09-29 15:22:39 ⇥
Size: 3023
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Testing of the major milestones Beta, RC and Final stretches over about a week and is done in three stages to ensure the best use of available human resources. | 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 7: | Line 7: |
| = Hardy ISO test schedule = | = Karmic ISO test schedule = |
| Line 10: | Line 10: |
| ||<rowbgcolor="#FFFFCC"> Beta || Smoke testing || March 13-15 || ||<rowbgcolor="#FFFFCC"> || Fix validation testing || March 15-17 || ||<rowbgcolor="#FFFFCC"> || ISO validation testing || March 18-19 || ||<rowbgcolor="#FFEBBB"> Release Candidate || Smoke testing || April 10-12 || ||<rowbgcolor="#FFEBBB"> || Fix validation testing || April 12-14 || ||<rowbgcolor="#FFEBBB"> || ISO validation testing || April 15-16 || ||<rowbgcolor="#FFCCCC"> Final || Smoke testing || April 17-19 || ||<rowbgcolor="#FFCCCC"> || Fix validation testing || April 19-21 || ||<rowbgcolor="#FFCCCC"> || ISO validation testing || April 22-23 || |
||<rowbgcolor="#FFFFCC"> Beta || Smoke testing || Sept. 24-29 || ||<rowbgcolor="#FFFFCC"> || ISO validation testing || Sept. 29-Sept. 30 || ||<rowbgcolor="#FFEBBB"> Release Candidate || Smoke testing || Oct. 15-20 || ||<rowbgcolor="#FFEBBB"> || ISO validation testing || Oct. 20-22|| ||<rowbgcolor="#FFCCCC"> Final || Smoke testing || Oct. 22-27 || ||<rowbgcolor="#FFCCCC"> || ISO validation testing || Oct. 27-28 || |
| Line 22: | Line 19: |
| 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 developers fix these bugs as well as other milestoned bugs we perform ''fix validation testing'' to confirm that these bugs are indeed fixed and that the fixes have not introduced other problems. Finally we perform complete ISO validation testing in which we apply every 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. | 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 28: | Line 25: |
| * Core distro flavours: '''Ubuntu, Kubuntu, Edubuntu, Server''' * Supported architectures: '''i386, amd64, sparc''' |
* Core distro flavours: '''Ubuntu, Kubuntu, Edubuntu, Xubuntu, UNR, UMR, Server''' * Supported architectures: '''i386, amd64, sparc, armel''' |
| Line 32: | Line 29: |
| * Select new features: '''Compiz, tracker, Firefox 3, GVFS, X config tool, disk encryption, Active Directory, Wubi''' | * Select features: '''Session management applet, encrypted folder, Wubi''' |
| Line 36: | Line 33: |
| == Fix validation testing == Test the changes that were introduced after the archive freeze to verify the fixes work and that they don't break surrounding functionality. '''[[Testing/ISO/FixValidation|Track fix validation testing here]]''' |
|
| Line 42: | Line 35: |
| Complete validation testing of all images and test cases. If phases 1 and 2 have been 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]]'''. | 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.
Karmic ISO test schedule
Release |
Task |
Date |
Beta |
Smoke testing |
Sept. 24-29 |
|
ISO validation testing |
Sept. 29-Sept. 30 |
Release Candidate |
Smoke testing |
Oct. 15-20 |
|
ISO validation testing |
Oct. 20-22 |
Final |
Smoke testing |
Oct. 22-27 |
|
ISO validation testing |
Oct. 27-28 |
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, Xubuntu, UNR, UMR, Server
Supported architectures: i386, amd64, sparc, armel
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)