From Fedora Project Wiki

< FWN‎ | Beats

(standardize dates)
(initial draft of QA section for FWN #165)
Line 10: Line 10:
 
=== Test Days ===
 
=== Test Days ===
  
This week's regular test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-02-19</ref> was on 20 Second Startup<ref>http://fedoraproject.org/wiki/Features/20SecondStartup</ref>. [[User:Harald|Harald Hoyer]] was the developer present, and there was a great turnout of 20 people contributing test results. Further results are still welcome from anyone - a full set of instructions for running tests is available on the Wiki page. As a result of the testing, Harald has made several modifications already that will help to optimize boot times for Fedora 11.
+
This week's regular test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-02-26</ref> was on CrashCatcher<ref>http://fedoraproject.org/wiki/Features/CrashCatcher</ref>. [[User:Zprikryl|Zdenek Prikryl]] and [[User:Jmoskovc]] were the developers present. Further results are still welcome from anyone - a full set of instructions for running tests is available on the Wiki page. As a result of the testing, over thirty issues were discovered and filed in the CrashCatcher trac system <ref>https://fedorahosted.org/crash-catcher</ref>.
  
Next week's test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-02-26</ref> will be on the Crash Catcher<ref>http://fedoraproject.org/wiki/Features/CrashCatcher</ref> feature planned for Fedora 11, which aims to make it easy for non-power uses to file useful reports when an application crashes. It will be held on Thursday (2009-02-26) in the #fedora-qa channel on Freenode IRC. Please drop by if you would like to help test this important new feature for Fedora 11 - no special equipment or expertise required!
+
Next week's test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-05</ref> will be on Anaconda's (the Fedora installer) interaction with block devices - especially RAID, LVM and encrypted devices. It will be held on Thursday (2009-03-05) in the #fedora-qa channel on Freenode IRC. Please drop by if you would like to help test this this area of Fedora.
  
 
<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 2009-02-18. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090218.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. The group agreed to create an autoqa component in the fedora-qa trac instance, and create a new mailing list for autoqa reports to be sent to (this will not be a discussion list). [[User:Adamwill|Adam Williamson]], [[User:Jlaska|James Laska]] and [[User:Johannbg|Jóhann Guðmundsson]] then initiated a discussion about creating a short-term solution for more organized reporting and collection of test results. Follow up a mailing list discussion, a system created by the Laptop.org<ref>http://www.laptop.org</ref> project, implemented as a Mediawiki plugin, was discussed. The group agreed that it seemed suited to the purpose, and James will propose it to the Infrastructure group, to see if they approve of the system, and whether they would prefer it to be added to the main Wiki or a special-purpose Wiki instance created just for this use. Finally, the group discussed the (then) upcoming test day, and agreed preparations were well in hand.
+
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-02-25. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090225.log.html</ref>. [[User:Jwboyer|Josh Boyer]] reported epic news: the PPC build of Rawhide can now be successfully installed. [[User:Wwoods|Will Woods]] suggested that now is a good time to start putting bugs on to the tracker bug for the release of Fedora 11 Beta<ref>https://bugzilla.redhat.com/show_bug.cgi?id=F11Beta</ref>. He also pointed out the tracker bug for Intel KMS-related issues<ref>https://bugzilla.redhat.com/show_bug.cgi?id=F11IntelKMS</ref>. [[User:Adamwill|Adam Williamson]] volunteered to organize a test day for the proposed new default NVIDIA driver, nouveau.
  
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-02-17. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Feb-17</ref>. A broad initial goal for the Bugzappers project was agreed: to stabilize the number of bugs in NEW (i.e. un-triaged) status on the components previously agreed to be the most significant. Brennan Ashton's metric reporting tool will be used to track this. Brennan demonstrated the current state of his tool on a small set of test data, to general approval. The group voted on [[User:Adamwill|Adam Williamson's]] proposal to have a stock signature appended to comments by members of the Bugzappers team in Bugzilla, both to identify the Bugzappers and to increase the visibility of the project. This was approved, and Matej Cepl will implement it using Greasemonkey, adding it to the Greasemonkey script already used by most Bugzappers.
+
[[User:Wwoods|Will Woods]] and [[User:jkeating|Jesse Keating]] discussed the progress of the autoqa system. Jesse would like to have more refined results output available soon, and a working example of a post tree-compose sanity test. [[User:Wwoods|Will Woods]] wants to aim to have a working verifytree test available by Fedora 11 Beta release.
  
The next QA weekly meeting will be held on 2009-02-25 at 1600 UTC in #fedora-qa, and the next Bugzappers weekly meeting on 2009-02-24 at 1700 UTC in #fedora-bugzappers.
+
[[User:Jlaska|James Laska]] gave a progress update on the Nitrate<ref>http://fedorahosted.org/nitrate</ref> test case management system, mostly on working with the developers of the internal Red Hat system to get the code publicly available. He also promised to get around to proposing the Semantic system developed by the Laptop.org project (also discussed in last week's meeting) to the Infrastructure group this week.
 +
 
 +
