From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 01:57, 26 October 2009 by Adamwill (talk | contribs) (create 199 qa beat)

QualityAssurance

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

Contributing Writer: Adam Williamson

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

Test Days

Last week's first Test Day[1] was on the confined SELinux users feature. The modest turnout of testers managed to run through nearly the whole set of tests and expose several bugs to help refine the feature. The second Test Day[2] was on power management[3] improvements in Fedora 12. A good turnout of testers ran the carefully prepared test suite on an even wider array of machines, providing valuable data for the developers.

Next week's Test Day[4], the last of the Fedora 12 cycle, will be on internationalization (also known as i18n)[5] - an event which usually has a strong focus on input methods, but can also cover issues like fonts. This Test Day was previously scheduled for 2009-10-15 but was postponed, this is the new date. The Test Day will run all day on Thursday 2009-10-29 in the #fedora-test-day IRC channel. Please come along and help ensure Fedora works just as well no matter what language you use!

No Fit and Finish track Test Day is planned for next week.

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

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-20
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-22
  3. ↑ https://fedoraproject.org/wiki/Features/PowerManagementF12
  4. ↑ https://fedoraproject.org/wiki/Test_Day:2009-10-29
  5. ↑ http://fedoraproject.org/wiki/I18N
  6. ↑ http://fedorahosted.org/fedora-qa/

Weekly meetings

The QA group weekly meeting[1] was held on 2009-10-19. The full log is available[2]. James Laska followed up on concerns raised at the last meeting by Jesse Keating that blocker bugs may not be being identified fast enough. James noted that research by himself and Adam Williamson indicated almost all issues had been escalated within two days of being identified, which he felt was a good record.

James Laska had also investigated the packaging of the israwhidebroken.com project code. He found it was very easy to build a package since the code used Python setuptools. He also reported that he had requested the creation of a public autoqa-devel mailing list for the AutoQA project[3].

James Laska initiated a review of the Beta testing process. Liam Li was thinking about ways to get 100% installation test case coverage, or at least improve the coverage to all tier 2 tests. James was pleased that all tier 1 tests had been covering during the Beta test process. James asked whether it would be possible to reduce the number of tests in the matrix. Liam was not sure whether that would actually reduce release quality. James suggested looking for potential duplication of cases in the matrix. Adam Williamson wondered if it would be possible to generate a version of the matrix showing only uncompleted tests, so it would be clearer which tests still needed to be performed. James pointed out that the matrix could already be sorted. Adam had not considered that possibility, and suggested that it be explained in Liam's test request emails. Ben Williams pointed out the Fedora Unity test matrix[4], and James suggested merging the two together. Will Woods discussed the possibility of integrating the AutoQA installation test results; he said it would be simpler to just have a link to an external AutoQA results page, but having the AutoQA system insert results into a Wiki page would be possible.

Will Woods and Kamil Paral reported on the progress of the AutoQA project. Will had been working on getting the production AutoQA instance up and running. He had given up on the idea of having israwhidebroken.com link back to detailed test results, instead planning to provide a page explaining where to find the results. This means israwhidebroken.com can go up as soon as the production AutoQA instance is running. Beyond this, Will has been working on a hook for Koji, which will allow AutoQA to trigger on new builds in Koji. A preliminary version of this code is available[5]. Kamil had continued work on his script to monitor important changes in packages, now renamed 'rpmguard'. It is now maintained in AutoQA git[6]. He had created test packages to make sure the script works as intended, and now is looking for feedback from a wider test audience. He planned to write a blog post to try and trigger people to test and provide feedback on the script. He was also looking for suggestions for the best possible output format for the tool.

Jóhann Guðmundsson and Adam Williamson updated the status of the project to revise debugging-related pages. Richard June had helped out by starting work on an alternative template page[7]. Adam felt it should be possible to come up with a template which would standardize the layout of such pages while still providing enough flexibility to cover different components, but he had not yet had enough time to try and work on this himself. He emphasized that no-one should wait on the planned template before revising pages to fit the new format and naming scheme. James Laska volunteered to work on renaming all existing pages to fit the new naming scheme.

