From Fedora Project Wiki

< FWN‎ | Beats

m (Adjusted QA participants and added quick-start guide <ref>)
m (correction john brown to edward kirk (that would be me ))
Line 20: Line 20:
 
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on February 11th. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090211.log.html</ref>. [[User:Wwoods|Will Woods]] gave a status report on the progress of the autoqa<ref>http://git.fedorahosted.org/git/?p=autoqa.git;a=summary</ref> project, which is working on creating automated test scripts to run whenever certain events happen. He also reported on progress with the Nitrate<ref>http://fedorahosted.org/nitrate</ref> project, which is for collecting test cases and test plans and compiling results from running them. [[User:Johannbg|Jóhann Guðmundsson]] asked if it will be possible to pull existing test cases from the current Wiki-based system into Nitrate when it is released, and [[User:Wwoods|Will Woods]] said this is likely to be possible.
 
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on February 11th. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090211.log.html</ref>. [[User:Wwoods|Will Woods]] gave a status report on the progress of the autoqa<ref>http://git.fedorahosted.org/git/?p=autoqa.git;a=summary</ref> project, which is working on creating automated test scripts to run whenever certain events happen. He also reported on progress with the Nitrate<ref>http://fedorahosted.org/nitrate</ref> project, which is for collecting test cases and test plans and compiling results from running them. [[User:Johannbg|Jóhann Guðmundsson]] asked if it will be possible to pull existing test cases from the current Wiki-based system into Nitrate when it is released, and [[User:Wwoods|Will Woods]] said this is likely to be possible.
  
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on February 10th. The group agreed that the current list of most-important components should be updated, and [[User:Tk009|John Brown]] will do this. [[User:Tk009|John Brown]], Brennan Ashton and [[User:Adamwill|Adam Williamson]] (links) agreed that simple goals should be set for the group, but did not reach final agreement on what these should be. [[User:Adamwill|Adam Williamson]] suggested that Bug Days be revived and made weekly, and this idea was supported by [[User:Tk009|John Brown]] and Brennan Ashton.
+
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on February 10th. The group agreed that the current list of most-important components should be updated, and [[User:Tk009|Edward Kirk]] will do this. [[User:Tk009|Edward Kirk]], Brennan Ashton and [[User:Adamwill|Adam Williamson]] (links) agreed that simple goals should be set for the group, but did not reach final agreement on what these should be. [[User:Adamwill|Adam Williamson]] suggested that Bug Days be revived and made weekly, and this idea was supported by [[User:Tk009|Edward Kirk]] and Brennan Ashton.
  
 
The next QA weekly meeting will be held on February 18th at 1600 UTC in #fedora-qa, and the next Bugzappers weekly meeting on February 17th at 1700 UTC in #fedora-bugzappers.
 
The next QA weekly meeting will be held on February 18th at 1600 UTC in #fedora-qa, and the next Bugzappers weekly meeting on February 17th at 1700 UTC in #fedora-bugzappers.

Revision as of 14:26, 16 February 2009

QualityAssurance

In this section, we cover the activities of the QA team[1].

Contributing Writer: Adam Williamson

Test Days

This week's regular test day[1] was on iSCSI[2]. Martin Sivak and Hans de Goede represented the developers, and testing was lead by User:mganisin with assistance from Chris Williams, Mike Anderson, Michael Christie and James Laska. Test cases worked on during the test day can be seen on the page. Please record any additional test ideas or considerations at Exploratory Testing iSCSI. Consult the quick start guide[3] for creating a software-based iscsi target for use with testing.

Next week's test day[4] will be on the 20 Second Startup[5] feature planned for Fedora 11. It will be held on Thursday (2009-02-19) in the #fedora-qa channel on Freenode IRC. Please drop by if you would like to help test and improve boot speed for Fedora 11.

Weekly meetings

The QA group weekly meeting[1] was held on February 11th. The full log is available[2]. Will Woods gave a status report on the progress of the autoqa[3] project, which is working on creating automated test scripts to run whenever certain events happen. He also reported on progress with the Nitrate[4] project, which is for collecting test cases and test plans and compiling results from running them. Jóhann Guðmundsson asked if it will be possible to pull existing test cases from the current Wiki-based system into Nitrate when it is released, and Will Woods said this is likely to be possible.

The Bugzappers group weekly meeting[5] was held on February 10th. The group agreed that the current list of most-important components should be updated, and Edward Kirk will do this. Edward Kirk, Brennan Ashton and Adam Williamson (links) agreed that simple goals should be set for the group, but did not reach final agreement on what these should be. Adam Williamson suggested that Bug Days be revived and made weekly, and this idea was supported by Edward Kirk and Brennan Ashton.

The next QA weekly meeting will be held on February 18th at 1600 UTC in #fedora-qa, and the next Bugzappers weekly meeting on February 17th at 1700 UTC in #fedora-bugzappers.

Wiki re-organization

Work continued on the ongoing project to rewrite and re-organize the main pages in the QA team's Wiki space[1]. Adam Williamson, Jóhann Guðmundsson, Christopher Beland and Leam Hall all contributed ideas, suggestions and drafts.[2][3]

Release-critical bug process

Adam Williamson initiated a discussion[1] regarding the process for handling release-critical bugs. Matej Cepl, James Laska, Jesse Keating, and John Poelstra contributed opinions. In the end it was agreed that the basic shape of the current process is a good one but the groups involved - BugZappers, release engineering, and developers - should communicate and collaborate more in deciding on release-critical bugs.

Xorg/Mesa/DRI testing

François Cami, together with others, proposed a project[1] to conduct organized testing of X.org and DRI functionality with a range of common hardware for Fedora 11. He highlighted four important areas he felt were needed for this: an opt-in system to record what hardware is owned by what testers (possibly utilizing Smolt), a system for producing test plans, a system for recording the results of tests, and regularly scheduled test sessions. Jóhann Guðmundsson supported the idea[2] and suggested that, while some of the features would require help from the infrastructure group, the QA group could at least immediately start writing test cases. James Laska pointed out that extensive information is needed to diagnose and fix X issues remotely. François will work with the X maintainers to define exactly what information needs to be provided.