FWN/Beats/QualityAssurance: Difference between revisions

Revision as of 19:51, 1 September 2010

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

Last week's Test Day^[1], held on 2010-08-26, was on OpenSCAP^[2], an open implementation of SCAP, which aims to provide a standardized approach to maintaining the security of systems. There was a good turnout for the Test Day, and it was successful in discovering five significant bugs for the developers to work on, one of which has already been fixed.

This week's Test Day^[3] on 2010-09-02 will be on preupgrade^[4], the Fedora in-place upgrade system. This is always an important test day as we attempt to ensure the upgrade mechanisms for the next release work as expected. As upgrading is a complex process and highly dependent on the installed system, it would help to have as many testers as possible to help track down any bugs we can find. As always, the Test Day will run all day in the #fedora-test-day IRC channel. You will need to have an installed Fedora 13 system you don't mind hurting in order to help out with the testing - but remember, testing in a virtual machine is easy and non-destructive!

Next week's Test Day^[5] on 2010-09-09 will be on systemd^[6], the new initialization system being introduced in Fedora 14. This is a major change which will affect every user of Fedora 14, so it would help to have as many testers as possible to help track down any bugs we can find. As always, the Test Day will run all day in the #fedora-test-day IRC channel. You can help out with testing using a live image or a virtual machine, so there's no need to alter your main system. Please drop by and help test systemd if you can!

If you would like to propose a main track Test Day for the Fedora 14 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac^[7].

Fedora 14 Beta blocker review

The first blocker review meeting for Fedora 14 Beta took place on Friday 2010-08-27^[1], and James Laska posted a recap^[2]. The group considered the eight open blockers for the Beta release and accepted two, rejected two, and left four on the list without confirming them, pending further information.

AutoQA

Josef Skladanka psoted a draft^[1] of a guide to writing AutoQA tests^[2]. Josef, Kamil Paral and James Laska continued to revise and refine the page over the next few days.

Vojtěch Aschenbrenner improved the upgrade path test^[3] to run automatically on post-bodhi-hook and to improve the output format.

[1] ttp://fedoraproject.org/wiki/QA

[2] ttp://fedoraproject.org/wiki/QA/Join

[3] ttp://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP

[4] ttp://fedoraproject.org/wiki/Features/OpenSCAP

[5] ttp://fedoraproject.org/wiki/Test_Day:2010-09-02_Preupgrade

[6] ttp://fedoraproject.org/wiki/Preupgrade

[7] ttp://fedoraproject.org/wiki/Test_Day:2010-09-09_Systemd

[8] ttp://fedoraproject.org/wiki/Features/systemd

[9] ttp://fedorahosted.org/fedora-qa/

[10] ttp://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-27/f-14-beta-blocker-review.2010-08-27-16.00.html

[11] ttp://lists.fedoraproject.org/pipermail/test/2010-August/093084.html

[12] ttp://fedorahosted.org/pipermail/autoqa-devel/2010-August/001038.html

[13] ttp://fedoraproject.org/wiki/User:Jskladan/Sandbox:Writing_autoqa_tests

[14] ttp://fedorahosted.org/pipermail/autoqa-devel/2010-August/001037.html

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[1]

[2]

[1]

[2]

[3]

@@ Line 14: / Line 14: @@
 This week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-09-02_Preupgrade</ref> on 2010-09-02 will be on preupgrade<ref>http://fedoraproject.org/wiki/Preupgrade</ref>, the Fedora in-place upgrade system. This is always an important test day as we attempt to ensure the upgrade mechanisms for the next release work as expected. As upgrading is a complex process and highly dependent on the installed system, it would help to have as many testers as possible to help track down any bugs we can find. As always, the Test Day will run all day in the #fedora-test-day IRC channel. You will need to have an installed Fedora 13 system you don't mind hurting in order to help out with the testing - but remember, testing in a virtual machine is easy and non-destructive!
-Next week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-09-09_Systemd</ref> on 2010-09-09 will be on systemd<ref>https://fedoraproject.org/wiki/Features/systemd</ref>, the new initialization system being introduced in Fedora 14. This is a major change which will affect every user of Fedora 14, so it would help to have as many testers as possible to help track down any bugs we can find. As always, the Test Day will run all day in the #fedora-test-day IRC channel. You can help out with testing using a live image or a virtual machine, so there's no need to alter your main system. Please drop by and help test systemd if you can!
+Next week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-09-09_Systemd</ref> on 2010-09-09 will be on systemd<ref>http://fedoraproject.org/wiki/Features/systemd</ref>, the new initialization system being introduced in Fedora 14. This is a major change which will affect every user of Fedora 14, so it would help to have as many testers as possible to help track down any bugs we can find. As always, the Test Day will run all day in the #fedora-test-day IRC channel. You can help out with testing using a live image or a virtual machine, so there's no need to alter your main system. Please drop by and help test systemd if you can!
 If you would like to propose a main track Test Day for the Fedora 14 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>.

Search