Jesse Keating asked the group to help review tag requests for the final release. He noted there was no formal set of requirements for tag requests for critical path packages, but asked reviewers to be sensible in judging whether the change was safe and genuinely necessary. Requests should explain what issue the updated package fixes, why it needs to be fixed, and the likely impact if it is not fixed. He provided an RSS feed[8] to monitor tickets as they come in.

Adam Williamson asked the group to help develop the Fedora 12 Common Bugs page[9] by adding issues to it and marking bugs which should be added to it with the CommonBugs keyword. James Laska provided a search URL[10] for listing bug reports marked as needing to be added to a Common Bugs page.

The Bugzappers group weekly meeting[11] was held on 2009-10-20. The full log is available[12]. Richard June reported on the progress of the kernel triage project. He had found more bugs that required further information, and was working with John Linville to ensure his process for getting more information on these reports was correct.

Adam Williamson provided an update on the debugging page revision project, recapping the discussion from the previous day's QA meeting.

Edward Kirk made a suggestion for a Triage Day event. He suggested a day to review all remaining open Fedora 10 bugs, trying to close reports that can be closed and rebase others to later Fedora releases if possible and necessary. The group liked the idea, and there was general agreement on Friday 2009-10-30 at 15:00 UTC as the date and time. Edward promised to announce the event on the mailing list ahead of time.

Brennan Ashton updated the status of the triage metrics project. He had not had time to work on it since his last update. He had tried to find someone to help maintain the project, but had not yet been successful. However, he had the upcoming week off and would try to produce a summary of the current state of the project to make it easier to find other maintainers. Adam Williamson and Edward Kirk were eager to try and help move the project forward.

Steven Parrish asked if any other group members would be at the upcoming FUDCon Toronto event[13]. Adam Williamson said that he and the rest of the Red Hat Fedora QA team would be there. Steven and Adam noted that limited funding was available for community members to attend the event, and explained that those wanting funding should add their name to the attendee list and check the column for funding. Brennan Ashton asked if anyone else would be driving from Boston. Adam pointed out that there was a group bus[14] being organized.

The next QA weekly meeting will be held on 2009-10-26 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-10-27 at 1500 UTC in #fedora-meeting.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-19/fedora-meeting.2009-10-19-15.58.log.html
  3. ↑ https://fedorahosted.org/fedora-infrastructure/ticket/1733
  4. ↑ http://spins.fedoraunity.org/Members/Southern_Gentleman/Fedora%2012%20%20beta%20TestMatrix
  5. ↑ https://fedorahosted.org/autoqa/browser/hooks/post-koji-build/watch-koji-builds.py
  6. ↑ http://git.fedorahosted.org/git/autoqa.git?a=tree;f=tests/rpmguard
  7. ↑ http://fedoraproject.org/wiki/Template:How_to_debug2
  8. ↑ https://fedorahosted.org/rel-eng/timeline?ticket=on&changeset=on&milestone=on&wiki=on&max=50&daysback=90&format=rss
  9. ↑ http://fedoraproject.org/wiki/Common_F12_bugs
  10. ↑ http://tinyurl.com/l4kma5
  11. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  12. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-20/fedora-meeting.2009-10-20-15.10.log.html
  13. ↑ http://fedoraproject.org/wiki/FUDCon:Toronto_2009
  14. ↑ http://fedoraproject.org/wiki/FUDCon:Toronto_2009#Bus_Travel

Fedora 12 Beta release

Of course, the week's big news was the release of Fedora 12 Beta[1]. This prompted several threads[2] [3] [4] [5] (and more) from enthusiastic testers, with valuable experiences which Adam Williamson encouraged to be turned into bug reports.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00393.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00453.html
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00458.html
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00486.html
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00493.html

Confined users Test Day summary

Eduard Benes provided a summary[1] of the SELinux confined users Test Day[2], listing the bug reports resulting from the Test Day and thanking the testers and also Dan Walsh, who had already begun resolving reported bugs.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00488.html
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-20

Fedora 12 blocker bug review meeting

Adam Williamson provided a recap[1] of the blocker bug review meeting which took place on Friday 2009-10-23, linking to a report[2] of the meeting which lists the status and actions decided for all 51 blocker bugs reviewed during the course of the meeting. He thanked all those who attended for their help in reviewing the large load of bugs.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00579.html
  2. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-23/fedora-bugzappers.2009-10-23-15.00.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=132432"