QualityAssurance
In this section, we cover the activities of the QA team[1]. It seems like the new layout has been a success, so we'll stick with it for the future.
Contributing Writer: Adam Williamson
Test Days
We had two Test Days last week. The first[1], on Tuesday 2010-03-30, was on the implementation of SSSD by default[2]. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. A small group of dedicated testers were able to expose five bugs, which the developers are now investigating. The second[3] was on ABRT[4], the automated bug report tool which has been included with Fedora by default since the release of Fedora 12. This event resulted in mostly positive test results, but also exposed six bugs, three of which have already been closed by the developers.
This week's Test Day[5], on Thursday 2010-04-08, will be on virtualization[6]. This is mainly focused on the Fedora virtualization stack, based around KVM, libvirt, and virt-manager. There've been many improvements throughout the stack for Fedora 13, so there's a lot of new stuff to test as well as making sure the basic functions are working properly. Virtualization is a very important area these days, so please come out to help us test it! The event will take place all day in the #fedora-test-day channel on Freenode IRC. If you can't make it on the day, you can still provide your results on the Wiki page before or after the event.
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[7].
- ↑ http://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault
- ↑ http://fedoraproject.org/wiki/Features/SSSDByDefault
- ↑ http://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT
- ↑ http://fedoraproject.org/wiki/Features/ABRT
- ↑ http://fedoraproject.org/wiki/Test_Day:2010-04-08_Virtualization
- ↑ http://fedoraproject.org/wiki/Virtualization
- ↑ http://fedorahosted.org/fedora-qa/
Fedora 13 testing
Once again, the week was occupied with much testing of Fedora 13 Beta candidate builds. The second release candidate was announced[1] on Wednesday 2010-03-31, and closely followed by the third release candidate on the same day[2]. As usual, Andre Robatino provided delta ISOs[3]. Installation validation testing on RC3[4] revealed a blocker bug in support for encrypted partitions[5]. This led the group, along with release engineering and development groups, to take the decision to delay the Beta release by a week[6].
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089807.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089826.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-April/089833.html
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC3_Install
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=578633
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-April/089828.html
Update acceptance testing
Adam Miller revised his proventesters SOP proposal[1] based on feedback received from Adam Williamson[2] and Jesse Keating[3].
Stock response for ABRT symbol failures
Christopher Beland proposed[1] a BugZappers stock response for the situation where ABRT fails to download the packages to provide debugging symbols in an automatically-generated bug report. After receiving no objections, he later reported[2] that he had added this to the page[3].
BugZapping classes
During the weekly BugZappers meeting[1], the group discussed the possibility of providing more ways for new members to get started. Chris Campbell volunteered to look into the possibility of running a test Bugzapping class. Shakthi Kannan suggested creating screencasts as examples of each step in the triage process, and Adam Williamson said he would forward this idea to the mailing list.