From Fedora Project Wiki

< FWN‎ | Beats

(Typo)
(fwn 209 beat)
Line 16: Line 16:
=== Weekly meetings ===
=== Weekly meetings ===


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-01-04. The full logs are available<ref>http://fedoraproject.org/wiki/QA/Meetings/20100104</ref>. [[User:Jlaska|James Laska]] reported that had finished his list of recommendations based on the Fedora 12 retrospective, and it was available on the wiki<ref>http://fedoraproject.org/wiki/Fedora_12_QA_Retrospective#Recommendations</ref>.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-01-11. The full logs are available<ref>http://fedoraproject.org/wiki/QA/Meetings/20100111</ref>. [[User:maxamillion|Adam Miller]] reported that he had begun working with [[User:Cwickert|Christoph Wickert]] and [[User:Kevin|Kevin Fenzi]] to plan the Fedora 13 Xfce test day. They had started a new mailing list for Xfce issues and discussed whether to commit to including Xfce 4.8 in Fedora 13.


[[User:Adamwill|Adam Williamson]] gave an update on the privilege escalation policy topic. He had escalated the issue to FESCo with a trac ticket<ref>http://fedorahosted.org/fesco/ticket/297</ref>. FESCo had not yet discussed the topic at a meeting or responded to the ticket.
[[User:Johannbg|Jóhann Guðmundsson]] had agreed with [[User:Cwickert|Christoph Wickert]] that a Fedora 13 LXDE test day would be a useful event. He promised to work on writing test cases and picking a date for the test day. He also suggested an LXDE mailing list may be a good idea.


[[User:Jlaska|James Laska]] reported that he, [[User:Adamwill|Adam Williamson]], [[User:Liam|Liam Li]], and [[User:Rhe|Rui He]] had attended a sprint meeting the previous week to work on open tickets for improving Fedora 13 test plans. He referenced the list of tickets which still remained open<ref>http://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&component=Test+Review&milestone=Fedora+13&order=priority</ref>. He also noted that he and Adam would be working on kicking off the Fedora 13 test day process soon. [[User:Johannbg|Jóhann Guðmundsson]] said he would be looking at the possibility of an LXDE test day, and [[User:maxamillion|Adam Miller]] said he would work on a proposal for the XFCE test day.
[[User:Jlaska|James Laska]] said he had spoken to [[MatthiasClasen|Matthias Clasen]] about the possibility of Fit'n'Finish test days for the Fedora 13 cycle, but Matthias thought this would likely not happen. James had also added some ideas about test days for the Fedora 13 cycle to the wiki talk page<ref>http://fedoraproject.org/wiki/Talk:QA/Fedora_13_test_days</ref>.


The group then discussed the list of recommendations<ref>http://fedoraproject.org/wiki/Fedora_12_QA_Retrospective#Recommendations</ref> [[User:Jlaska|James Laska]] had developed based on the feedback received from the Fedora 12 cycle. [[User:Adamwill|Adam Williamson]] volunteered to work with [[User:Rhe|Rui He]] on adding installation testing to the wiki list of QA project activities. [[User:Johannbg|Jóhann Guðmundsson]] said he would look through the Fedora 13 feature list and see if useful debugging guides could be written for any of the new features, similar to the page he wrote for Dracut<ref>http://fedoraproject.org/wiki/How_to_debug_Dracut_problems</ref> in the Fedora 12 cycle. Adam was in the middle of creating a desktop validation test plan (for confirming that releases meet the desktop release criteria). On the topic of creating an X.org test plan, Adam felt that a test plan was unnecessary as the question of what to test for X.org was a simple one, while all the complexity lay in getting enough testing done on a wide enough range of hardware. James, Will and [[User:Kparal|Kamil Paral]] were working on the packaging necessary for the deployment of the israwhidebroken.com project. Will and Kamil were working on an initial implementation of automated package sanity testing. [[User:Liam|Liam Li]] and Rui He were working on automating as many of the installation validation tests as possible. James noted that he planned to bring the installation testing SOP<ref>http://fedoraproject.org/wiki/User:Liam/Draft_Install_Test_SOP</ref> and blocker bug meeting SOP<ref>http://fedoraproject.org/wiki/User:Poelstra/blocker_bug_meeting_sop</ref> out of draft status. He also suggested having an SOP to determine whether to document issues as common bugs, release notes, install guide items or in other ways.
James had also posted a request to the mailing lists<ref>http://lists.fedoraproject.org/pipermail/devel/2010-January/043856.html</ref> for reviews of packages needed for the AutoQA project, but he was still looking for people to review the packages.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2010-01-05. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-01-05/fedora-meeting.2010-01-05-15.05.log.html</ref>. The group discussed [[User:Hdia|Hamidou Dia's]] proposal to document the procedure for determining assignees for components where the correct assignee is not defined in Bugzilla's database. After much discussion, the group tentatively concluded that in cases where the choice of assignee is straightforward this should be fixed in Bugzilla's database, and in cases where it is not straightforward, the components wiki page is not well-suited to explaining the procedure.
[[User:Wwoods|Will Woods]] gave an update on the AutoQA project. He had been filing tickets to plan out future work on automated installation testing, organized under a milestone<ref>http://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan</ref>. However, the next priority was to work on dependency check tests, organized under another milestone<ref>http://fedorahosted.org/autoqa/milestone/autoqa%20depcheck</ref>. This requires the creation of a post-bodhi-update hook; Will had been working with [[User:Lmacken|Luke Macken]] to decide on the best method of doing this. He also noted that rpmguard had now been merged into AutoQA's master branch. [[User:Kparal|Kamil Paral]] noted that he had written a blog post<ref>http://kparal.wordpress.com/2010/01/11/rpmguard-a-wiki-page-and-a-new-output-format/</ref> on the recent changes to rpmguard and the creation of an rpmguard wiki page<ref>http://fedorahosted.org/autoqa/wiki/rpmguard</ref>. He was now thinking about how to improve rpmguard's reporting method. [[User:Jlaska|James Laska]] provided an update on the status of packaging the AutoQA components into Fedora: autotest-client is awaiting review<ref>http://bugzilla.redhat.com/show_bug.cgi?id=548522</ref>, autoqa and autotest are packaged, and he is working on a plan for packaging gwt, which has a large amount of Java dependencies. He was considering having a sprint to work on that.


