QualityAssurance
In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].
Contributing Writer: Adam Williamson
Test Days
A special Test Day[1] was held on Wednesday 2011-06-08 for World IPv6 Day[2], thanks to Linda Wang. Despite the complexity involved in implementing an IPv6 setup for testing, a good group of testers were able to run through the various tests and identify some bugs which have already received developer attention.
The Fedora 15 Test Day track is now finished, and the main Fedora 16 Test Day track has not yet started. If you would like to propose a main track Test Day for the Fedora 16 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[3].
Security spin testing
Athmane Madjoudj announced some testing he had done on the Fedora 15 security spin[1]. Adam Williamson thanked him and asked if he had contacted the security spin authors about it[2], and Athmane replied that he would. Later, Athmane announced that he had added some more tests[3], and Adam suggested writing them up as test cases[4]. Athmane did this[5], and then continued to add more test cases regularly. In the course of this work, Athmane noticed and helped to address some problems with the rendering of tags and templates in the wiki[6] [7].
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-May/100484.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-May/100485.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-May/100496.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-May/100497.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-May/100511.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-June/100668.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-June/100763.html
Release criteria revisions
Adam Williamson continued with revisions of the release criteria. He announced that the wording 'release-blocking desktops' to describe the desktops that are capable of blocking release had been generally well received, so he had updated the criteria to use this wording[1].
Installer validation test revisions
Rui He reported that she had refined the various installation source tests that form part of the installation validation matrix by creating some new tests and renaming and adjusting others[1]. James Laska followed up with some questions and comments[2], and Rui He continued with further improvements.
Overly similar application names
Vitezslav Humpa started a discussion and made some proposals around the issue of applications with very similar names and icons in the system menus[1]. This resulted in an active and productive debate across several teams about the best way to move forward in addressing the problem. In the end it was agreed that it would be best and fastest to work on a case-by-case basis through the most commonly-encountered name collisions.
Draft btrfs test case
John Dulaney announced that he had been working on a btrfs test case in advance of Fedora 16, where it is likely to be the default filesystem, and that he had a draft available for review[1]. Rui He, Rahul Sundaram and JB replied with comments and suggestions.
Fedora 15 QA retrospective
James Laska announced that he had completed the Fedora 15 QA retrospective wiki page, and drafted a set of recommendations for review by the group. He asked for feedback on the retrospective and the recommendations[1].
AutoQA
There were two big AutoQA developments since the last newsletter. One was the so-called 'pretty patch', which improved the layout and legibility of AutoQA results, particularly the dependency check test. It was submitted to the mailing list on 2011-06-06[1] by Kamil Paral and pushed on 2011-06-10[2]. The other was a patch from Tim Flink to reduce the volume of messages sent out by AutoQA, notably by not sending emails to maintainers when the tests are entirely successful. This patch was submitted on 2011-06-06[3] and merged on 2011-06-09[4].