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
Internationalization and localization test week was ongoing during the week - there will be a full report next week. There were three test days: desktop localization on Tuesday 2011-08-30[1], localization and internationalization in the installer on Wednesday 2011-08-31[2], and desktop internationalization on Thursday 2011-09-01[3].
Next week will be Graphics Test Week - yes, it's time to make sure the graphics drivers are in shape for Fedora 16! Tuesday 2011-09-06 will be Nouveau Test Day[4], Wednesday 2011-09-07 will be Radeon Test Day[5], and Thursday 2011-09-08 will be Intel graphics Test Day[6]. As always we need to check up and make sure there are no big problems in graphics card support, check on progress since the last day, and ensure 3D support is in good shape for GNOME Shell. If you have an NVIDIA, AMD or Intel graphics card - and that's more than 95% of you! - please come along and help out.
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-08-30_L10n_Desktop
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-08-31_L10n_I18n_Installation
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-01_I18n_Desktop
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon
- ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-08_Intel
Fedora 16 Alpha preparation
Following the previous week's slip, Fedora 16 Alpha RC4 arrived on 2011-08-15[1]. Two more blocker bugs[2] [3] were quickly discovered in the new build, and Alpha RC5 promptly followed it on 2011-08-16[4]. The team put in a heroic effort to complete Alpha validation testing on RC5 in less than 24 hours, with the installation[5], base [6] and desktop [7] matrices all filled out. As the testing exposed no further blocker bugs, the QA team was able to report that RC5 met the release requirements at the Go / No-Go meeting of 2011-08-17[8], and the release was declared gold.
Masami Ichikawa noticed that some libreport packages were missing from the Alpha Xfce and LXDE live images, which stopped abrt and sealert from being able to report bugs on these live images[9]. Kevin Fenzi reported that he had fixed the problem post-Alpha[10].
- ↑ http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000266.html
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=730863
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=730887
- ↑ http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000268.html
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Install
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Base
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Desktop
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-08-17/f16_alpha_gono-go_meeting_%232.2011-08-17-21.05.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101912.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/102002.html
Test compose extension for Fedora 16 Beta
At the weekly meeting of 2011-08-22[1], John Dulaney suggested starting the release validation period for Fedora 16 Beta earlier by producing the first test compose (a full build of the live and install image set that makes up a (pre-)release, but which happens ahead of the freeze date for the next (pre-)release and hence cannot possibly be validated as the (pre-)release image set) ahead of schedule. Adam Williamson had been thinking along the same lines, and suggested replacing the "Pre-Beta Acceptance Test Plan" milestone with an earlier TC1 compose. The group was generally in favor of the idea. Later, Adam and John were able to obtain the agreement of the installer and release engineering teams.
Release criteria updates
Adam Williamson reported that he had committed his proposed modifications to the firstboot release criteria and validation tests (see FWN #284)[1]. Adam also made two alternate proposals for refining how the criteria apply to installations to EFI systems[2]. Peter Robinson[3] and Jurgen Kramer[4] generally agreed with the idea of promoting the importance of EFI installations.
Adam also kicked off a discussion about kickstart release criteria[5]. Stephen Smoogen suggested a minimal criterion could be "Does it take a minimal kickstart and build a default system. The minimal being the exact stuff that would be created if a person just clicked through a release."[6].
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101916.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101939.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101942.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101944.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/102052.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/102163.html
Explaining the need for a BIOS boot partition during installation
Tom Horsley questioned whether the Fedora 16 installer's message explaining the need for a BIOS boot partition when booting from BIOS (rather than EFI) using a drive with a GPT disk label was understandable[1]. Adam Williamson wasn't sure the installer was the right place for a detailed explanation of GPT issues[2], but Scott Robbins[3] and Rahul Sundaram[4] agreed with Tom. Rahul suggested filing a bug requesting the message be improved.
Fedora 16 in boot.fedoraproject.org
"Tony" reported that there was no Fedora 16 option available at http://boot.fedoraproject.org[1]. Kevin Fenzi apologized for the oversight and said he had added it to the menu[2]. Tony responded to say that things were working great[3].