(create fwn 280 qa beat) |
(add new info from this week) |
||
| Line 10: | Line 10: | ||
=== Test Days === | === 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<ref>http://fedorahosted.org/fedora-qa/</ref>. | 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<ref>http://fedorahosted.org/fedora-qa/</ref>. [[User:Athmane|Athmane Madjoudj]] has been working on a proposed EC2 Test Day<ref>http://fedorahosted.org/fedora-qa/ticket/212</ref>. | ||
<references/> | <references/> | ||
| Line 17: | Line 17: | ||
At the QA group meeting of 2011-06-27<ref>http://fedoraproject.org/wiki/QA/Meetings/20110627</ref>, [[User:Rbergero|Robyn Bergeron]] emerged from a nutshell to bring up the topic of proposed pre-built Fedora images for Amazon's EC2 cloud platform<ref>http://aws.amazon.com/ec2/</ref>. These are being treated as new spins, and so they need QA approval (among other things). The group agreed to work with the Cloud SIG to draw up test procedures, and co-ordinate this through the cloud mailing list. | At the QA group meeting of 2011-06-27<ref>http://fedoraproject.org/wiki/QA/Meetings/20110627</ref>, [[User:Rbergero|Robyn Bergeron]] emerged from a nutshell to bring up the topic of proposed pre-built Fedora images for Amazon's EC2 cloud platform<ref>http://aws.amazon.com/ec2/</ref>. These are being treated as new spins, and so they need QA approval (among other things). The group agreed to work with the Cloud SIG to draw up test procedures, and co-ordinate this through the cloud mailing list. | ||
<references/> | |||
=== Test case development === | |||
[[User:Jdulaney|John Dulaney]] and [[User:Rhe|Rui He]] have been working on test cases for btrfs<ref>http://fedorahosted.org/fedora-qa/ticket/209</ref>. Rui has also been working on VNC install test cases<ref>http://fedorahosted.org/fedora-qa/ticket/210</ref>. | |||
<references/> | <references/> | ||
| Line 40: | Line 46: | ||
=== AutoQA === | === AutoQA === | ||
The team was in the final run-up to the release of AutoQA 0.5.0, which would include the previously-discussed 'pretty output' and spam reduction patches. Lucas Rodrigues announced the release of Autotest 0.13.0<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-June/002454.html</ref>, with packages available for testing in the autoqa-testing repository. | The team was in the final run-up to the release of AutoQA 0.5.0, which would include the previously-discussed 'pretty output' and spam reduction patches. The release of 0.5.0 duly happened on 2011-06-29<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-June/002496.html</ref>. Lucas Rodrigues announced the release of Autotest 0.13.0<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-June/002454.html</ref>, with packages available for testing in the autoqa-testing repository. | ||
<references/> | <references/> | ||
Revision as of 02:23, 7 July 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
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]. Athmane Madjoudj has been working on a proposed EC2 Test Day[2].
Cloud image approval
At the QA group meeting of 2011-06-27[1], Robyn Bergeron emerged from a nutshell to bring up the topic of proposed pre-built Fedora images for Amazon's EC2 cloud platform[2]. These are being treated as new spins, and so they need QA approval (among other things). The group agreed to work with the Cloud SIG to draw up test procedures, and co-ordinate this through the cloud mailing list.
Test case development
John Dulaney and Rui He have been working on test cases for btrfs[1]. Rui has also been working on VNC install test cases[2].
New proposed release validation matrices
Athmane Madjoudj combined the security test cases he has been working on recently into a proposed validation matrix for the Security Lab spin[1] and asked the group for feedback on it[2]. Adam Williamson proposed a new validation matrix[3] for validation tests which do not fit under the existing 'install' or 'desktop' matrices, for now referring to it as 'base', and asked for feedback[4].
Ensuring consistency of validation tests and release criteria
Adam Williamson began a survey to check the consistency of the release validation tests and the release criteria, to ensure tests were present for every criterion[1]. Together with Rui He and Athmane Madjoudj, he created new test cases and adjusted existing ones to ensure consistency with the Alpha release criteria.
Making release criteria more generic
James Laska proposed several changes to the release criteria[1], intended to make them more generic and hence applicable to secondary architectures. Adam Williamson generally liked the proposal but made some comments and asked some questions about some of them[2].
AutoQA
The team was in the final run-up to the release of AutoQA 0.5.0, which would include the previously-discussed 'pretty output' and spam reduction patches. The release of 0.5.0 duly happened on 2011-06-29[1]. Lucas Rodrigues announced the release of Autotest 0.13.0[2], with packages available for testing in the autoqa-testing repository.