From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 169 qa beat)
(create qa beat for fwn 170)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


This week's<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-26</ref> was on the Noveau driver<ref>https://fedoraproject.org/wiki/Features/NouveauAsDefault</ref>for NVIDIA video cards, which will become the default in Fedora 11. Thanks to an excellent turnout, over 80 sets of results were reported, and several bug reports were made: some of the issues have already been resolved. The developer present was [[User:bskeggs|Ben Skeggs]], and [[User:Adamwill|Adam Williamson]], [[User:Jlaska|James Laska]] and [[User:Wwoods|Will Woods]] were present for the QA team.
This week's first Test Day<ref>https://fedoraproject.org/wiki/Test_Day:Radeon_2009-04-01</ref> was on the Radeon driver for ATI video cards, which has seen substantial changes for Fedora 11. The turnout was again excellent and many useful bug reports were filed. The developer present was [[DaveAirlie|Dave Airlie]], and [[User:Adamwill|Adam Williamson]] and [[User:Jlaska|James Laska]] were present for the QA team. The second Test Day<ref>https://fedoraproject.org/wiki/Test_Day:Power_management_2009-04-02</ref> was on power management. There was a good turnout of dedicated Rawhide users, and the results were quite positive: most testers found everything worked and few major bugs were discovered.


Next week again will see two test days. The first<ref>https://fedoraproject.org/wiki/QA/Test_Days/2009-04-01</ref> will be on the radeon driver for ATI graphics cards, while the second<ref>https://fedoraproject.org/wiki/QA/Test_Days/2009-04-02</ref> will be on <ref>https://fedoraproject.org/wiki/Features/PowerManagement</ref> power management. Live CDs will be available for both test days so you'll be able to test without a Rawhide installation. The Radeon test day will be held on Wednesday (2009-03-01) and the Power Management test day on Thursday (2009-03-02) in the #fedora-qa channel on Freenode IRC. If you have a Radeon graphics card, please make sure to come along to the first test day; if you have a laptop, please come to the second. If you can't make it on the day, please do the tests and fill out your results on the page another day.
Next week's Test Day<ref>https://fedoraproject.org/wiki/Test_Day:2009-04-09_UEFI</ref> will be on the UEFI<ref>https://fedoraproject.org/wiki/Features/EFI</ref> support in Fedora 11. UEFI hardware is not yet widely available, so this Test Day is mostly only of interest to Red Hat QA staff with access to testing hardware.


<references/>
<references/>
Line 18: Line 18:
=== Weekly meetings ===
=== Weekly meetings ===


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-03-25. [[User:Wwoods|Will Woods]] reported that the Fedora 11 beta release had slipped.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-04-01. The full log is available<ref>http://www.happyassassin.net/extras/fedora-qa-20090401.log</ref>[[User:Jlaska|James Laska]] and [[User:Adamwill|Adam Williamson]] reported no progress this week with the Semantic mediawiki extension.


[[User:Jlaska|James Laska]] reported that packaging work on the Semantic extension for Mediawiki was progressing, and one package had already passed review. He also noted that he had created a test Mediawiki instance with the extension enabled, but had not yet been able to do much testing. [[User:Adamwill|Adam Williamson]] confirmed that he also had not had time to do much testing.
[[User:Jlaska|James Laska]] reported that packaging work on the Semantic extension for Mediawiki was progressing, and one package had already passed review. He also noted that he had created a test Mediawiki instance with the extension enabled, but had not yet been able to do much testing. [[User:Adamwill|Adam Williamson]] confirmed that he also had not had time to do much testing.


[[User:Adamwill|Adam Williamson]] reported that planning for the Radeon test day was still in progress. He also reported that Bugzappers team review of Anaconda bugs for the Fedora 11 beta release had been successfully completed.
[[User:Adamwill|Adam Williamson]] noted that the release notes should cover the known problem with generating live USB images from the Fedora 11 Beta live CD images using Fedora 10, caused by the older version of syslinux it contains. The group agreed to file a bug on this issue and add a note to the release notes, linking to the bug report.


[[User:Adamwill|Adam Williamson]] reported that the Xfce test day was fully planned, and [[User:Kevin|Kevin Fenzi]] reported that he had successfully generated some live CD images for the test day. Adam asked if someone could make sure these images would be available for download.
[[User:Wwoods|Will Woods]] and [[User:jkeating|Jesse Keating]] reported steady progress with autoqa work, and hope to have two hooks - post-repo-update and post-tree-compose - running by next week.


[[User:Wwoods|Will Woods]] reported that he had been testing upgrade scenarios for the Fedora 11 beta release and had found several bugs in this area.
[[User:Wwoods|Will Woods]] brought up the new blog<ref>http://rawhidewatch.wordpress.com/</ref> started by [[User:Wtogami| Warren Togami]] to note major issues in Rawhide, and suggested the QA group should propose to work together with Warren on the project.


