From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 221 qa beat)
(create fwn 288 draft)
 
(61 intermediate revisions by the same user not shown)
Line 3: Line 3:


In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.


Contributing Writer: [[User:Adamwill|Adam Williamson]]
Contributing Writer: [[User:Adamwill|Adam Williamson]]
Line 10: Line 12:
=== Test Days ===
=== Test Days ===


Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-08_Virtualization</ref> was on virtualization<ref>http://fedoraproject.org/wiki/Virtualization</ref>. This was mainly focused on the Fedora virtualization stack, based around KVM, libvirt, and virt-manager. A small band of hardened virtualization testers were able to expose 14 bugs, which the developers are now investigating. Thanks to everyone who came out to help with the testing.
In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization</ref>, another i18n desktop test day on 2011-09-22<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop</ref>, an ABRT test day on 2011-09-26<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT</ref>, a power management test day on 2011-09-29<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement</ref>, printing test day on 2011-10-06<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing</ref>, Fedora packager plugin for Eclipse test day on 2011-10-13<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse</ref>, and Cloud SIG test day on 2011-10-20<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day</ref>. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.
 
The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide<ref>http://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref>, or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki<ref>http://fedoraproject.org/wiki/QA/Test_Days/Create</ref>.
 
<references/>


This week is a big moment in the Test Day schedule: Graphics Test Week. There will be three Test Days focusing on the three major graphics drivers: NVIDIA Test Day on Tuesday 2010-04-13<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-13_Nouveau</ref>, ATI/AMD Test Day on Wednesday 2010-04-14<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-14_Radeon</ref>, and Intel graphics Test Day on Thursday 2010-04-15<ref>http://fedoraproject.org/wiki/Test_Day:2010-04-15_Intel</ref>. As always, widespread graphics testing is critical to the development of these drivers. Around 75% of all bugs reported in the last Graphics Test Week have been closed (either as fixed, or as duplicates), so the information gathered isn't ignored! Testing can be done with a live image, so there's no need to have an unstable Fedora installation to do the testing, and the tests are easy to do and come with full instructions. Almost everyone has an NVIDIA, AMD/ATI or Intel graphics adapter, so please come out to help us test! The events will take place all day in the #fedora-test-day channel on Freenode IRC (if you're not sure how to use IRC, there's an instruction page<ref>http://fedoraproject.org/wiki/How_to_use_IRC</ref>, or you can use WebIRC<ref>http://webchat.freenode.net/?channels=fedora-test-day</ref>. If you can't make it on the day, you can still provide your results on the Wiki page before or after the event.
=== Fedora 16 preparation ===


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>.
As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.


<references/>
<references/>


=== Fedora 13 testing ===
=== Release criteria updates ===


This week saw the group wrap up Fedora 13 Beta validation testing. After the previous week's delay, the fourth<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089919.html</ref> and fifth<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089962.html</ref> release candidate builds for the Beta arrived during the week. Installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC4_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC4_Desktop</ref> validation testing for the RC4 build were both broadly successful, but [[User:Adamwill|Adam Williamson]] realized that the build included a critical bug which would cause systems containing a certain common network adapter to be unable to boot<ref>http://bugzilla.redhat.com/show_bug.cgi?id=577463</ref>, so the RC5 build provided an updated kernel to fix that issue. Adam posted a call for testing of the updated kernel<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089944.html</ref> which drew an overwhelming response, with dozens of group members confirming the kernel worked on their systems. The group re-ran the validation tests<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC5_Install</ref>, and subsequently agreed with the development and release engineering groups at the go/no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-04-08/f-13-beta-eng-readiness.2010-04-08-00.01.html</ref> that the RC5 build met all the release criteria<ref>http://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria</ref> and so was suitable for release as Fedora 13 Beta. [[User:Rhe|Rui He]] summarized the validation test results<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090015.html</ref> and encouraged more group members to be involved in the validation testing for future releases.
Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, [[User:Adamwill|Adam Williamson]] reported that he had committed his proposed modifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html</ref>. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html</ref>.
 
Adam also passed on a suggestion from [[User:Pjones|Peter Jones]] to improve the clarity of the virtualization criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html</ref>. After an extensive discussion, an elegant wording suggestion from Albert Graham<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html</ref> was eventually accepted and committed<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html</ref>.
 
