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
Call for Anaconda test cases
Chris Lumens posted a call for test cases[1] for automated storage testing in Anaconda, the Fedora system installer. Several people followed up with suggestions for tests.
Blocker bug tracking process improvements
Following some discussion on possible improvements to monitoring blocker bug trackers[1], Bruno Wolff provided some prefab Bugzilla queries for finding blocker bugs which have been closed but not verified[2], to help ensure that blocker bugs do not drop off the radar if they are improperly closed.
Update testing process improvements
Kevin Fenzi posted a call for ideas and comments on potential improvements and adjustments to the update testing processes[1]. An extensive discussion followed, and the various ideas presented and discussed will feed into FESCo's consideration of the topic.
Critical path test case creation process
Adam Williamson announced[1] that he had opened a trac ticket[2] to track the creation of a framework for package-specific test cases to aid the critical path package update testing process. Several recent discussions within both the development and QA groups had reinforced the need for specific test cases for critical path package updates, and he planned to create a framework to aid the creation of these tests and their integration into Bodhi, fedora-easy-karma and similar tools.