From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 271 qa beat)
(create fwn 272 beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


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.
Thursday 2011-04-14 was virtualization Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization</ref>, hosted by our awesome virtualization team. A decent turnout of nine testers were able to run through all the test cases, and identify several bugs for the team to work on.


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!
Thursday 2011-04-21 is the last of three GNOME 3 Test Days<ref>http://fedoraproject.org/wiki/Test_Day:2011-04-21_GNOME3_Final</ref>, where we will be testing out the final GNOME 3.0 release and making sure it is well integrated into Fedora 15, and identifying any remaining bugs that can be fixed up before Fedora 15's release. Live images are already available on the Test Day page to aid in testing, and it's very easy to join in and run through as many or as few test cases as you like. Please join us in #fedora-test-day on Freenode IRC<ref>irc://irc.freenode.net/fedora-test-day</ref> for this key Test Day!
 
Thursday 2011-04-28 is scheduled to be cloud Test Day, where the cloud SIG will be guiding testers in running Fedora 15 on Amazon's EC2 cloud, and testing out the Fedora 15 features BoxGrinder<ref>http://fedoraproject.org/wiki/Features/BoxGrinder</ref> (a tool designed to make it simple to rapidly create Fedora-based appliances and deploy them to various virtual platforms) and CloudFS<ref>http://fedoraproject.org/wiki/Features/CloudFS</ref> (a cloud-ready distributed filesystem). If you're interested in the cutting (bleeding?) edge of cloud development with Fedora, come and dive in!


<references/>
<references/>
Line 18: Line 20:
=== Fedora 15 Beta preparation ===
=== 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<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.
Fedora 15 Beta RC2 arrived on 2011-04-09<ref>http://lists.fedoraproject.org/pipermail/test/2011-April/098755.html</ref> and the group got down to testing it, filling out the installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_15_Beta_RC2_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_15_Beta_RC2_Desktop</ref>test matrices and delving into various issues on the mailing list, particularly to do with GNOME 3. At the go/no-go meeting of 2011-04-13<ref>http://meetbot.fedoraproject.org/fedora-meeting/2011-04-13/fedora_15_beta_gono-go_meeting.2011-04-13-21.00.html</ref> the QA group was able to confidently declare RC2 had met all the release requirements, thanks to this diligent testing, and the RC2 images were declared gold. Rest is for the weak, though, so on 2011-04-15 the group followed up with the first blocker bug review meeting for Fedora 15 final<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-15/f-15-blocker-review.2011-04-15-17.00.html</ref>, a mere four hour sprint at which 58 potential blocker bugs were reviewed.
 
<references/>
 
=== Systemd and GNOME Shell documentation ===
 
[[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/>
 
=== 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]].
 
[[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/>
 
=== Slow login investigation ===
 
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 04:20, 21 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

  1. ↑ http://fedoraproject.org/wiki/QA
  2. ↑ http://fedoraproject.org/wiki/QA/Join

Test Days

Thursday 2011-04-14 was virtualization Test Day[1], hosted by our awesome virtualization team. A decent turnout of nine testers were able to run through all the test cases, and identify several bugs for the team to work on.

Thursday 2011-04-21 is the last of three GNOME 3 Test Days[2], where we will be testing out the final GNOME 3.0 release and making sure it is well integrated into Fedora 15, and identifying any remaining bugs that can be fixed up before Fedora 15's release. Live images are already available on the Test Day page to aid in testing, and it's very easy to join in and run through as many or as few test cases as you like. Please join us in #fedora-test-day on Freenode IRC[3] for this key Test Day!

Thursday 2011-04-28 is scheduled to be cloud Test Day, where the cloud SIG will be guiding testers in running Fedora 15 on Amazon's EC2 cloud, and testing out the Fedora 15 features BoxGrinder[4] (a tool designed to make it simple to rapidly create Fedora-based appliances and deploy them to various virtual platforms) and CloudFS[5] (a cloud-ready distributed filesystem). If you're interested in the cutting (bleeding?) edge of cloud development with Fedora, come and dive in!

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2011-04-21_GNOME3_Final
  3. ↑ irc://irc.freenode.net/fedora-test-day
  4. ↑ http://fedoraproject.org/wiki/Features/BoxGrinder
  5. ↑ http://fedoraproject.org/wiki/Features/CloudFS

Fedora 15 Beta preparation

Fedora 15 Beta RC2 arrived on 2011-04-09[1] and the group got down to testing it, filling out the installation[2] and desktop[3]test matrices and delving into various issues on the mailing list, particularly to do with GNOME 3. At the go/no-go meeting of 2011-04-13[4] the QA group was able to confidently declare RC2 had met all the release requirements, thanks to this diligent testing, and the RC2 images were declared gold. Rest is for the weak, though, so on 2011-04-15 the group followed up with the first blocker bug review meeting for Fedora 15 final[5], a mere four hour sprint at which 58 potential blocker bugs were reviewed.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-April/098755.html
  2. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_15_Beta_RC2_Install
  3. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_15_Beta_RC2_Desktop
  4. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-04-13/fedora_15_beta_gono-go_meeting.2011-04-13-21.00.html
  5. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2011-04-15/f-15-blocker-review.2011-04-15-17.00.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=232759"