[[User:Tflink|Tim Flink]] raised the question to what extent support for Xen virtualization should be included in the release criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html</ref>. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html</ref>.
 
Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html</ref>.
 
Finally, Adam proposed a criterion for i18n (translation) issues<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html</ref>. After discussion, the proposal was agreed upon at a blocker review meeting later in the week<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html</ref>.


<references/>
<references/>


=== Testing non-English keyboard layouts ===
=== Update policy changes ===


Petri Laine reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089995.html</ref> that he had experienced problems using a non-default keyboard mapping in Fedora 13 Beta RC5. [[User:Adamwill|Adam Williamson]] replied<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089998.html</ref> that similar bugs had occurred during previous release periods, and then announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090001.html</ref> that he had extended an installation validation test case<ref>http://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28encrypted%29_install</ref> and created a desktop validation test case<ref>http://fedoraproject.org/wiki/QA:Testcase_desktop_login</ref> to try to ensure that similar issues are caught in future testing rounds. Petri appended his report to an existing bug report<ref>http://bugzilla.redhat.com/show_bug.cgi?id=571900</ref> and followed up on the problem there.
In September, [[User:Karsten|Karsten Hopp]] raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html</ref>. [[User:Adamwill|Adam Williamson]] explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html</ref>. [[User:Cra|Chuck Anderson]] noted that he had the update in question installed, but was struggling for lack of information on how to test it properly<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html</ref>. [[User:Sundaram|Rahul Sundaram]] suggested that Karsten file a ticket with FESCo to raise the issue<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html</ref>, and Karsten did<ref>http://fedorahosted.org/fesco/ticket/664</ref>.
 
That ticket was merged with another similar one reported by Doug Ledford<ref>http://fedorahosted.org/fesco/ticket/667</ref>, which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed<ref>http://fedorahosted.org/bodhi/ticket/642</ref>, and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester<ref>http://fedorahosted.org/fesco/ticket/667#comment:26</ref>, effectively a proposal to end the proven tester system, as this is the only function it serves.
 
The QA group discussed this proposal at the weekly meeting of 2011-11-07<ref>http://fedoraproject.org/wiki/QA/Meetings/20111107</ref>, agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.


<references/>
<references/>


=== Ensuring packages are signed ===
=== Update candidate notification ===


[[User:Jlaska|James Laska]] proposed<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090025.html</ref> a new release criterion and validation test to ensure that all packages are signed with a valid Feora GPG signature. [[User:Notting|Bill Nottingham]] pointed out<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090026.html</ref> that this would not slot easily into the existing package release workflow. He also noted that Bodhi is supposed to reject un-signed packages. [[User:jkeating|Jesse Keating]] explained<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090028.html</ref> that this was a mash configuration option which had been disabled intentionally for initial Branched composes as some packages were known not to be signed at that time. Bill ultimately suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/090032.html</ref> that the signature check should be re-enabled in the relevant mash configurations.
Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html</ref>. There were no takers for the second question, but for the first, [[User:Adamwill|Adam Williamson]] suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html</ref>, and [[User:till|Till Maas]] pointed out that Bodhi can actually provide per-package RSS notifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html</ref>.


<references/>
<references/>


=== Bugzappers screencasts ===
=== Proven tester meetings ===
 
As a response to the concerns about candidate updates not receiving enough karma, [[User:Kevin|Kevin Fenzi]] ran a series of weekly proven tester meetups<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html</ref> from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html</ref>.