[[User:Wwoods|Will Woods]] pointed out the Fedora 11 feature list<ref>http://fedoraproject.org/wiki/Releases/11/FeatureList</ref> and explained that the QA team must ensure, by feature freeze, that all accepted features have a workable test process. He asked for the group's help in ensuring that all proposed features are checked for this and a useful test plan is drawn up where possible. [[User:Adamwill|Adam Williamson]] volunteered to liaise with the developers of the Nouveau<ref>http://fedoraproject.org/wiki/Features/NouveauAsDefault</ref> and automatic font / MIME installer<ref>http://fedoraproject.org/wiki/Features/AutoFontsAndMimeInstaller</ref> features.
 +
 
 +
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-02-24. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Feb-24</ref>. There was some more discussion of goals for the group, and the group agreed with [[User:Beland|Christopher Beland's]] suggestion that the targetted components page<ref>https://fedoraproject.org/wiki/BugZappers/components</ref> be updated to list the number of NEW bugs for each component.
 +
 
 +
[[User:Mcepl|Matej Cepl]] provided the new Greasemonkey script to add a standard signature to each comment posted by a Bugzapper group member<ref>http://mcepl.fedorapeople.org/scripts/greasemonkey/add_bugzappers_signature.user.js</ref>. [[User:Poelstra|John Poelstra]] wanted to have a single location for all necessary Greasemonkey scripts for triagers. Brennan Ashton reported that he is working on an RPM package which would contain Greasemonkey and the scripts.
 +
 
 +
[[User:Adamwill|Adam Williamson]] volunteered to organize a new series of triage days, to get the whole group together to work on triaging and training new members. Matej stated that he is happy to help mentor new triagers by email or IRC at any time.
 +
 
 +
The next QA weekly meeting will be held on 2009-03-04 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-03 at 1700 UTC in #fedora-meeting.
 +
 
 +
<references/>
 +
 
 +
=== Goals ===
 +
 
 +
[[User:Beland|Christopher Beland]] wrapped up the discussion on group goals<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01011.html</ref>. "The official goal is now to stabilize the number of NEW bugs for each key component.  Counts from today have been copied into that page on the wiki<ref>https://fedoraproject.org/wiki/BugZappers/components</ref>, and there's a preformatted query from which you can get the current count."
  
 
<references/>
 
<references/>
  
=== Wiki re-organization ===
+
=== Bugs filed against default component ===
  
[[User:Adamwill|Adam Williamson]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00710.html</ref> that the first phase of the Wiki re-organization project was complete, with the new front page and 'how to join in' page for the QA Wiki space put into place.
+
Lex Hider pointed out<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01038.html</ref> that the 0xFFFF component in Bugzilla gets many reports simply because it is the first component in the list. He reported that he has tried to clean up all the current reports against this component, and suggested creating a new component, owned by the Bugzappers group, to catch this problem in future.
  
 
<references/>
 
<references/>
  
=== Reporting bugs to Bugzilla ===
+
=== QA review for feature pages ===
  
[[User:Beland|Christopher Beland]] encouraged<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00837.html</ref> testers to report bugs to Bugzilla as well as sending a mail about them to the test-list mailing list, and told the group that he had added some text to this effect to the QA group front page on the Wiki. [[User:Adamwill|Adam Williamson]] suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00844.html</ref> that the text might be better placed on the Wiki page about how properly to report bugs, rather than the QA group front page.
+
[[User:Wwoods|Will Woods]] asked the group<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01075.html</ref> to work on reviewing the feature pages for Fedora 11, and help make sure they all have viable test procedures, as previously discussed at the weekly meeting. He later emphasized<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01090.html</ref> that the aim is actively to help the development team produce viable test plans, not simply to reject or mark the features which do not yet have them.
  
 
<references/>
 
<references/>
  
=== Semantic - test reporting plugin for Mediawiki ===
+
=== Improving Bugzappers documentation for beginners ===
  
[[User:Jlaska|James Laska]] sent in a report<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00756.html</ref> on Semantic, the Laptop.org project's Mediawiki extension for managing test reports.
+
A new group member, Hunter Bukowski, agreed<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01138.html</ref> with previous suggestions that the current Bugzappers documentation in the Wiki is not sufficient in quantity or organization to allow new Bugzappers to get started without other references. He volunteered to help improve this situation.
  
 
<references/>
 
<references/>
  
=== Encouraging Rawhide testing ===
+
=== The CLA for Bugzappers ===
  
[[MarkMcLoughlin|Mark McLoughlin]] made some suggestions<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00846.html</ref> about how to improve the ongoing quality and consistency of Rawhide, in order to make it possible for more people to test it. He suggested that a definition should be made of what should be expected to work in Rawhide all the time - e.g. basic installation, booting, network and a few core applications - and a RawhideBlocker tracker bug be created on Bugzilla to track bugs in Rawhide which breaks any of these functions, with the intention that those bugs be addressed as a matter of high priority.
+
A new volunteer, Lalit Dhiri, introduced himself<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg00912.html</ref> and tried to join the FAS group for the Bugzappers team. [[User:Sundaram|Rahul Sundaram]] rejected his application, as he had not yet signed the CLA - the legal agreement all Fedora contributors are required to sign. Upon further discussion, it was agreed by [[User:Pfrields|Paul Frields]] and [[TomCallaway|Tom 'spot' Callaway]] that signing the CLA should not be required for Bugzappers, as none of the work normally required in the Bugzappers group constitutes a 'contribution' to Fedora in this sense. The requirement for Bugzappers to sign the CLA was officially removed.
  
 
<references/>
 
<references/>

Revision as of 03:31, 28 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 CrashCatcher[2]. Zdenek Prikryl and User:Jmoskovc were the developers present. Further results are still welcome from anyone - a full set of instructions for running tests is available on the Wiki page. As a result of the testing, over thirty issues were discovered and filed in the CrashCatcher trac system [3].

Next week's test day[4] will be on Anaconda's (the Fedora installer) interaction with block devices - especially RAID, LVM and encrypted devices. It will be held on Thursday (2009-03-05) in the #fedora-qa channel on Freenode IRC. Please drop by if you would like to help test this this area of Fedora.

Weekly meetings

The QA group weekly meeting[1] was held on 2009-02-25. The full log is available[2]. Josh Boyer reported epic news: the PPC build of Rawhide can now be successfully installed. Will Woods suggested that now is a good time to start putting bugs on to the tracker bug for the release of Fedora 11 Beta[3]. He also pointed out the tracker bug for Intel KMS-related issues[4]. Adam Williamson volunteered to organize a test day for the proposed new default NVIDIA driver, nouveau.

Will Woods and Jesse Keating discussed the progress of the autoqa system. Jesse would like to have more refined results output available soon, and a working example of a post tree-compose sanity test. Will Woods wants to aim to have a working verifytree test available by Fedora 11 Beta release.

James Laska gave a progress update on the Nitrate[5] test case management system, mostly on working with the developers of the internal Red Hat system to get the code publicly available. He also promised to get around to proposing the Semantic system developed by the Laptop.org project (also discussed in last week's meeting) to the Infrastructure group this week.

Will Woods pointed out the Fedora 11 feature list[6] and explained that the QA team must ensure, by feature freeze, that all accepted features have a workable test process. He asked for the group's help in ensuring that all proposed features are checked for this and a useful test plan is drawn up where possible. Adam Williamson volunteered to liaise with the developers of the Nouveau[7] and automatic font / MIME installer[8] features.

The Bugzappers group weekly meeting[9] was held on 2009-02-24. The full log is available[10]. There was some more discussion of goals for the group, and the group agreed with Christopher Beland's suggestion that the targetted components page[11] be updated to list the number of NEW bugs for each component.

Matej Cepl provided the new Greasemonkey script to add a standard signature to each comment posted by a Bugzapper group member[12]. John Poelstra wanted to have a single location for all necessary Greasemonkey scripts for triagers. Brennan Ashton reported that he is working on an RPM package which would contain Greasemonkey and the scripts.

Adam Williamson volunteered to organize a new series of triage days, to get the whole group together to work on triaging and training new members. Matej stated that he is happy to help mentor new triagers by email or IRC at any time.

The next QA weekly meeting will be held on 2009-03-04 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-03 at 1700 UTC in #fedora-meeting.

Goals

Christopher Beland wrapped up the discussion on group goals[1]. "The official goal is now to stabilize the number of NEW bugs for each key component. Counts from today have been copied into that page on the wiki[2], and there's a preformatted query from which you can get the current count."

Bugs filed against default component

Lex Hider pointed out[1] that the 0xFFFF component in Bugzilla gets many reports simply because it is the first component in the list. He reported that he has tried to clean up all the current reports against this component, and suggested creating a new component, owned by the Bugzappers group, to catch this problem in future.

QA review for feature pages

Will Woods asked the group[1] to work on reviewing the feature pages for Fedora 11, and help make sure they all have viable test procedures, as previously discussed at the weekly meeting. He later emphasized[2] that the aim is actively to help the development team produce viable test plans, not simply to reject or mark the features which do not yet have them.

Improving Bugzappers documentation for beginners

A new group member, Hunter Bukowski, agreed[1] with previous suggestions that the current Bugzappers documentation in the Wiki is not sufficient in quantity or organization to allow new Bugzappers to get started without other references. He volunteered to help improve this situation.

The CLA for Bugzappers

A new volunteer, Lalit Dhiri, introduced himself[1] and tried to join the FAS group for the Bugzappers team. Rahul Sundaram rejected his application, as he had not yet signed the CLA - the legal agreement all Fedora contributors are required to sign. Upon further discussion, it was agreed by Paul Frields and Tom 'spot' Callaway that signing the CLA should not be required for Bugzappers, as none of the work normally required in the Bugzappers group constitutes a 'contribution' to Fedora in this sense. The requirement for Bugzappers to sign the CLA was officially removed.