From Fedora Project Wiki

< FWN‎ | Beats

(https)
(create fwn 241 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


This week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP</ref> on 2010-08-26 will be on OpenSCAP<ref>http://fedoraproject.org/wiki/Features/OpenSCAP</ref>, an open implementation of SCAP, which aims to provide a standardized approach to maintaining the security of systems. This Test Day is most likely to be of interest to those who already have some knowledge of SCAP and are interested in an open source implementation within the Fedora project. As always, the Test Day will run all day in the #fedora-test-day IRC channel.
Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP</ref>, held on 2010-08-26, was on OpenSCAP<ref>http://fedoraproject.org/wiki/Features/OpenSCAP</ref>, 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.


Next 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!
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!


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>.
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>.
Line 18: Line 20:
<references/>
<references/>


=== Fedora 14 Alpha testing ===
=== Fedora 14 Beta blocker review ===


As always, the QA team was very active in testing the latest pre-release, Fedora 14 Alpha, conducting desktop<ref>http://fedoraproject.org/wiki/QA:Desktop_validation_testing</ref> and installation<ref>http://fedoraproject.org/wiki/QA:Installation_validation_testing</ref> validation testing (with the valued help of the desktop SIGs) for each build as we worked through the test candidate<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092367.html</ref>, RC1<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092468.html</ref>, RC2<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092493.html</ref>, RC3<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092573.html</ref> and RC4<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092700.html</ref>. At the initial go/no-go meeting on 2010-08-12<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-12-00.00.html</ref>, the QA representative [[User:Adamwill|Adam Williamson]] had to propose a slip due to a remaining blocker issue<ref>http://bugzilla.redhat.com/show_bug.cgi?id=623129</ref>. This issue was resolved in RC4. A second potential blocker lingered, but extensive feedback from many QA group members to Adam's request for testing<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092681.html</ref> was instrumental in identifying it as not blocking the release, and at the second go/no-go meeting, QA along with the development and release engineering groups agreed to go ahead with the Alpha release<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-08-19/fedora-meeting.2010-08-19-00.00.html</ref>.
The first blocker review meeting for Fedora 14 Beta took place on Friday 2010-08-27<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-27/f-14-beta-blocker-review.2010-08-27-16.00.html</ref>, and [[User:Jlaska|James Laska]] posted a recap<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/093084.html</ref>. 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.


<references/>
<references/>


=== Release criteria update ===
=== AutoQA ===
 
The blocker review process for Fedora 14 Alpha made it clear that there were several areas where the coverage of the release criteria<ref>http://fedoraproject.org/wiki/Fedora_Release_Criteria</ref> was incomplete, so [[User:Adamwill|Adam Williamson]] proposed several new criteria in two mailing list threads<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092615.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092617.html</ref>, to cover booting to a console and the 'basic graphics mode' of the installer. The proposals were generally positively received, so Adam went ahead and added them to the criteria<ref>http://lists.fedoraproject.org/pipermail/test/2010-August/092784.html</ref>.
 
<references/>
 
=== Learning lessons from updates ===


[[User:Kevin|Kevin Fenzi]] created a page<ref>http://fedoraproject.org/wiki/Updates_Lessons</ref> to track problems caused by updates to stable Fedora releases, and brought it up for discussion during the weekly QA meeting of 2010-08-16<ref>http://fedoraproject.org/wiki/QA/Meetings/20100816</ref>. [[User:Jlaska|James Laska]] suggested that issues tracked there should be discussed at the FESCo level, and any issues of concern for QA passed back down to the QA group by FESCo. James also volunteered to adjust the wiki page to track recommendations and results for each issue.
[[User:Jskladan|Josef Skladanka]] psoted a draft<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-August/001038.html</ref> of a guide to writing AutoQA tests<ref>http://fedoraproject.org/wiki/User:Jskladan/Sandbox:Writing_autoqa_tests</ref>. Josef, [[User:Kparal|Kamil Paral]] and [[User:Jlaska|James Laska]] continued to revise and refine the page over the next few days.
 
<references/>
 
=== AutoQA ===


Vojtěch Aschenbrenner created a test case<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-August/000967.html</ref> for checking if a new package for a given release would be considered a 'newer' package than the newest version of the same package available in the repositories for later releases, a situation which causes problems with upgrades. [[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] continued to work on the complex dependency check tests, and Will recently posted a summary of the current status and next steps<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-August/001010.html</ref>.
Vojtěch Aschenbrenner improved the upgrade path test<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-August/001037.html</ref> to run automatically on post-bodhi-hook and to improve the output format.


<references/>
<references/>

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

  1. ↑ http://fedoraproject.org/wiki/QA
  2. ↑ http://fedoraproject.org/wiki/QA/Join

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].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP
  2. ↑ http://fedoraproject.org/wiki/Features/OpenSCAP
  3. ↑ http://fedoraproject.org/wiki/Test_Day:2010-09-02_Preupgrade
  4. ↑ http://fedoraproject.org/wiki/Preupgrade
  5. ↑ http://fedoraproject.org/wiki/Test_Day:2010-09-09_Systemd
  6. ↑ https://fedoraproject.org/wiki/Features/systemd
  7. ↑ http://fedorahosted.org/fedora-qa/

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.

  1. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-27/f-14-beta-blocker-review.2010-08-27-16.00.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2010-August/093084.html

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. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2010-August/001038.html
  2. ↑ http://fedoraproject.org/wiki/User:Jskladan/Sandbox:Writing_autoqa_tests
  3. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2010-August/001037.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=195269"