From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 223 qa beat)
(create fwn 225 qa beat)
Line 8: Line 8:
<references/>
<references/>


=== Test Days ===
=== Fedora 13 testing ===
 
Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-22_StorageFiltering</ref> was on Anaconda (the Fedora installer)'s storage support<ref>http://fedoraproject.org/wiki/Anaconda/Features/StorageFiltering</ref>. The turnout was unfortunately low, perhaps due to the hardware requirements for testing, but nevertheless the few testers present managed to expose four bugs.
 
This week will see the final two Test Days of the Fedora 13 cycle. First up is Preupgrade Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-29_Preupgrade</ref> on Thursday 2010-04-29, followed by Xfce Test Day<ref>http://fedoraproject.org/wiki/Test_Day:XFCE_F13_20100430</ref> on Friday 2010-04-30.


These are two juicy topics: preupgrade<ref>http://fedoraproject.org/wiki/How_to_use_PreUpgrade</ref> is the recommended method for upgrading from one Fedora release to the next, and Xfce is one of the most popular 'alternate' Linux desktops, and has a very dedicated Fedora SIG<ref>http://fedoraproject.org/wiki/Xfce</ref> which works hard to provide a smooth experience and live spin, and has organized the Test Day to make sure the Fedora 13 Xfce experience is second to none.
The QA group has spent the last two weeks almost entirely engaged in Fedora 13 testing, with the release cycle nearing its end. Testing of the test compose (TC1) began on 2010-04-29<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090520.html</ref>, with as usual installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_TC1_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_TC1_Desktop</ref> validation tests.  


As always, the Test Days will run all day in the #fedora-test-day channel on Freenode IRC. If you're not sure about IRC, read the guide or use WebIRC<ref>http://webchat.freenode.net/?channels=fedora-test-day</ref>. If you can't do the testing on the Test Day, you can still run through the tests and provide your results earlier or later. You can do the Xfce testing with a live image which will be provided on the Test Day page. Obviously this isn't possible for the preupgrade testing, but you can test it in a virtual machine if you don't want to (or can't) mess with your real Fedora installation.
Thanks to this testing and also more general long-term Fedora 13 use, a large pool of release blocking bugs built up, with over 60 release blocking bugs needing to be addressed before final release could be considered. At the regular blocker bug review meetings, the group - along with the development and release engineering groups - gradually tackled this set of bugs until the list was eventually cleared for the RC1 release<ref>http://lists.fedoraproject.org/pipermail/test/2010-May/090707.html</ref> on 2010-05-07, only a day behind the planned schedule.  


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<ref>http://fedorahosted.org/fedora-qa/</ref>.
RC1 testing - installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC1_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC1_Desktop</ref> - was generally positive, but two issues led to the release of a minimally-changed RC2<ref>http://lists.fedoraproject.org/pipermail/test/2010-May/090721.html</ref>. RC2 installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC2_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC2_Desktop</ref> testing was again mostly positive, but identified a bug<ref>http://bugzilla.redhat.com/show_bug.cgi?id=590640</ref> with NFS installation, which at the 2010-05-12 go/no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-05-12/f-13-readiness.2010-05-12-00.00.html</ref> was agreed to be potentially significant enough to delay the final release. The slip was announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-May/090881.html</ref> on 2010-05-12; a RC3 build will now be provided by the release engineering team for QA testing during the next few days and, we hope, validation for release on 2010-05-25.


<references/>
<references/>


=== Update acceptance testing ===
=== Test Days ===
 
At the weekly QA meeting<ref>http://fedoraproject.org/wiki/QA/Meetings/20100419</ref>, [[User:maxamillion|Adam Miller]] asked if a vote would be needed to move ahead with the proventesters policy he was drafting. [[User:Adamwill|Adam Williamson]] said votes were not normally needed and suggested just sending a final draft to the mailing list with a note that it would go into effect if there were no major objections. Adam Miller subsequently sent the final draft to the list<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090252.html</ref>, where Adam Williamson<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090257.html</ref>, [[ShmuelSiegel|Shmuel Siegel]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090260.html</ref> and others suggested small amendments, which Adam Miller accepted<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090288.html</ref>.
 