[[User:campbecg|Chris Campbell]] had suggested that the wiki page on capturing stack traces<ref>http://fedoraproject.org/wiki/StackTraces</ref> should be updated further to reflect the capabilities of abrt, which was introduced in Fedora 12. The group agreed that this was a good idea and agreed that [[User:Adamwill|Adam Williamson]] should contact Chris and ask him to make his proposed changes.
There was no BugZappers meeting during the week due to the absence of several members.


[[User:campbecg|Chris Campbell]] had also proposed an agenda item about the handling by Bugzilla of bugs with many duplicates, but no-one present at the meeting was sure exactly what the issue was. The group agreed to table the item until Chris could explain the issue more clearly.
<references/>
 
=== X.org update testing request ===


Juan P. Daza noted that the wiki's list of active triagers<ref>http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref> may be somewhat out of date, missing some new triagers and listing some who have become inactive. The group agreed that Juan could work on contacting apparently inactive triagers and proposing an update to the list.
[[User:Adamwill|Adam Williamson]] asked the group<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087886.html</ref> to make a special effort to test several new X.org and graphics-related candidate updates, due to the significant impact they could have if approved as stable updates. Many group members responded with valuable feedback, which helped the X developers promote the updates to stable status with confidence.


<references/>
<references/>


=== Improved preupgrade test case ===
=== Desktop validation testing update ===


