From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 23:38, 20 February 2009 by Adamwill (talk | contribs) (fwn #164 qa beat draft 1)


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 20 Second Startup[2]. 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.

Next week's test day[3] will be on the Crash Catcher[4] 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!

Weekly meetings

The QA group weekly meeting[1] was held on February 18th. 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. 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). Adam Williamson, James Laska and 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[4] 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 Bugzappers group weekly meeting[5] was held on February 17th. The full log is available[6]. 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 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.

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

Wiki re-organization

Adam Williamson announced[1] 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.

Reporting bugs to Bugzilla

Christopher Beland encouraged[1] 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. Adam Williamson suggested[2] that the text might be better placed on the Wiki page about how properly to report bugs, rather than the QA group front page.

Semantic - test reporting plugin for Mediawiki

James Laska sent in a report[1] on Semantic, the project's Mediawiki extension for managing test reports.

Encouraging Rawhide testing

Mark McLoughlin made some suggestions[1] 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.