[[User:Kparal|Kamil Paral]] reported that the package update acceptance test plan<ref>http://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan</ref> could be completed before the end of the Fedora 13 cycle, for automation and implementation in the Fedora 14 cycle. Kamil later posted a final call for comments<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090287.html</ref> on the plan, to which [[User:Jlaska|James Laska]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090313.html</ref> and [[User:jkeating|Jesse Keating]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090317.html</ref> provided detailed responses.
 
<references/>
 
=== Remote accessibility release criterion proposal ===
 
[[User:Adamwill|Adam Williamson]] proposed<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090255.html</ref> a new release criterion stating that it must be possible to install a system in such a way that it is immediately remotely accessible. This was in response to reports on the list that it was not possible to do this in Fedora 13, in contrast to previous releases, which was causing sysadmins dealing with remote machines some problems.
 
<references/>
 
=== Fedora 11 end-of-life notification ===
 
[[User:Poelstra|John Poelstra]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090326.html</ref> that he would soon send out the end-of-life notification for Fedora 11 on bugs reported against that release. [[User:tibbs|Jason Tibbitts]] noted<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090328.html</ref> that he had adjusted open package review requests filed against that release, so these would not erroneously receive notifications.
 
<references/>
 
=== Fedora 13 testing ===
 
This week saw the second blocker bug review meeting<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2010-04-23/fedora-bugzappers.2010-04-23-16.06.log.html</ref> for the final release. The group reviewed all open blocker bugs with assistance from the development team; in general, progress is being made on all blockers and we don't foresee any major problems resolving them in time for release.
 
Al Dunsmuir reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090238.html</ref> a crash in Firefox with the common Noscript extension when browsing the release notes, which he filed as a bug<ref>http://bugzilla.redhat.com/show_bug.cgi?id=583826</ref>.


Joachim Backes reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090330.html</ref> a problem booting to runlevel 3 with the echoing of login information: he had seen cases where the username was not echoed back to the screen when typed, but the password was (obviously, the behavior should be opposite). Steven I Usdansky confirmed<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090335.html</ref> that he had seen a similar issue.
The final two Test Days of the Fedora 13 release cycle were Preupgrade Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-29_Preupgrade</ref> on Thursday 2010-04-29, followed by Xfce Test Day<ref>http://fedoraproject.org/wiki/Test_Day:XFCE_F13_20100430</ref> on Friday 2010-04-30. [[User:Rhe|Rui He]] provided a recap<ref>http://lists.fedoraproject.org/pipermail/test/2010-May/090657.html</ref> of the preupgrade Test Day, reporting that "many bugs/problems were found out in different conditions during preupgrading." Only one dedicated Xfce enthusiast - thank you, Nathan! - provided a full set of Xfce test results, but these indicated that everything was working correctly.


<references/>
<references/>

Revision as of 22:59, 12 May 2010

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

Fedora 13 testing

The QA group has spent the last two weeks almost entirely engaged in Fedora 13 testing, with the release cycle nearing its end. Testing of the test compose (TC1) began on 2010-04-29[1], with as usual installation[2] and desktop[3] validation tests.

Thanks to this testing and also more general long-term Fedora 13 use, a large pool of release blocking bugs built up, with over 60 release blocking bugs needing to be addressed before final release could be considered. At the regular blocker bug review meetings, the group - along with the development and release engineering groups - gradually tackled this set of bugs until the list was eventually cleared for the RC1 release[4] on 2010-05-07, only a day behind the planned schedule.

RC1 testing - installation[5] and desktop[6] - was generally positive, but two issues led to the release of a minimally-changed RC2[7]. RC2 installation[8] and desktop[9] testing was again mostly positive, but identified a bug[10] with NFS installation, which at the 2010-05-12 go/no-go meeting[11] was agreed to be potentially significant enough to delay the final release. The slip was announced[12] on 2010-05-12; a RC3 build will now be provided by the release engineering team for QA testing during the next few days and, we hope, validation for release on 2010-05-25.

Test Days

The final two Test Days of the Fedora 13 release cycle were Preupgrade Test Day[1] on Thursday 2010-04-29, followed by Xfce Test Day[2] on Friday 2010-04-30. Rui He provided a recap[3] of the preupgrade Test Day, reporting that "many bugs/problems were found out in different conditions during preupgrading." Only one dedicated Xfce enthusiast - thank you, Nathan! - provided a full set of Xfce test results, but these indicated that everything was working correctly.