[[User:Jlaska|James Laska]] noted that most critical bugs for the beta release were already known and being tracked, and re-testing was not necessary for any known issues. A long discussion followed on the correct place and format in which to note known issues. The group agreed that known issues for the beta release should be noted within the beta release notes as separate sub-headings, and a concerted effort should be made to make sure that the release notes were referred to in all official, semi-official and unofficial communications regarding the beta release. [[User:Wwoods|Will Woods']] suggestion that this was a job for the <marquee> tag was roundly rejected.
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-03-31. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-31</ref>. The group agreed that too much time was being spent on discussing moving the meeting time and there were too many problems to declare a move, so they agreed to keep to the present time for now.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-03-24. It was a short meeting as several key group members were not able to attend. Matej Cepl reported that he had consolidated his RHEL and Fedora triage and signature scripts into a single Greasemonkey script<ref>http://mcepl.fedorapeople.org/scripts/greasemonkey/bugzillaBugTriage.user.js</ref>. Other topics were deferred to future meetings or the mailing list for lack of a reasonable number of group members to make binding decisions.
The group discussed whether the How to Triage page<ref>https://fedoraproject.org/wiki/User:Beland/How_to_Triage</ref> should stay as a single page or be split up. No broad agreement was reached. Eventually they agreed to focus on finalizing the content before worrying too much about organization. Some revisions to the content of the page were agreed upon, and [[User:Beland|Christopher Beland]] made them.


The next QA weekly meeting will be held on 2009-04-02 at 1600 UTC (note reversion to previous meeting time) in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-01 at 1500 UTC in #fedora-meeting.
The next QA weekly meeting will be held on 2009-04-08 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-07 at 1500 UTC in #fedora-meeting.


<references/>
<references/>


=== Wiki changes ===
=== Anonymous test result reporting ===


The group discussed [[User:Beland|Christopher Beland's]] new How to Triage draft<ref>https://fedoraproject.org/wiki/User:Beland/How_to_Triage</ref>, and Chris made several revisions and improvements. Chris summarized<ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg01105.html</ref> several remaining questions relating to the page, and Adam Williamson<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg01125.html</ref> and [[User:Tk009|Edward Kirk]] provided feedback<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg01110.html</ref>.
Paul Frields reported<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg01225.html</ref> that the infrastucture team had set up a special namespace for future Test Day pages on the Wiki. This namespace allows anonymous editing, so testers will be able to report their results without having to sign up for a FAS account (and so sign the CLA), which some testers were not comfortable with having to do.


<references/>
<references/>


=== Bugzappers meeting schedule  ===
=== New group members ===


[[User:Adamwill|Adam Williamson]] requested<ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg01108.html</ref> a final decision on re-scheduling the Bugzappers group movement, but no final conclusion was yet reached.
Two new members sent introduction emails: Bashir Souid<ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg01253.html</ref> and Gireesh Sreekantan<ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg01259.html</ref>.  
 
<references/>
 
=== Triage Days on the Wiki ===
 
[[User:Adamwill|Adam Williamson]] apologized for the delay, and announced <ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg01129.html</ref> that a Triage Day page was now available on the Wiki, explaining the existence and function of the Bugzappers group's weekly Triage Day.


<references/>
<references/>

Revision as of 22:57, 5 April 2009

QualityAssurance

In this section, we cover the activities of the QA team[1].

Contributing Writer: Adam Williamson

Test Days

This week's first Test Day[1] was on the Radeon driver for ATI video cards, which has seen substantial changes for Fedora 11. The turnout was again excellent and many useful bug reports were filed. The developer present was Dave Airlie, and Adam Williamson and James Laska were present for the QA team. The second Test Day[2] was on power management. There was a good turnout of dedicated Rawhide users, and the results were quite positive: most testers found everything worked and few major bugs were discovered.

Next week's Test Day[3] will be on the UEFI[4] support in Fedora 11. UEFI hardware is not yet widely available, so this Test Day is mostly only of interest to Red Hat QA staff with access to testing hardware.

Weekly meetings

The QA group weekly meeting[1] was held on 2009-04-01. The full log is available[2]James Laska and Adam Williamson reported no progress this week with the Semantic mediawiki extension.

James Laska reported that packaging work on the Semantic extension for Mediawiki was progressing, and one package had already passed review. He also noted that he had created a test Mediawiki instance with the extension enabled, but had not yet been able to do much testing. Adam Williamson confirmed that he also had not had time to do much testing.

Adam Williamson noted that the release notes should cover the known problem with generating live USB images from the Fedora 11 Beta live CD images using Fedora 10, caused by the older version of syslinux it contains. The group agreed to file a bug on this issue and add a note to the release notes, linking to the bug report.

Will Woods and Jesse Keating reported steady progress with autoqa work, and hope to have two hooks - post-repo-update and post-tree-compose - running by next week.

Will Woods brought up the new blog[3] started by Warren Togami to note major issues in Rawhide, and suggested the QA group should propose to work together with Warren on the project.

The Bugzappers group weekly meeting[4] was held on 2009-03-31. The full log is available[5]. The group agreed that too much time was being spent on discussing moving the meeting time and there were too many problems to declare a move, so they agreed to keep to the present time for now.

The group discussed whether the How to Triage page[6] should stay as a single page or be split up. No broad agreement was reached. Eventually they agreed to focus on finalizing the content before worrying too much about organization. Some revisions to the content of the page were agreed upon, and Christopher Beland made them.

The next QA weekly meeting will be held on 2009-04-08 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-07 at 1500 UTC in #fedora-meeting.

Anonymous test result reporting

Paul Frields reported[1] that the infrastucture team had set up a special namespace for future Test Day pages on the Wiki. This namespace allows anonymous editing, so testers will be able to report their results without having to sign up for a FAS account (and so sign the CLA), which some testers were not comfortable with having to do.

New group members

Two new members sent introduction emails: Bashir Souid[1] and Gireesh Sreekantan[2].