From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 219 qa beat)
(https)
Line 12: Line 12:
Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-03-25_Printing</ref> was on printing, including the implementation of automatic print driver installation<ref>http://fedoraproject.org/wiki/Features/AutomaticPrintDriverInstallation</ref>in Fedora 13. There was a disappointingly low turnout, despite [[User:twaugh|Tim Waugh's]] extensive efforts to organize and promote the event. We theorize that printing works so well for most people that they didn't think it was necessary to turn up! Nevertheless, thanks to those who did come out to test, and reported five bugs for Tim to work on.
Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-03-25_Printing</ref> was on printing, including the implementation of automatic print driver installation<ref>http://fedoraproject.org/wiki/Features/AutomaticPrintDriverInstallation</ref>in Fedora 13. There was a disappointingly low turnout, despite [[User:twaugh|Tim Waugh's]] extensive efforts to organize and promote the event. We theorize that printing works so well for most people that they didn't think it was necessary to turn up! Nevertheless, thanks to those who did come out to test, and reported five bugs for Tim to work on.


This week sees two Test Days. The first<ref>https://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault</ref>, on Tuesday 2010-03-30, will have passed by the time you read this; it will have been on the implementation of SSSD by default<ref>http://fedoraproject.org/wiki/Features/SSSDByDefault</ref>. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. We'll bring you a report on this event next week.
This week sees two Test Days. The first<ref>http://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault</ref>, on Tuesday 2010-03-30, will have passed by the time you read this; it will have been on the implementation of SSSD by default<ref>http://fedoraproject.org/wiki/Features/SSSDByDefault</ref>. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. We'll bring you a report on this event next week.


The second<ref>https://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT</ref> will be on ABRT<ref>http://fedoraproject.org/wiki/Features/ABRT</ref>, the automated bug report tool which has been included with Fedora by default since the release of Fedora 12. We'll be testing Fedora 13 enhancements to ABRT and making sure the system is working correctly for the upcoming Fedora 13 release. ABRT is important to all Fedora users and developers, so if you have a few minutes, please come along and help test! As usual, you can test with an installed Fedora 13 or Rawhide system, or a live image which is available on the Test Day page. [[User:Zprikryl|Zdenek Prikryl]], [[User:Jmoskovc|Jiri Moskovc]] and [[User:Adamwill|Adam Williamson]] will be on hand during the event, which will run all day on Thursday 2010-04-01 in the #fedora-test-day IRC channel.
The second<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT</ref> will be on ABRT<ref>http://fedoraproject.org/wiki/Features/ABRT</ref>, the automated bug report tool which has been included with Fedora by default since the release of Fedora 12. We'll be testing Fedora 13 enhancements to ABRT and making sure the system is working correctly for the upcoming Fedora 13 release. ABRT is important to all Fedora users and developers, so if you have a few minutes, please come along and help test! As usual, you can test with an installed Fedora 13 or Rawhide system, or a live image which is available on the Test Day page. [[User:Zprikryl|Zdenek Prikryl]], [[User:Jmoskovc|Jiri Moskovc]] and [[User:Adamwill|Adam Williamson]] will be on hand during the event, which will run all day on Thursday 2010-04-01 in the #fedora-test-day IRC channel.


