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-10 was the second of three planned GNOME 3 Test Days[1]. Despite a reduced turnout, a lot of valuable testing took place thanks to the dedication of those who did show up, and many more bugs were discovered - some being fixed during the event. Vitezslav Humpa, who along with Radek Lat helped to organize this event, posted a recap [2] to the mailing list with a good overview of all the reported bugs.
Thus Thursday, 2011-03-17, will be preupgrade Test Day[3], where we will be testing this important mechanism for upgrading to Fedora 15. Upgrading is always one of the thorniest areas of a Fedora release, so if it's important to you and you can come along and help test, please do - the more testing we can get early on, the better the final result will be.
Next Thursday, 2011-03-24, is scheduled as power management Test Day[4], to test out various aspects of power management in Fedora 15. However, planning for the event is not yet complete, so it may be cancelled or postponed.
Test case management system comparison
Continuing her ongoing work on test case management system evaluation, Rui He posted a proposed list of features[1] that the candidate new system, Nitrate, must have before it can replace the current system of using the Wiki to organize test cases. After James Laska replied[2], the two continued to discuss and refine the list.
Fedora 15 Beta preparation
The first Beta blocker/nice-to-have review meeting took place on 2011-03-11[1], and the team worked through the full list of proposed Beta blocker and nice-to-have bugs. The first Beta test compose is due for release on 2011-03-22.