QualityAssurance
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
Test Days
Last week's Test Day[1] was on the installer's (Anaconda) storage system. Unfortunately not a huge number of testers were present for this test day, but those who did come managed to test a range of scenarios and file several important bug reports. Thanks to all testers.
Next week's Test Day[2] on 2009-10-08 will be specifically on the use of software RAID arrays with Anaconda. As always, the Test Day will run all day in the #fedora-test-day IRC channel. This is a nice tightly focused topic with clear test cases, and an important feature for many users, so please come out to the Test Day and help us ensure softward RAID is tested on a wide range of storage hardware and configurations.
No Fit and Finish track Test Day is planned for next week.
If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[3].
Weekly meetings
The QA group weekly meeting[1] was held on 2009-09-28. The full log is available[2]. Adam Williamson noted that follow-up on the development issues discussed the previous week was impossible with Jesse Keating and David Pravec absent, so left the topic for the following week.
Will Woods reported on the progress of the AutoQA project. The major achievement was a working prototype of the planned israwhidebroken.com site, of which Will provided a screenshot[3]. The source code for the web application which controls the page is also available[4]. The app allows results for manual-only tests to be provided by users authenticated via FAS. Will is planning to extend the app to provide links to logs for the automated tests, and the ability to add bug report links for failed tests. Two new tests[5] [6] had been added to cover the later stages of Anaconda installation (beyond disk partitioning).
Adam Williamson summarized upcoming events, and James Laska pointed out the relevant calendar page[7]. The beta freeze and beta candidate build process was imminent, and the fourth beta blocker review meeting was due Friday 2009-10-02. Denise Dumas pointed out that some important bugs required testing to confirm prospective fixes, and Adam pointed to the beta blocker bug list[8] as a reference for these.
James Laska started a discussion regarding plans for the then-upcoming Anaconda storage filtering Test Day[9]. Denise Dumas was in favour of cancelling it as the storage filtering changes had been delayed until Fedora 13. James and Adam Williamson suggested converting it into a more general test day on Anaconda storage issues, and this path was agreed upon. James and Denise agreed to work to ensure Anaconda would be in a testable state for the Test Day.
The Bugzappers group weekly meeting[10] was held on 2009-09-29. The full log is available[11]. Edward Kirk reported that he had started work on moving action items from previous meetings into Trac[12], as had been discussed the previous week, and would continue to work on it. Adam Williamson encouraged him to ask for help if he felt it was too much work to complete on his own.
Edward Kirk also provided a draft of the meeting organization SOP[13] that he had begun work on. The group felt it was a good start. Edward wondered where the page should end up, and Adam Williamson suggested it should be a page of its own, linked from the main Meetings page[14], as other SOP pages are. Edward promised to work on finalizing the page for the next meeting.
Edward Kirk said that he had emailed Brennan Ashton for an update on the triage metrics project, but had not received a reply. He said he was working on a plan to move the project forward given Brennan's erratic availability.
Edward Kirk asked if it was yet time to implement the previously discussed change to triage policy, which was intended to begin when Fedora 13 became active. Adam Williamson noted that branching had occurred on the development side, but Rawhide was still tracking Fedora 12 rather than Fedora 13, and the policy change should take effect when Rawhide began tracking Fedora 13.
Edward Kirk reminded the group that housekeeping tasks[15] for the Fedora 13 release would be due soon. He and John Poelstra already had planned to divide the tasks up between themselves.
Sergey Rudchenko asked about what to do with Fedora 10 bugs as the end of support for Fedora 10 approached. Edward Kirk and Adam Williamson suggested that he ask the reporters of Fedora 10 bugs to see if they could be reproduced on Fedora 11 or 12, and move the bugs to one of those releases if they could.
The next QA weekly meeting will be held on 2009-10-05 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-10-06 at 1500 UTC in #fedora-meeting.
- ↑ http://fedoraproject.org/wiki/QA/Meetings
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.log.html
- ↑ http://wwoods.fedorapeople.org/screenshots/irb.png
- ↑ http://fedorapeople.org/gitweb?p=wwoods/public_git/israwhidebroken.git;a=summary
- ↑ http://fedoraproject.org/wiki/QA:Anaconda_package_install_test_case
- ↑ http://fedoraproject.org/wiki/QA:Anaconda_bootloader_setup_test_case
- ↑ http://poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html
- ↑ http://bugzilla.redhat.com/showdependencytree.cgi?id=507678&hide_resolved=1
- ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-01_Anaconda/Features/StorageFiltering
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-09-29/fedora-meeting.2009-09-29-15.25.log.html
- ↑ http://fedorahosted.org/triage/
- ↑ https://fedoraproject.org/wiki/User:Tk009/meeting-sop
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
- ↑ http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Blocker bug criteria
Alexey Torkhov asked[1] about the Wiki page on release criteria[2], asking 'If I've found a bug that (I think) breaks MUST rule should I add it to both F12Beta and F12Blocker trackers? And if it breaks SHOULD rule, it should be added only to F12Blocker tracker?' Adam Williamson replied[3] that Alexey's interpretation was correct as far as the criteria defined on that page went, but in practice bugs outside of those criteria were still considered Beta and final release blockers, as it was very hard comprehensively to codify all possible release criteria.
Beta test compose Delta ISOs
Andre Robatino reported[1] that he had been unable to generate Delta ISOs from the Alpha release to the Beta test compose due to some technical problems.
Xfce Test Day recap
Kevin Fenzi provided a recap[1] of the previous week's Xfce Test Day[2], thanking participants and providing a list of bugs which had been filed.
Wiki Test Results name space
James Laska forwarded[1] a ticket[2] about the creation of a Test_Results wiki namespace for the purpose of filing test results separately from Test Day events (the name space will allow people who have not signed the CLA to file results, as they currently are able to on Test Day pages). Adam Williamson replied[3] worrying about the implied suggestion that the Test_Day namespace be removed and all Test Day pages moved to the Test_Results namespace, which he thought would be a bad change. Jóhann Guðmundsson agreed[4].
Proposed removal of Anaconda from Test Day CDs
Kamil Paral proposed[1] the removal of Anaconda from the standard build configuration for Test Day live images, on the basis that it is rarely used as part of Test Day testing and dependency problems with the anaconda package sometimes cause problems in the generation of the images. Several replies felt the change was unnecessary, and the availability of Anaconda on the Test Day CDs probably helped get more people testing Rawhide installation. In the end it was agreed that adding instructions for removing anaconda from the build to the Test Day live CD creation instructions page[2] would be sufficient to address the problem.
Installation testing results
Liam Li provided a report[1] on testing conducted by his team of Red Hat testers on installation using the pre-Beta and Beta test compose images. He summarized the bugs they had encountered, and asked for help in completing the test cases listed on the test matrix[2] which the team had not been able to cover.