From Fedora Project Wiki

< FWN‎ | Beats

(fix an https)
(create fwn 271 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Thursday 2011-03-24 was power management Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-03-24</ref>. The event produced a great turnout of testers who provided results on a wide range of hardware, and the developers are already looking at the bugs filed. Thanks to everyone who came out to help.
Thursday 2011-03-31 was ABRT Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-03-31_ABRT_Retrace_Server</ref>. As well as checking that ABRT (Fedora's automated crash report tool) is working as expected for Fedora 15, we tested out a big new feature, the retrace server<ref>http://fedoraproject.org/wiki/Features/RetraceServer</ref>. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download and install often large debuginfo packages in order to submit reports. [[User:Mnowak|Michal Nowak]] posted a recap<ref>http://lists.fedoraproject.org/pipermail/test-announce/2011-April/000224.html</ref> of the event, noting that there had been eight testers and seventeen bugs filed overall.


This Tuesday, 2011-03-29, was printing Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-03-29</ref>. The turnout was a little smaller than we hoped, but the testers who did come managed to find lots of bugs, and Fedora's printing maintainer, Tim Waugh, was very happy with all the results.
This Thursday, 2011-04-14, will be virtualization Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization</ref>, where our awesome virtualization team, starring Justin Forbes<ref>http://jforbes.livejournal.com</ref>, will be our guides as we test the various virtualization features of Fedora 15, including shiny SPICE support in virt-manager<ref>http://fedoraproject.org/wiki/Features/SpiceInVirtManager</ref>. Virtualization is a key component of any distribution nowadays, and the virtualization team always put on a smoothly run event, so please come along and help us test!
 
This Thursday, 2011-03-31, will be ABRT Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-03-31_ABRT_Retrace_Server</ref>. As well as checking that ABRT (Fedora's automated crash report tool) is working as expected for Fedora 15, we'll be testing out a big new feature, the retrace server<ref>http://fedoraproject.org/wiki/Features/RetraceServer</ref>. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download and install often large debuginfo packages in order to submit reports. Please come along and help us test this exciting new feature!
 
There is currently no Test Day planned for next Thursday, 2011-04-07. Take the day off!


<references/>
<references/>


=== Anaconda testing ===
=== Fedora 15 Beta preparation ===


[[User:Jlaska|James Laska]] requested testing of an installer image which included updated versions of anaconda and lorax that needed testing before being approved as stable updates<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098018.html</ref>. Several testers responded, and the updates were soon approved.
Preparation for the Fedora 15 Beta release moved into high gear over the last couple of weeks, with two more blocker review meetings<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-01/f-15-beta-blocker.2011-04-01-17.00.html</ref> <ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-08/f-15-beta-blocker-review.2011-04-08-17.00.html</ref> and the TC1<ref>http://lists.fedoraproject.org/pipermail/test-announce/2011-March/000215.html</ref>, RC1<ref>http://lists.fedoraproject.org/pipermail/test-announce/2011-April/000220.html</ref> and RC2<ref>http://lists.fedoraproject.org/pipermail/test-announce/2011-April/000221.html</ref> releases. Many testers made valuable contributions to the desktop and installation validation testing processes for each of these releases, and we were able to achieve comprehensive test coverage, and identify several blocker issues for the development team to fix. The group was able to catch SELinux issues caused by the introduction of the /run directory<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098444.html</ref> very early and ensure the change did not land in the 'stable' Fedora 15 repository until this was resolved, and did not affect the Beta release.


<references/>
<references/>


=== GNOME Tweak Tool testing ===
=== Systemd and GNOME Shell documentation ===


[[User:Salimma|Michel Salim]] announced that GNOME Tweak Tool, an application for tweaking various advanced settings in GNOME 3, was now available for testing<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098107.html</ref>. Several group members thanked Michel for the announcement and provided feedback on the tool.
[[User:Sundaram|Rahul Sundaram]] posted some documentation on Systemd<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098234.html</ref> and GNOME Shell<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098246.html</ref>. Both posts led to some lively discussion and suggested improvements.


<references/>
<references/>


=== Fedora 15 Beta preparation ===
=== Release criteria revisions ===
 
[[User:Adamwill|Adam Williamson]] announced his intention to push various recently discussed release criteria revisions into production<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098288.html</ref>, and later announced that he had done so<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098365.html</ref>. In the meantime, a discussion developed on how to capture the fact that some desktops can block the release and some cannot in a clear yet future-proof way, with another proposal from Adam<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098303.html</ref> and some well-considered reservations<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098315.html</ref> from [[User:Johannbg|Jóhann Guðmundsson]].


The third Beta blocker/nice-to-have review meeting took place on 2011-03-25<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2011-03-25/f-15-beta-blocker.2011-03-25-16.59.html</ref>, and the team worked through the full list of proposed Beta blocker and nice-to-have bugs. The first test compose was scheduled for Tuesday 2011-03-22, but could not be completed on that day due to various outstanding bugs and the lack of the planned NetworkManager 0.9 packages. At a special release schedule meeting on Wednesday 2011-03-23<ref>http://meetbot.fedoraproject.org/fedora-meeting/2011-03-23/fedora-meeting.2011-03-23-19.30.html</ref>, the QA and release engineering teams, and the Fedora Project Leader, agreed that the late arrival of NetworkManager 0.9 justified a one week slip in the release schedule. The first test compose was then set for Tuesday 2011-03-29.
[[User:Bruno|Bruno Wolff]] suggested criteria for image sizes<ref>http://lists.fedoraproject.org/pipermail/test/2011-April/098764.html</ref>, to ensure that images at each release point are of an appropriate size for convenient testing. Adam provided a proposed wording<ref>http://lists.fedoraproject.org/pipermail/test/2011-April/098811.html</ref>. [[User:Ausil|Dennis Gilmore]] pointed out that the sources DVD should probably be exempt from the criterion<ref>http://lists.fedoraproject.org/pipermail/test/2011-April/098817.html</ref>, at least until final release time.


<references/>
<references/>


=== Improving pre-release download page ===
=== Slow login investigation ===


[[User:Tflink|Tim Flink]] passed on some feedback<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098160.html</ref> he had received from a new tester who had downloaded a pre-release and asked some questions in the #fedora IRC channel, which does not handle pre-release issues. He suggested that it would be a good idea to add some text to the pre-release download page<ref>http://fedoraproject.org/get-prerelease</ref> explaining the right places to go to post feedback and get help with pre-release issues. [[User:Johannbg|Jóhann Guðmundsson]] and [[User:Adamwill|Adam Williamson]] both suggested filing a request with the websites team, and Tim reported<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098173.html</ref> that he had filed a ticket<ref>http://fedorahosted.org/fedora-websites/ticket/45</ref>.
Joachim Backes reported that he was seeing slow logins in Fedora 15<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098386.html</ref>, and Panu Matilainen confirmed the issue<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098392.html</ref>. Panu was able to pinpoint the issue as a bug in at-spi2-core<ref>http://lists.fedoraproject.org/pipermail/test/2011-March/098400.html</ref> and help the desktop team to produce a fix. Great work!


<references/>
<references/>

Revision as of 05:07, 14 April 2011

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

Thursday 2011-03-31 was ABRT Test Day[1]. As well as checking that ABRT (Fedora's automated crash report tool) is working as expected for Fedora 15, we tested out a big new feature, the retrace server[2]. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download and install often large debuginfo packages in order to submit reports. Michal Nowak posted a recap[3] of the event, noting that there had been eight testers and seventeen bugs filed overall.

This Thursday, 2011-04-14, will be virtualization Test Day[4], where our awesome virtualization team, starring Justin Forbes[5], will be our guides as we test the various virtualization features of Fedora 15, including shiny SPICE support in virt-manager[6]. Virtualization is a key component of any distribution nowadays, and the virtualization team always put on a smoothly run event, so please come along and help us test!

Fedora 15 Beta preparation

Preparation for the Fedora 15 Beta release moved into high gear over the last couple of weeks, with two more blocker review meetings[1] [2] and the TC1[3], RC1[4] and RC2[5] releases. Many testers made valuable contributions to the desktop and installation validation testing processes for each of these releases, and we were able to achieve comprehensive test coverage, and identify several blocker issues for the development team to fix. The group was able to catch SELinux issues caused by the introduction of the /run directory[6] very early and ensure the change did not land in the 'stable' Fedora 15 repository until this was resolved, and did not affect the Beta release.

Systemd and GNOME Shell documentation

Rahul Sundaram posted some documentation on Systemd[1] and GNOME Shell[2]. Both posts led to some lively discussion and suggested improvements.

Release criteria revisions

Adam Williamson announced his intention to push various recently discussed release criteria revisions into production[1], and later announced that he had done so[2]. In the meantime, a discussion developed on how to capture the fact that some desktops can block the release and some cannot in a clear yet future-proof way, with another proposal from Adam[3] and some well-considered reservations[4] from Jóhann Guðmundsson.

Bruno Wolff suggested criteria for image sizes[5], to ensure that images at each release point are of an appropriate size for convenient testing. Adam provided a proposed wording[6]. Dennis Gilmore pointed out that the sources DVD should probably be exempt from the criterion[7], at least until final release time.

Slow login investigation

Joachim Backes reported that he was seeing slow logins in Fedora 15[1], and Panu Matilainen confirmed the issue[2]. Panu was able to pinpoint the issue as a bug in at-spi2-core[3] and help the desktop team to produce a fix. Great work!