(qa beat for 212) |
(qa beat for 213) |
||
| Line 10: | Line 10: | ||
=== Test Days === | === Test Days === | ||
There was no Test Day last week. Next week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-02-18_Color_management</ref> will be on color management<ref>http://fedoraproject.org/wiki/Features/ColorManagement</ref>. This significant new feature for Fedora 13 makes it easy to set up color profiles for monitors, scanners and printers, meaning you can rely on seeing the true colors of images from production all the way through to final printing. This is particularly significant for photographers and designers, but a correct color profile can improve anyone's desktop experience, so please come along to make sure the new color management tools get tested on a wide range of hardware. We would particularly appreciate testing from anyone with access to a colorimeter. The Test Day will run all day on Thursday 2010-02-18 in the #fedora-test-day IRC channel. | |||
If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>. | |||
<references/> | <references/> | ||
| Line 18: | Line 18: | ||
=== Weekly meetings === | === Weekly meetings === | ||
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-02- | The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-02-08. The full logs are available<ref>http://fedoraproject.org/wiki/QA/Meetings/20100208</ref>. [[User:Jlaska|James Laska]] and [[User:Kevin|Kevin Fenzi]] arranged to update the list of RSS feeds tracked by the QA IRC bot, zodbot. | ||
[[User: | [[User:Jlaska|James Laska]] reported that [[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] had arranged a meeting the next day to discuss plans for the AutoQA results database. James also mentioned he had not had time to discuss updating the QA calendar with [[User:poelstra|John Poelstra]]. | ||
[[User: | [[User:Jlaska|James Laska]], [[User:jkeating|Jesse Keating]] and [[User:Adamwill|Adam Williamson]] discussed the planned Wiki page for 'last known good' Rawhide builds. Jesse clarified the process from the release engineering side, and James planned to document everything in a trac ticket to track the creation of the Wiki page. | ||
[[User: | [[User:Jlaska|James Laska]] noted that the third automated Rawhide acceptance test point had passed the previous week, and had been marked as a failure due to a bug<ref>http://bugzilla.redhat.com/show_bug.cgi?id=559290</ref> resulting in high memory requirements for installation. | ||
[[User: | [[User:Wwoods|Will Woods]] was not around to provide an AutoQA project update, but had provided a blog post with some information<ref>http://qa-rockstar.livejournal.com/9234.html</ref>. [[User:Kparal|Kamil Paral]] reported that he had not made any progress on rpmguard this week. [[User:Jlaska|James Laska]] passed on a report on installation automation from [[User:Liam|Liam Li]], who had been discussing the best approach for booting with custom kernel parameters with the virtualization team<ref>http://lists.fedoraproject.org/pipermail/virt/2010-February/001809.html</ref>. On gwt packaging, James reported that he had had feedback from upstream developers about the bundled JARs<ref>http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/fc5713c023919618/f423351722bc7afe</ref>. He was aiming to have one package in progress during the week. | ||
[[User: | [[User:Adamwill|Adam Williamson]] briefly outlined upcoming events, noting the first Alpha test compose was due in the coming week, with installation and desktop validation testing planned. The second Alpha blocker bug meeting was also on the calendar. | ||
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2010-02-09. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-09/fedora-meeting.2010-02-09-15.06.log.html</ref>. [[User:Adamwill|Adam Williamson]] reported that he had sent a draft stock response text for bugs filed against orphaned packages to the mailing list for review<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088369.html</ref>. The group agreed that the draft looked good. | |||
[[User: | [[User:campbecg|Chris Campbell]] reported that he was looking into implementing multi-row button capability for the triage Jetpack script, as having a button for each stock response would result in more buttons than it is currently capable of handling. He said he would give another update next week. | ||
[[User: | [[User:Adamwill|Adam Williamson]] highlighted the upcoming second blocker bug review meeting for Fedora 13 Alpha, and asked group members to elevate any bugs they thought might constitute Alpha blockers. [[User:campbecg|Chris Campbell]] said he wasn't aware of any really serious nouveau bugs at present. Adam said he would check on intel and radeon bugs. | ||
[[User: | [[User:Tk009|Edward Kirk]] reported that he had not yet been able to send out the email to discuss rearranging the weekly meeting time. | ||
[[User:Tk009|Edward Kirk]] reported for Juan P. Daza on his update of the active triager list<ref>http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref>. He had emailed all known triagers and found 23 did not respond (while 56 did). None of those 23 were listed on the active triagers page, so no adjustment would be necessary. | |||
[[User: | [[User:Tk009|Edward Kirk]] noted that he was still working on updating the housekeeping procedures for closing blocker tracking bugs for Fedora releases that have already gone out. He expected it would only need some Wiki page updates, and will report next week. | ||
The next QA weekly meeting will be held on 2010-02- | During the open floor period, it became clear that almost all components on the components list<ref>http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref> were listed as not requiring help. The group thought this was probably not desired, so [[User:Adamwill|Adam Williamson]] and [[User:Tk009|Edward Kirk]] promised to look into it. | ||
The next QA weekly meeting will be held on 2010-02-15 at 1600 UTC in #fedora-meeting. The next Bugzappers weekly meeting will be held on 2010-02-16 at 1500 UTC in #fedora-meeting. | |||
<references/> | <references/> | ||
=== | === Fedora 13 Alpha test compose === | ||
[[User: | [[User:Rhe|Rui He]] outlined<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088396.html</ref> the upcoming Fedora 13 Alpha test compose validation testing schedule, with the release due 2010-02-11 and desktop and installation validation testing due to run through 2010-02-17. She linked to the installation<ref>http://fedoraproject.org/wiki/QA:Fedora_13_Alpha_TC_Install_Test_Results</ref> and desktop<ref>http://fedoraproject.org/wiki/QA:Fedora_13_Alpha_TC_Desktop_Test_Results</ref> results matrices, and asked group members to contribute results if they could. | ||
<references/> | <references/> | ||
=== | === Automated live image testing === | ||
Jon Jaroker kindly explained<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088436.html</ref> some work he has been doing on implemented ongoing automated testing of the Fedora live desktop image. His goal is to have an automated testing system which tests both the boot process and some basic desktop functionality using automated scripts, and flags up regressions. [[User:Adamwill|Adam Williamson]] thanked Jon for his work<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088437.html</ref> and suggested he co-ordinate with [[User:maxamillion|Adam Miller]] on live image automation, and consider integrating his work into the AutoQA framework<ref>http://fedoraproject.org/wiki/AutoQA</ref>. | |||
<references/> | <references/> | ||
Revision as of 23:57, 14 February 2010
QualityAssurance
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
Test Days
There was no Test Day last week. Next week's Test Day[1] will be on color management[2]. This significant new feature for Fedora 13 makes it easy to set up color profiles for monitors, scanners and printers, meaning you can rely on seeing the true colors of images from production all the way through to final printing. This is particularly significant for photographers and designers, but a correct color profile can improve anyone's desktop experience, so please come along to make sure the new color management tools get tested on a wide range of hardware. We would particularly appreciate testing from anyone with access to a colorimeter. The Test Day will run all day on Thursday 2010-02-18 in the #fedora-test-day IRC channel.
If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[3].
Weekly meetings
The QA group weekly meeting[1] was held on 2010-02-08. The full logs are available[2]. James Laska and Kevin Fenzi arranged to update the list of RSS feeds tracked by the QA IRC bot, zodbot.
James Laska reported that Will Woods and Kamil Paral had arranged a meeting the next day to discuss plans for the AutoQA results database. James also mentioned he had not had time to discuss updating the QA calendar with John Poelstra.
James Laska, Jesse Keating and Adam Williamson discussed the planned Wiki page for 'last known good' Rawhide builds. Jesse clarified the process from the release engineering side, and James planned to document everything in a trac ticket to track the creation of the Wiki page.
James Laska noted that the third automated Rawhide acceptance test point had passed the previous week, and had been marked as a failure due to a bug[3] resulting in high memory requirements for installation.
Will Woods was not around to provide an AutoQA project update, but had provided a blog post with some information[4]. Kamil Paral reported that he had not made any progress on rpmguard this week. James Laska passed on a report on installation automation from Liam Li, who had been discussing the best approach for booting with custom kernel parameters with the virtualization team[5]. On gwt packaging, James reported that he had had feedback from upstream developers about the bundled JARs[6]. He was aiming to have one package in progress during the week.
Adam Williamson briefly outlined upcoming events, noting the first Alpha test compose was due in the coming week, with installation and desktop validation testing planned. The second Alpha blocker bug meeting was also on the calendar.
The Bugzappers group weekly meeting[7] was held on 2010-02-09. The full log is available[8]. Adam Williamson reported that he had sent a draft stock response text for bugs filed against orphaned packages to the mailing list for review[9]. The group agreed that the draft looked good.
Chris Campbell reported that he was looking into implementing multi-row button capability for the triage Jetpack script, as having a button for each stock response would result in more buttons than it is currently capable of handling. He said he would give another update next week.
Adam Williamson highlighted the upcoming second blocker bug review meeting for Fedora 13 Alpha, and asked group members to elevate any bugs they thought might constitute Alpha blockers. Chris Campbell said he wasn't aware of any really serious nouveau bugs at present. Adam said he would check on intel and radeon bugs.
Edward Kirk reported that he had not yet been able to send out the email to discuss rearranging the weekly meeting time.
Edward Kirk reported for Juan P. Daza on his update of the active triager list[10]. He had emailed all known triagers and found 23 did not respond (while 56 did). None of those 23 were listed on the active triagers page, so no adjustment would be necessary.
Edward Kirk noted that he was still working on updating the housekeeping procedures for closing blocker tracking bugs for Fedora releases that have already gone out. He expected it would only need some Wiki page updates, and will report next week.
During the open floor period, it became clear that almost all components on the components list[11] were listed as not requiring help. The group thought this was probably not desired, so Adam Williamson and Edward Kirk promised to look into it.
The next QA weekly meeting will be held on 2010-02-15 at 1600 UTC in #fedora-meeting. The next Bugzappers weekly meeting will be held on 2010-02-16 at 1500 UTC in #fedora-meeting.
- ↑ http://fedoraproject.org/wiki/QA/Meetings
- ↑ http://fedoraproject.org/wiki/QA/Meetings/20100208
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=559290
- ↑ http://qa-rockstar.livejournal.com/9234.html
- ↑ http://lists.fedoraproject.org/pipermail/virt/2010-February/001809.html
- ↑ http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/fc5713c023919618/f423351722bc7afe
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2010-02-09/fedora-meeting.2010-02-09-15.06.log.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-February/088369.html
- ↑ http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
- ↑ http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
Fedora 13 Alpha test compose
Rui He outlined[1] the upcoming Fedora 13 Alpha test compose validation testing schedule, with the release due 2010-02-11 and desktop and installation validation testing due to run through 2010-02-17. She linked to the installation[2] and desktop[3] results matrices, and asked group members to contribute results if they could.
Automated live image testing
Jon Jaroker kindly explained[1] some work he has been doing on implemented ongoing automated testing of the Fedora live desktop image. His goal is to have an automated testing system which tests both the boot process and some basic desktop functionality using automated scripts, and flags up regressions. Adam Williamson thanked Jon for his work[2] and suggested he co-ordinate with Adam Miller on live image automation, and consider integrating his work into the AutoQA framework[3].