At the weekly Bugzappers meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-04-06/fedora-meeting.2010-04-06-15.00.log.html</ref>, [[User:Adamwill|Adam Williamson]] noted that he had not yet forwarded [[User:Shakthimaan|Shakthi Kannan's]] suggestion of making Bugzapping screencasts to the mailing list. The next day, he did so<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/089972.html</ref>. [[User:etank|Eric Lake]], [[User:campbecg|Chris Campbell]] and James Gledhill all posted in support of the idea, but no-one yet had the combination of free time and expertise to make the screencasts.
Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html</ref>. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.


<references/>
<references/>


=== AutoQA ===
=== QA group representation at FUDCon Pune ===


With Fedora 13 validation testing winding down, work on AutoQA was picking up steam again, with the team working on dependency checking<ref>http://fedorahosted.org/autoqa/milestone/autoqa depcheck</ref>, tests<ref>http://fedorahosted.org/autoqa/milestone/Package%20Sanity%20Tests</ref> to implement the Package Sanity Test Plan<ref>http://fedoraproject.org/wiki/QA:Package_Sanity_Test_Plan</ref>, the results database idea<ref>http://fedorahosted.org/autoqa/milestone/Resultdb</ref> and the automated installation test plan<ref>http://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan</ref>.
[[User:Ankursinha|Ankur Sinha]] asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html</ref>. [[User:Adamwill|Adam Williamson]] replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html</ref>. A S Alam then stepped up to volunteer to lead a QA session<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html</ref>. His session was scheduled for 2011-11-04<ref>http://fudcon.in/sessions/fedora-testing</ref>, but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!


<references/>
<references/>

Latest revision as of 05:10, 17 November 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].

We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.

Contributing Writer: Adam Williamson

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

Test Days

In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September[1] ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15[2], another i18n desktop test day on 2011-09-22[3], an ABRT test day on 2011-09-26[4], a power management test day on 2011-09-29[5], printing test day on 2011-10-06[6], Fedora packager plugin for Eclipse test day on 2011-10-13[7], and Cloud SIG test day on 2011-10-20[8]. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.

The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide[9], or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki[10].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization
  3. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop
  4. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT
  5. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement
  6. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing
  7. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse
  8. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day
  9. ↑ http://fedoraproject.org/wiki/QA/SOP_Test_Day_management
  10. ↑ http://fedoraproject.org/wiki/QA/Test_Days/Create

Fedora 16 preparation

As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.


Release criteria updates

Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, Adam Williamson reported that he had committed his proposed modifications[1]. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards[2].

Adam also passed on a suggestion from Peter Jones to improve the clarity of the virtualization criteria[3]. After an extensive discussion, an elegant wording suggestion from Albert Graham[4] was eventually accepted and committed[5].

Tim Flink raised the question to what extent support for Xen virtualization should be included in the release criteria[6]. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion[7].

Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage[8].

Finally, Adam proposed a criterion for i18n (translation) issues[9]. After discussion, the proposal was agreed upon at a blocker review meeting later in the week[10].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html
  8. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html
  9. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html
  10. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html

Update policy changes

In September, Karsten Hopp raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time[1]. Adam Williamson explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group[2]. Chuck Anderson noted that he had the update in question installed, but was struggling for lack of information on how to test it properly[3]. Rahul Sundaram suggested that Karsten file a ticket with FESCo to raise the issue[4], and Karsten did[5].

That ticket was merged with another similar one reported by Doug Ledford[6], which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed[7], and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester[8], effectively a proposal to end the proven tester system, as this is the only function it serves.

The QA group discussed this proposal at the weekly meeting of 2011-11-07[9], agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html
  5. ↑ http://fedorahosted.org/fesco/ticket/664
  6. ↑ http://fedorahosted.org/fesco/ticket/667
  7. ↑ http://fedorahosted.org/bodhi/ticket/642
  8. ↑ http://fedorahosted.org/fesco/ticket/667#comment:26
  9. ↑ http://fedoraproject.org/wiki/QA/Meetings/20111107

Update candidate notification

Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system[1]. There were no takers for the second question, but for the first, Adam Williamson suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository[2], and Till Maas pointed out that Bodhi can actually provide per-package RSS notifications[3].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html

Proven tester meetings

As a response to the concerns about candidate updates not receiving enough karma, Kevin Fenzi ran a series of weekly proven tester meetups[1] from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives[2] [3] [4] [5] [6].

Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing[7]. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html

QA group representation at FUDCon Pune

Ankur Sinha asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities[1]. Adam Williamson replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself[2]. A S Alam then stepped up to volunteer to lead a QA session[3]. His session was scheduled for 2011-11-04[4], but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html
  4. ↑ http://fudcon.in/sessions/fedora-testing
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=261435"