If you would like to propose a main track Test Day for the Fedora 13 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 13 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 28: Line 28:
'John H' reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089584.html</ref> that the test candidate build failed to install correctly to an Intel X25-M SSD. [[User:Jlaska|James Laska]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089595.html</ref> he file a bug report on the issue.
'John H' reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089584.html</ref> that the test candidate build failed to install correctly to an Intel X25-M SSD. [[User:Jlaska|James Laska]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089595.html</ref> he file a bug report on the issue.


[[User:Kparal|Kamil Paral]], Joachim Backes<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089715.html</ref> and others found a bug<ref>https://bugzilla.redhat.com/show_bug.cgi?id=577789</ref> which prevented the boot process from completing successfully with the Plymouth graphical boot system enabled. The bug was later tracked down and resolved in a build which will be brought into the second Beta release candidate.
[[User:Kparal|Kamil Paral]], Joachim Backes<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/089715.html</ref> and others found a bug<ref>http://bugzilla.redhat.com/show_bug.cgi?id=577789</ref> which prevented the boot process from completing successfully with the Plymouth graphical boot system enabled. The bug was later tracked down and resolved in a build which will be brought into the second Beta release candidate.


<references/>
<references/>

Revision as of 06:27, 31 March 2010

QualityAssurance

In this section, we cover the activities of the QA team[1]. This week, we are trying out a new topic-focused layout, without the topic-by-topic weekly meeting recaps. Please let me know if you particularly like or dislike the new layout!

Contributing Writer: Adam Williamson

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

Test Days

Last week's Test Day[1] was on printing, including the implementation of automatic print driver installation[2]in Fedora 13. There was a disappointingly low turnout, despite Tim Waugh's extensive efforts to organize and promote the event. We theorize that printing works so well for most people that they didn't think it was necessary to turn up! Nevertheless, thanks to those who did come out to test, and reported five bugs for Tim to work on.

This week sees two Test Days. The first[3], on Tuesday 2010-03-30, will have passed by the time you read this; it will have been on the implementation of SSSD by default[4]. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. We'll bring you a report on this event next week.

The second[5] will be on ABRT[6], the automated bug report tool which has been included with Fedora by default since the release of Fedora 12. We'll be testing Fedora 13 enhancements to ABRT and making sure the system is working correctly for the upcoming Fedora 13 release. ABRT is important to all Fedora users and developers, so if you have a few minutes, please come along and help test! As usual, you can test with an installed Fedora 13 or Rawhide system, or a live image which is available on the Test Day page. Zdenek Prikryl, Jiri Moskovc and Adam Williamson will be on hand during the event, which will run all day on Thursday 2010-04-01 in the #fedora-test-day IRC channel.

If you would like to propose a main track Test Day for the Fedora 13 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-03-25_Printing
  2. ↑ http://fedoraproject.org/wiki/Features/AutomaticPrintDriverInstallation
  3. ↑ http://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault
  4. ↑ http://fedoraproject.org/wiki/Features/SSSDByDefault
  5. ↑ http://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT
  6. ↑ http://fedoraproject.org/wiki/Features/ABRT
  7. ↑ http://fedorahosted.org/fedora-qa/

Fedora 13 testing

The first test compose for Fedora 13 Beta was announced[1] by Rui He on 2010-03-23. The group helped to fill out the planned installation[2] and desktop[3] test matrices. Rui He provided a summary[4] of the TC test results. Shortly after the test compose, the first release candidate build followed[5] on 2010-03-26. Andre Robatino provided delta ISOs between TC1 and RC1[6]. Again, the group quickly filled out the desktop[7] and install[8] matrices. The testers found several blocker issues.

The third blocker bug review meeting for Fedora 13 Beta was held on 2010-03-26[9]. All outstanding Beta blocker bugs were reviewed, and developers were consulted on the remaining open bugs to ensure fixes should be available in time for the release candidate process to begin the following week.

'John H' reported[10] that the test candidate build failed to install correctly to an Intel X25-M SSD. James Laska suggested[11] he file a bug report on the issue.

Kamil Paral, Joachim Backes[12] and others found a bug[13] which prevented the boot process from completing successfully with the Plymouth graphical boot system enabled. The bug was later tracked down and resolved in a build which will be brought into the second Beta release candidate.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089526.html
  2. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_TC1_Install
  3. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_TC1_Desktop
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089681.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089680.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089684.html
  7. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC1_Desktop
  8. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC1_Install
  9. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2010-03-26/f-13-beta-blocker-review.2010-03-26-16.05.html
  10. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089584.html
  11. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089595.html
  12. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089715.html
  13. ↑ http://bugzilla.redhat.com/show_bug.cgi?id=577789

Update acceptance testing

During the weekly QA meeting[1], the group discussed the status of the various proposed changes and policies regarding updates. Adam Williamson summarized that "we need: a policy/sop for the 'proventesters' group, and a guide to providing updates-testing feedback for a) branched and b) stable releases, explaining what actually should be tested and how feedback should be given". Adam Miller provided[2] a second draft of the proventesters SOP proposal, and Adam Williamson posted a discussion of testing procedure[3] which posited that a policy for testing updates was impossible within the current Bodhi system, and the best way forward would be to revise the way Bodhi works. Mathieu Bridon pointed out[4] that Williamson's proposal was very similar to Doug Ledford's earlier proposal[5], and explained that the infrastructure team was already working Doug's ideas into their plans for 'Bodhi 2', the next major revision of Bodhi.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings/20100322
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089764.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089690.html
  4. ↑ http://lists.fedoraproject.org/pipermail/devel/2010-March/134089.html
  5. ↑ http://lists.fedoraproject.org/pipermail/devel/2010-March/131799.html

Target bug trackers

Following on from discussion the previous week, Adam Williamson posted a proposal[1] on the use of the Target bug trackers, suggesting either discontinuing their use or repurposing them to track bugs which did not constitute release blockers, but for which fixes would be accepted through release freezes. The thread turned into quite a wide-ranging discussion about freeze procedures and update acceptance. Later, Adam summarized by suggesting the key issue to decide is 'whether we want to have a time-defined stage' where only fixes for blockers and certain specifically chosen bugs would be accepted, and if a tracker bug is the most sensible way to keep track of those bugs[2].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089575.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089664.html

Bugzapping in the classroom

Vedran Miletić asked the groupCite error: Closing </ref> missing for <ref> tag to provide support and assistance.


rsync for test builds

Andre Robatino asked[1] if it would be possible to set up rsync access for the server on which test builds are stored, to make it easier to convert a DVD build into a multi-CD build for testing purposes. He then suggested[2] that zsync would serve the purpose even better. Adam Williamson pointed out[3] that zsync was still not packaged in Fedora due to a problem with bundled libraries.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089669.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089735.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2010-March/089798.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=162621"