From Fedora Project Wiki

< FWN‎ | Beats

(create 191 qa beat)
(create 192 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Last week's main track Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-08-27_Dracut</ref> was on Dracut<ref>http://fedoraproject.org/wiki/Features/ABRT</ref>, the new initrd generation tool. There was a solid turnout of testers and developers. Many cases were tested to work without problems, but some problem cases were identified, and bugs were filed.
Last week's main track Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS</ref> was on Sugar on a Stickthe Fedora-derived USB stick distribution which features the Sugar desktop environment that is the default desktop for the OLPC project. Not too many people showed up to test, but we did get a solid set of results, and this was the first test day to experiment with a new result reporting system based on the Semantic MediaWiki plugin.


Next week's main track Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS</ref> will be on Sugar on a Stick, the Fedora-derived USB stick distribution which features the Sugar desktop environment that is the default desktop for the OLPC project. This Test Day is being led by the Sugar developers. If you're interested in this exciting and innovative desktop environment, please come along and help test it! The testing will be on Sugar on a Stick v2 Beta, which should be available in time for the Test Day. The Test Day will be held on Thursday 2009-09-03 in IRC #fedora-test-day.
This coming week is special from a Test Day perspective: it's Video Test Week! There will be not one but three main track Test Days, one for each of the major video adapter manufacturers. Wednesday 2009-09-09 is ATI/AMD Radeon Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-09_Radeon</ref>. Thursday 2009-09-10 is NVIDIA Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-10_Nouveau</ref>. And last but not least, Friday 2009-09-11 is Intel graphics Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-11_Intel</ref>. As always, graphics drivers are one of the most vital parts of the Fedora experience, and the three main drivers have received their usual round of significant changes since the last release, so we encourage everyone to come out on the appropriate Test Day for their hardware and help test. There will be live images available, so you don't need Rawhide - or even Fedora - installed to test: you just need to show up, download a live image, run some simple tests to see how well the graphics work, and report your results. This will help us immensely to make sure Fedora 12 has good support for as much graphics hardware as possible, so please do come along! Each Test Day will run all day and be held in Freenode IRC #fedora-test-day. If you're not sure how to use IRC, see this page<ref>http://fedoraproject.org/wiki/How_to_use_IRC</ref>.


Next week's Fit and Finish<ref>http://fedoraproject.org/wiki/Fit_and_Finish</ref> project Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-01_Sectool</ref> will be on Sectool<ref>http://fedorahosted.org/sectool</ref>, the security audit and intrusion detection tool. The Fit and Finish team are working throughout the Fedora 12 cycle to file the rough edges off Fedora's desktop experience, so please come along and help them test! The Test Day will be held on Tuesday 2009-09-01 in IRC #fedora-test-day.
Next week's Fit and Finish<ref>http://fedoraproject.org/wiki/Fit_and_Finish</ref> project Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-08_Fit_and_Finish:Sharing</ref> will be on sharing - sharing files, printers, music, and even remote desktop functionality. This area is critical to many users but often overlooked, so please come along to help refine it! The Test Day will be held on Tuesday 2009-09-08 in Freenode IRC #fedora-test-day.


If you would like to propose a main track Test Day for the Fedora 12 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 12 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 22: Line 22:
=== Weekly meetings ===
=== Weekly meetings ===


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-08-24. The full log is available<ref>http://fedoraproject.org/wiki/QA/Meetings/20090824</ref>. [[User:Jlaska|James Laska]] led a post-Alpha release recap (on the assumption the Fedora 12 Alpha would in fact be released on time). The group agreed that the process had been handled quite well. [[User:jkeating|Jesse Keating]] was happy with the level of communication between release engineering and QA. James felt the blocker bug review meetings had gone smoothly and been a positive contribution. [[User:Adamwill|Adam Williamson]] thought the Alpha process had flagged up the need for a better process for filtering Anaconda updates into Fedora. James summarized areas of possible improvement: he felt planned testing could be extended to areas beyond installation. The group agreed, but generally felt that installation was the most important area by a significant margin. James committed to trying to extend the test plan to cover X.org testing for the Fedora 12 Beta release. [[User:Wwoods|Will Woods]] pointed out that basic X functionality was part of the Rawhide acceptance test plan, and suggested that the Rawhide acceptances tests should be considered a prerequisite to the installation testing.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-08-31. The full log is available<ref>http://fedoraproject.org/wiki/QA/Meetings/20090831</ref>. [[User:dpravec|David Pravec]] reported that he had created the test-announce mailing list<ref>http://admin.fedoraproject.org/mailman/listinfo/test-announce</ref> for important QA and BugZappers event announcements.


[[User:Wwoods|Will Woods]] reported on the progress of the AutoQA project. He noted that the automated tests were still running and sending results to the mailing list<ref>http://fedorahosted.org/mailman/listinfo/autoqa-results</ref>. He had fixed bugs in several of the tests, and improved the subject lines of the result emails. He was still engaged in tracing other bugs in the existing tests, and writing documentation for creating tests and hooks. [[User:jkeating|Jesse Keating]] pointed out that a new upstream release of autotest was available, and committed to getting it packaged and made available through the infrastructure team for testing. [[User:Adamwill|Adam Williamson]] asked whether the current state of the project was sufficient for the planned israwhidebroken.com website to be created. Will explained that some bits were still missing, particularly a method for getting data from autotest into the page.
[[User:Jlaska|James Laska]] reported that he had not yet been able to talk to [[User:Liam|Liam Li]] about refining the install test plan to be more achievable within the timeframe for each snapshot release. He had improved the Dracut Test Day test cases. He had also spoken to [[User:Mmcgrath|Mike McGrath]] about the impact of nightly Rawhide images on the resources of alt.fedoraproject.org. Mike had not yet seen or had reported any major problems, but would like to be kept in the loop when new milestones are released. [[User:Adamwill|Adam Williamson]] asked if Infrastructure had any numbers for downloads of the nightly images. James did not know, but would ask.


[[User:dpravec|David Pravec]] proposed creating a fedora-test-announce mailing list for those who wanted to be informed of events such as Test Days, but did not want to follow the traffic of fedora-test-list. [[User:Adamwill|Adam Williamson]] suggested using the list to announce test composes and changes to release schedules. [[User:jkeating|Jesse Keating]] worried about the principle of creating more and more mailing lists, and suggested posting announcements to fedora-devel-announce instead, but [[User:Jlaska|James Laska]] said he had been asked to stop posting Test Day announcements to that list in the past. In the end the group agreed on the proposal, and David took responsibility for creating the list.
[[User:jkeating|Jesse Keating]] reported that he had built the new version of autotest for the AutoQA project to test. [[User:Jlaska|James Laska]] and [[User:Wwoods|Will Woods]] were in progress on testing it, and would report next week.


[[User:Jlaska|James Laska]] asked for an update on Test Day status. [[User:Adamwill|Adam Williamson]] reported that the Fit and Finish team's Printing Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-08-18_Fit_and_Finish:Printing</ref> had gone smoothly, from what he had seen. James linked to his report<ref>http://www.redhat.com/archives/fedora-test-list/2009-August/msg00609.html</ref> on the ABRT Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-08-20_ABRT</ref>, and thanked [[User:dpravec|David Pravec]] and [[User:Kparal|Kamil Paral]] for organizing the event. James also reported on the readiness of the upcoming Dracut Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-08-27_Dracut</ref>.
[[User:Wwoods|Will Woods]] reported on the progress of the AutoQA project. They had spent the week writing documentation, collected in the AutoQA category on the Wiki<ref>http://fedoraproject.org/wiki/Category:AutoQA</ref>. There are pages on how to write hooks and tests for AutoQA, and also pages on how AutoQA and autotest work. Will emphasized that no particular knowledge of how AutoQA itself works is required to write tests and hooks that can be used with it, and it's best to write tests and hooks before worrying about wrapper code to use them in AutoQA. In the coming week, they were planning to work on a method to get data back out of autotest to be used for projects like the israwhidebroken.com site.


[[User:Adamwill|Adam Williamson]] raised the topic of the recently-introduced nightly live builds of Rawhide<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/</ref>, and asked the group to support him in publicising their existence. [[User:jkeating|Jesse Keating]] worried that the limited resources of the server on which they are hosted would be put under serious strain if they become too widely used. This led to another discussion of the best way to distribute regularly updated large images to a mass user base. As usual, no definite answers were discovered. [[User:Kevin|Kevin Fenzi]] wondered if DeltaISOs would help, but Jesse explained they would not, due to the contents of a live image as compared to an installation image (live images essentially contain one large file that is an image of an entire filesystem, while installation images contain individual package files, and hence are much more amenable to having their size reduced by DeltaISOs).
[[User:Jlaska|James Laska]] did a Test Day update. He thanked those who had participated in the Dracut Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-08-27_Dracut</ref>, and promised to send a summary to the mailing list soon. He noted that a sectool Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-09-01_Sectool</ref> was due the day after the meeting. [[User:Adamwill|Adam Williamson]] suggested some potential improvements to the Wiki page, and James asked him to send them to the mailing list so the Test Day organizer, Eduard Beneš, could update the page. The Sugar on a Stick Test Day was due the Thursday after the meeting, and noted that he and [[User:Sdz|Sebastian Dziallas]] were working on getting the page ready, using the new Semantic system for reporting results. Finally, [[User:Adamwill|Adam Williamson]] noted that Graphics Test Week was coming the following week, and he was working on getting the pages created. He expected to be able to re-use many test cases from the Fedora 11 Test Days.


[[User:dpravec|David Pravec]] wanted to improve on the reporting of results of Test Days. He felt that having a results table which was essentially a set of Bugzilla links at the bottom of each Test Day page was unnecessary repetition of work. [[User:Adamwill|Adam Williamson]] pointed out that the results tables for some Test Days contained significantly more information than simply links to bug reports. David's suggestion was to automate the linking of Bugzilla reports to the Test Day Wiki pages in some way. Adam felt this might be theoretically possible, but technically difficult without undesirable significant modifications to Bugzilla. [[User:Jlaska|James Laska]] noted that reporting results to the Wiki pages was only ever intended to be an interim solution, and the group was still officially committed to implementing a proper test case management system, which should render the problem irrelevant. In the meantime, James and Adam were both happy to accept any improvements anyone could propose for the Wiki-based system. David promised to work on providing a practical proposal.
[[User:Kparal|Kamil Paral]] brought up the idea of using zsync<ref>http://zsync.moria.org.uk/</ref> to reduce the download weight of nightly Rawhide live images. [[User:jkeating|Jesse Keating]] and [[User:Adamwill|Adam Williamson]] did not think it would result in much benefit, due to the way Fedora live CDs are implemented (as a single large filesystem image, rather than a set of package files). [[User:Wwoods|Will Woods]] suggested doing some tests to be sure, and Kamil said he would do this.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-08-25. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-08-25/fedora-meeting.2009-08-25-15.06.log.html</ref>. [[User:Adamwill|Adam Williamson]] gave an update on the proposal to add the semantics switchover to the QA team calendar. He noted that the public Google calendar the QA team had run for a short time was now mostly unused and had only been intended as a test. He further noted that the Infrastructure group was still working on providing a project-wide calendaring solution. Niels Haase clarified that he had in mind the short lists of tasks and dates related to specific groups<ref>http://poelstra.fedorapeople.org/schedules/</ref> that are published by the release engineering team. Adam said he could have the switchover added to these Fedora 13 schedules once they were created.
The group discussed the status of the proposed lower process capabilities feature for Fedora 12<ref>http://fedoraproject.org/wiki/Features/LowerProcessCapabilities</ref>. There was general concern that development of this feature was not sufficiently advanced for the current stage of Fedora 12 development. Fenris02 agreed to talk to the feature maintainer to see what could be done to avoid dropping the feature entirely for Fedora 12.


[[User:Rjune|Richard June]] gave an update on the kernel triage project. He had started on his work of triaging wireless related bugs. So far he had found that most reports were either very old, or were valid reports which already included all necessary information and hence did not need to be triaged. [[User:Adamwill|Adam Williamson]] suggested that he continue on wireless bugs for a while, and if the same pattern persisted, try a different kernel component instead. If several kernel components all seemed to be in the same state, the value of continuing with the kernel triage project could be re-evaluated.
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-09-01. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-09-01/fedora-meeting.2009-09-01-15.01.log.html</ref>. [[User:Adamwill|Adam Williamson]] noted that some planned topics could not be discussed, as important people were not present: Brennan Ashton was not available to update on the triage metrics project, and [[User:Rjune|Richard June]] was not present to update on the kernel triage project.


[[User:Tk009|Edward Kirk]] said that he was working on an SOP (standard operating procedure) detailing all aspects of arranging the Bugzappers group meetings, and asked the group if it had particular ideas or suggestions about any part of the process. In general everyone agreed the current process was good and was happy that Edward was working on officially documenting it. Edward promised to submit a draft of the SOP to the mailing list or a future meeting for review.
The group discussed the new test-announce mailing list<ref>http://admin.fedoraproject.org/mailman/listinfo/test-announce</ref>. [[User:Mcepl|Matej Cepl]] suggested that it be added to Gmane<ref>http://www.gmane.org/</ref>. [[User:Adamwill|Adam Williamson]] promised to do this.


[[User:Tk009|Edward Kirk]] suggested having meetbot announce Bugzappers meetings in related channels shortly ahead of the meeting. [[User:Kevin|Kevin Fenzi]] and [[User:Adamwill|Adam Williamson]] worried that this might annoy people, and also considered the dystopian possibilities of a world where all projects announced all their meetings in all relevant channels. The proposal was not taken further.
[[User:Adamwill|Adam Williamson]] brought up the topic of Triage Days, which [[User:Tk009|Edward Kirk]] had put on the agenda with a view to presenting some ideas on improving them. However, Edward was not at the meeting. No-one else had significant ideas on the topic.


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


<references/>
<references/>


=== ABRT Test Day report ===
=== Zsync feasibility ===


[[User:dpravec|David Pravec]] and [[User:Kparal|Kamil Paral]] reported<ref>http://www.redhat.com/archives/fedora-test-list/2009-August/msg00609.html</ref> on the ABRT Test Day held on 2009-08-20, with a list of all bugs reported during the Test Day and their current statuses. They were happy with the success of the Test Day.
As discussed at the meeting, [[User:Kparal|Kamil Paral]] tested<ref>http://kparal.wordpress.com/2009/09/01/zsync-transfer-large-files-efficiently/</ref> the practicality of using zsync<ref>http://zsync.moria.org.uk/</ref> to reduce the size of nightly Rawhide live image downloads. He found that savings of between 30% and 60% were possible when testing the deltas between various nightly images.
 
<references/>
 
=== Installation testing SOP update ===
 
[[User:Liam|Liam Li]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-September/msg00007.html</ref> that he had updated the installation testing SOP draft<ref>http://fedoraproject.org/wiki/User:Liam/Draft_Install_Test_SOP</ref>, with improved instructions on summarizing test results.
 
<references/>
 
=== Test Day summaries ===
 
Test Day summaries for Dracut<ref>http://www.redhat.com/archives/fedora-test-list/2009-September/msg00027.html</ref> and Sectool<ref>http://www.redhat.com/archives/fedora-test-list/2009-September/msg00053.html</ref> were provided by [[User:Jlaska|James Laska]] and Eduard Beneš respectively.
 
<references/>
 
=== Mediawiki Semantic plugin testing ===
 
[[User:Mchua|Mel Chua]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-September/msg00085.html</ref> that he had built a working Mediawiki test instance with the Semantic extension<ref>http://semantic-mediawiki.org/wiki/Semantic_MediaWiki</ref> installed, for the purpose of implementing an improved test result reporting system. He linked to a meeting log<ref>http://meetbot.fedoraproject.org/fedora-qa/2009-09-02/fedora-qa.2009-09-02-14.14.log.html</ref> which documented the implementation. He noted that the upstream project were interested in having Fedora's use of the Semantic system documented, and asked if anyone would be willing to work on this.


<references/>
<references/>

Revision as of 19:53, 4 September 2009

QualityAssurance

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

Contributing Writer: Adam Williamson

Test Days

Last week's main track Test Day[1] was on Sugar on a Stickthe Fedora-derived USB stick distribution which features the Sugar desktop environment that is the default desktop for the OLPC project. Not too many people showed up to test, but we did get a solid set of results, and this was the first test day to experiment with a new result reporting system based on the Semantic MediaWiki plugin.

This coming week is special from a Test Day perspective: it's Video Test Week! There will be not one but three main track Test Days, one for each of the major video adapter manufacturers. Wednesday 2009-09-09 is ATI/AMD Radeon Test Day[2]. Thursday 2009-09-10 is NVIDIA Test Day[3]. And last but not least, Friday 2009-09-11 is Intel graphics Test Day[4]. As always, graphics drivers are one of the most vital parts of the Fedora experience, and the three main drivers have received their usual round of significant changes since the last release, so we encourage everyone to come out on the appropriate Test Day for their hardware and help test. There will be live images available, so you don't need Rawhide - or even Fedora - installed to test: you just need to show up, download a live image, run some simple tests to see how well the graphics work, and report your results. This will help us immensely to make sure Fedora 12 has good support for as much graphics hardware as possible, so please do come along! Each Test Day will run all day and be held in Freenode IRC #fedora-test-day. If you're not sure how to use IRC, see this page[5].

Next week's Fit and Finish[6] project Test Day[7] will be on sharing - sharing files, printers, music, and even remote desktop functionality. This area is critical to many users but often overlooked, so please come along to help refine it! The Test Day will be held on Tuesday 2009-09-08 in Freenode IRC #fedora-test-day.

If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[8].

Weekly meetings

The QA group weekly meeting[1] was held on 2009-08-31. The full log is available[2]. David Pravec reported that he had created the test-announce mailing list[3] for important QA and BugZappers event announcements.

James Laska reported that he had not yet been able to talk to Liam Li about refining the install test plan to be more achievable within the timeframe for each snapshot release. He had improved the Dracut Test Day test cases. He had also spoken to Mike McGrath about the impact of nightly Rawhide images on the resources of alt.fedoraproject.org. Mike had not yet seen or had reported any major problems, but would like to be kept in the loop when new milestones are released. Adam Williamson asked if Infrastructure had any numbers for downloads of the nightly images. James did not know, but would ask.

Jesse Keating reported that he had built the new version of autotest for the AutoQA project to test. James Laska and Will Woods were in progress on testing it, and would report next week.

Will Woods reported on the progress of the AutoQA project. They had spent the week writing documentation, collected in the AutoQA category on the Wiki[4]. There are pages on how to write hooks and tests for AutoQA, and also pages on how AutoQA and autotest work. Will emphasized that no particular knowledge of how AutoQA itself works is required to write tests and hooks that can be used with it, and it's best to write tests and hooks before worrying about wrapper code to use them in AutoQA. In the coming week, they were planning to work on a method to get data back out of autotest to be used for projects like the israwhidebroken.com site.

James Laska did a Test Day update. He thanked those who had participated in the Dracut Test Day[5], and promised to send a summary to the mailing list soon. He noted that a sectool Test Day[6] was due the day after the meeting. Adam Williamson suggested some potential improvements to the Wiki page, and James asked him to send them to the mailing list so the Test Day organizer, Eduard Beneš, could update the page. The Sugar on a Stick Test Day was due the Thursday after the meeting, and noted that he and Sebastian Dziallas were working on getting the page ready, using the new Semantic system for reporting results. Finally, Adam Williamson noted that Graphics Test Week was coming the following week, and he was working on getting the pages created. He expected to be able to re-use many test cases from the Fedora 11 Test Days.

Kamil Paral brought up the idea of using zsync[7] to reduce the download weight of nightly Rawhide live images. Jesse Keating and Adam Williamson did not think it would result in much benefit, due to the way Fedora live CDs are implemented (as a single large filesystem image, rather than a set of package files). Will Woods suggested doing some tests to be sure, and Kamil said he would do this.

The group discussed the status of the proposed lower process capabilities feature for Fedora 12[8]. There was general concern that development of this feature was not sufficiently advanced for the current stage of Fedora 12 development. Fenris02 agreed to talk to the feature maintainer to see what could be done to avoid dropping the feature entirely for Fedora 12.

The Bugzappers group weekly meeting[9] was held on 2009-09-01. The full log is available[10]. Adam Williamson noted that some planned topics could not be discussed, as important people were not present: Brennan Ashton was not available to update on the triage metrics project, and Richard June was not present to update on the kernel triage project.

The group discussed the new test-announce mailing list[11]. Matej Cepl suggested that it be added to Gmane[12]. Adam Williamson promised to do this.

Adam Williamson brought up the topic of Triage Days, which Edward Kirk had put on the agenda with a view to presenting some ideas on improving them. However, Edward was not at the meeting. No-one else had significant ideas on the topic.

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

Zsync feasibility

As discussed at the meeting, Kamil Paral tested[1] the practicality of using zsync[2] to reduce the size of nightly Rawhide live image downloads. He found that savings of between 30% and 60% were possible when testing the deltas between various nightly images.

Installation testing SOP update

Liam Li announced[1] that he had updated the installation testing SOP draft[2], with improved instructions on summarizing test results.

Test Day summaries

Test Day summaries for Dracut[1] and Sectool[2] were provided by James Laska and Eduard Beneš respectively.

Mediawiki Semantic plugin testing

Mel Chua announced[1] that he had built a working Mediawiki test instance with the Semantic extension[2] installed, for the purpose of implementing an improved test result reporting system. He linked to a meeting log[3] which documented the implementation. He noted that the upstream project were interested in having Fedora's use of the Semantic system documented, and asked if anyone would be willing to work on this.