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
The Fedora 15 Test Day track is now finished, and the main Fedora 16 Test Day track has not yet started. If you would like to propose a main track Test Day for the Fedora 16 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[1].
Release criteria and validation testing
Rui He added the finished VNC installation test cases to the install testing template[1]. Adam Williamson provided a survey comparing the Beta release criteria against the validation test cases[2], as he previously had for the Alpha release criteria (see FWN #280), and began filing tickets to request updates to the validation tests where needed.
James Laska put into production[3] his proposed changes to the release criteria to make them more generic (see FWN #280). James proceeded on to considering ways to implement release criteria and criteria variations specific to secondary architectures, outlining several possible ways to proceed with this[4]. Jóhann Guðmundsson[5], Adam Williamson[6] and Dennis Gilmore[7] provided feedback on his proposals, and all involved generally agreed on an approach to the problem.
Adam Williamson expanded his proposed 'base' release validation test matrix into a full proposed template page[8], and requested feedback on the draft.
- ↑ http://fedorahosted.org/fedora-qa/ticket/210#comment:3
- ↑ http://fedorahosted.org/fedora-qa/ticket/151#comment:15
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101156.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101177.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101178.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101182.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101192.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101180.html
A plea to proventesters
Michael Schwendt reminded proventesters[1] not to file positive feedback on an update for which a previous tester had provided negative feedback unless they were very sure the negative feedback was erroneous.
AutoQA
Having finished and released AutoQA 0.5.0, the AutoQA team was planning for the 0.6.0 development cycle[1]. James Laska and Kamil Paral have been working on an SOP for AutoQA releases[2].