Cadence
|
Size: 1932
Comment:
|
← Revision 16 as of 2013-10-22 21:08:31 ⇥
Size: 2714
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(QATeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = Deprecated = /!\ '''NOTE, as of Trusty we as a community are migrating away from specificly scheduled cadence testing. This role will be fulfilled by automated testing. Instead exploratory manual testing is encouraged at all times throughout the cycle. See the [[https://wiki.ubuntu.com/QATeam/Roles/Tester|tester role]] for more information.''' /!\ |
|
| Line 2: | Line 11: |
| Cadence testing is a term used to describe how the quality team operates it's testing schedule. We follow a 2 week cadence for testing. This means, every 2 weeks we focus and test the various aspects of ubuntu. This includes image testing, as well as other areas of concern for QA that are specific to that cadence week. | Cadence testing is a term used to describe how the quality team operates its testing schedule. We follow a 2-week cadence for testing. This means that every 2 weeks, we focus and test the various aspects of Ubuntu. This includes image testing, as well as other areas of concern for QA that are specific to that cadence week. |
| Line 5: | Line 14: |
| Each release will have it's own schedule. Some adjustments to the strict 2 weeks may be made for holidays, etc, so do pay attention to the schedule for each release. [[https://wiki.ubuntu.com/QATeam/Cadence/Raring|Raring]] |
Each release will have its own schedule. Some adjustments to the strict 2 weeks may be made for holidays, etc, so do pay attention to the schedule for each release. In addition, we normally delay the first week of cadence testing until some initial development work has occurred. === Saucy === '''[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy|Saucy Cadence Schedule]]''' === Raring === '''[[https://wiki.ubuntu.com/QATeam/Cadence/Raring|Raring Cadence Schedule]]''' |
| Line 10: | Line 21: |
| In practice, every 2 weeks we as a team test the daily images for ubuntu over the course of the week. Members download the daily iso for ubuntu (i386/amd64) and execute the testcases for the iso and report there results to the tracker. | In practice, every 2 weeks, we as a team test the daily images for Ubuntu over the course of the week. Members download the daily iso for Ubuntu (i386/amd64) and execute the testcases for the iso and report their results to the tracker. |
| Line 12: | Line 23: |
| The week is defined as Saturday to Saturday (in your local timezone). In addition during this testing week, we also test some specific testcases that have been chosen for the week. These change for every cadence week, but typically include testing specfic packages, such as a desktop application like nautilus or libreoffice, or testing hardware, like checking laptop microphone and webcam functionality for regressions. | The week is defined as Saturday to Saturday (in your local timezone). In addition during this testing week, we also test some specific testcases that have been chosen for the week. These change every cadence week, but typically include testing specific packages, such as a desktop application like nautilus or libreoffice, or testing hardware, like checking laptop microphone and webcam functionality for regressions. |
Deprecated
![Warning /!\](/moin_static198/light/img/icon_eek.png "Warning /!\"){kind=icon}
NOTE, as of Trusty we as a community are migrating away from specificly scheduled cadence testing. This role will be fulfilled by automated testing. Instead exploratory manual testing is encouraged at all times throughout the cycle. See the tester role for more information.
Cadence
Cadence testing is a term used to describe how the quality team operates its testing schedule. We follow a 2-week cadence for testing. This means that every 2 weeks, we focus and test the various aspects of Ubuntu. This includes image testing, as well as other areas of concern for QA that are specific to that cadence week.
Schedule
Each release will have its own schedule. Some adjustments to the strict 2 weeks may be made for holidays, etc, so do pay attention to the schedule for each release. In addition, we normally delay the first week of cadence testing until some initial development work has occurred.
Saucy
Raring
How does it work?
In practice, every 2 weeks, we as a team test the daily images for Ubuntu over the course of the week. Members download the daily iso for Ubuntu (i386/amd64) and execute the testcases for the iso and report their results to the tracker.
The week is defined as Saturday to Saturday (in your local timezone). In addition during this testing week, we also test some specific testcases that have been chosen for the week. These change every cadence week, but typically include testing specific packages, such as a desktop application like nautilus or libreoffice, or testing hardware, like checking laptop microphone and webcam functionality for regressions.
How can I help?
You can help by testing the daily images during the cadence week, as well as submitting results for the targeted testcases as part of that week's testing. Follow the schedule link above and find the current cadence testing week. Inside you'll find links to the tracker that contains milestones and testcases for you to submit results against. Follow the tests and submit your results.
Need help learning how to submit results and use the tracker? Start here. Then follow the linked tutorial for submitting cadence test results.
Testing/Cadence (last edited 2013-10-22 21:08:31 by adsl-98-70-51-119)