[[User:Rhe|Rui He]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-December/msg00338.html</ref> that she had created a new test case for preupgrade<ref>http://fedoraproject.org/wiki/QA:Testcase_Preupgrade_low_/boot_disk_space</ref> to better reflect the commonly-encountered real-world situation where multiple kernels are installed on the system to be upgraded, resulting in low space in the /boot partition. This test case should mean problems in this scenario, as encountered by many Fedora 11 users when trying to upgrade to Fedora 12, will be caught earlier in the testing process. Rui He asked for the group's help in reviewing the new test case.
[[User:Adamwill|Adam Williamson]] updated the status of the desktop validation testing project: he had now created a draft test matrix<ref>http://fedoraproject.org/wiki/User:Adamwill/Draft_desktop_test_matrix</ref> to organize desktop validation testing for the Fedora 13 cycle, and asked for the group's comments on it, and opinions on whether it should be merged with the installation testing matrix, or made into a separate page. [[User:Rhe|Rui He]] thought<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087939.html</ref> it should be a separate page. [[User:Jlaska|James Laska]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087944.html</ref> separate pages with a read-only master page which would transclude the separate pages.


<references/>
<references/>


=== Translation checking collaboration with localization team ===
=== Contact with Symbian QA group ===


[[User:Noriko|Noriko Mizumoto]] informed the group<ref>http://www.redhat.com/archives/fedora-test-list/2009-December/msg00352.html</ref> of the localization team's plan to do periodic checks of its translations in a 'real-world' situation, by testing a current Rawhide live image and checking for translation problems. She asked the QA team to assist by providing the live images for testing. [[User:Adamwill|Adam Williamson]] thanked her for co-ordinating with the QA team, and pointed out<ref>http://www.redhat.com/archives/fedora-test-list/2009-December/msg00355.html</ref> that the already available nightly live images<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/</ref> should be suitable for testing. He also suggested that QA team members with knowledge of languages other than English could help in the translation checking process.
Symbian's Mike Kinghan asked<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087942.html</ref> if the group was interested in helping Symbian's fledgling community QA group with the benefit of its immense wisdom and experience. Once the laughter had died down, [[User:Johannbg|Jóhann Guðmundsson]] suggested that Mike could post his questions to the list for feedback from all group members, and/or contact [[User:Adamwill|Adam Williamson]], the community QA lead.


<references/>
<references/>


=== Desktop validation test cases ===
=== Updated gnome-shell available for testing ===


[[User:Adamwill|Adam Williamson]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2010-January/msg00055.html</ref> that he had completed an initial set of desktop validation test cases<ref>http://fedoraproject.org/wiki/Category:Desktop_Acceptance_Test_Cases</ref> to be used in checking if Fedora releases and pre-releases meet the appropriate desktop release criteria. He welcomed the group's help in reviewing these test cases.
[[User:maxamillion|Adam Miller]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087958.html</ref> that he had updated Rawhide's gnome-shell package to a recent upstream git snapshot, and asked the group to help test it and send feedback and bug reports upstream to the GNOME project.


<references/>
<references/>

Revision as of 07:20, 16 January 2010

QualityAssurance

In this section, we cover the activities of the QA team[1], as the QA group and the Fedora project in general awaken from its holiday slumber!

Contributing Writer: Adam Williamson

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

Test Days

There was no Test Day last week, and no Test Day is currently planned for this 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[1].

  1. ↑ http://fedorahosted.org/fedora-qa/

Weekly meetings

The QA group weekly meeting[1] was held on 2010-01-11. The full logs are available[2]. Adam Miller reported that he had begun working with Christoph Wickert and Kevin Fenzi to plan the Fedora 13 Xfce test day. They had started a new mailing list for Xfce issues and discussed whether to commit to including Xfce 4.8 in Fedora 13.

Jóhann Guðmundsson had agreed with Christoph Wickert that a Fedora 13 LXDE test day would be a useful event. He promised to work on writing test cases and picking a date for the test day. He also suggested an LXDE mailing list may be a good idea.

James Laska said he had spoken to Matthias Clasen about the possibility of Fit'n'Finish test days for the Fedora 13 cycle, but Matthias thought this would likely not happen. James had also added some ideas about test days for the Fedora 13 cycle to the wiki talk page[3].

James had also posted a request to the mailing lists[4] for reviews of packages needed for the AutoQA project, but he was still looking for people to review the packages.

Will Woods gave an update on the AutoQA project. He had been filing tickets to plan out future work on automated installation testing, organized under a milestone[5]. However, the next priority was to work on dependency check tests, organized under another milestone[6]. This requires the creation of a post-bodhi-update hook; Will had been working with Luke Macken to decide on the best method of doing this. He also noted that rpmguard had now been merged into AutoQA's master branch. Kamil Paral noted that he had written a blog post[7] on the recent changes to rpmguard and the creation of an rpmguard wiki page[8]. He was now thinking about how to improve rpmguard's reporting method. James Laska provided an update on the status of packaging the AutoQA components into Fedora: autotest-client is awaiting review[9], autoqa and autotest are packaged, and he is working on a plan for packaging gwt, which has a large amount of Java dependencies. He was considering having a sprint to work on that.

There was no BugZappers meeting during the week due to the absence of several members.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://fedoraproject.org/wiki/QA/Meetings/20100111
  3. ↑ http://fedoraproject.org/wiki/Talk:QA/Fedora_13_test_days
  4. ↑ http://lists.fedoraproject.org/pipermail/devel/2010-January/043856.html
  5. ↑ http://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan
  6. ↑ http://fedorahosted.org/autoqa/milestone/autoqa%20depcheck
  7. ↑ http://kparal.wordpress.com/2010/01/11/rpmguard-a-wiki-page-and-a-new-output-format/
  8. ↑ http://fedorahosted.org/autoqa/wiki/rpmguard
  9. ↑ http://bugzilla.redhat.com/show_bug.cgi?id=548522

X.org update testing request

Adam Williamson asked the group[1] to make a special effort to test several new X.org and graphics-related candidate updates, due to the significant impact they could have if approved as stable updates. Many group members responded with valuable feedback, which helped the X developers promote the updates to stable status with confidence.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-January/087886.html

Desktop validation testing update

Adam Williamson updated the status of the desktop validation testing project: he had now created a draft test matrix[1] to organize desktop validation testing for the Fedora 13 cycle, and asked for the group's comments on it, and opinions on whether it should be merged with the installation testing matrix, or made into a separate page. Rui He thought[2] it should be a separate page. James Laska suggested[3] separate pages with a read-only master page which would transclude the separate pages.

  1. ↑ http://fedoraproject.org/wiki/User:Adamwill/Draft_desktop_test_matrix
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2010-January/087939.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2010-January/087944.html

Contact with Symbian QA group

Symbian's Mike Kinghan asked[1] if the group was interested in helping Symbian's fledgling community QA group with the benefit of its immense wisdom and experience. Once the laughter had died down, Jóhann Guðmundsson suggested that Mike could post his questions to the list for feedback from all group members, and/or contact Adam Williamson, the community QA lead.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-January/087942.html

Updated gnome-shell available for testing

Adam Miller announced[1] that he had updated Rawhide's gnome-shell package to a recent upstream git snapshot, and asked the group to help test it and send feedback and bug reports upstream to the GNOME project.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2010-January/087958.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=146052"