FWN/Beats/QualityAssurance: Difference between revisions

Revision as of 22:06, 5 March 2010

QualityAssurance

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

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

Test Days

Last week's planned Test Day on the use of SSSD by default^[1] unfortunately had to be postponed. The new date will be announced in FWN when it is decided.

Next week's Test Day^[2] will be on webcams. Well, that's simple! We like webcams. We want them to work. If your webcam works, we would like to know this so we can celebrate and bask in the warm, contented glow. If your webcam does not work, this makes us very sad and we would like to make it work. So, if you have a webcam, please come along, run a few simple tests, and if it doesn't work, we'll do our best to change that! Testing will be very easy and you'll be able to use a live CD or an installed Fedora system to test. The Test Day will run all day on Thursday 2010-03-11 in the #fedora-test-day IRC channel.

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^[3].

Weekly meetings

The QA group weekly meeting^[1] was held on 2010-03-01. The full logs are available^[2]. Adam Miller reported back on his proposal for managing membership of the QA group in FAS. He had created a draft proposal^[3] and started a mailing list thread^[4] on the topic. James Laska thanked him for his work. Edward Kirk wondered about the mentoring proposal, asking if mentors were already lined up. Adam said that was not yet arranged. He thought that any existing member of the group could be a potential mentor, and new members could be handled on a case-by-case basis. James asked if some groups document mentor responsibilities; Adam replied that he was not sure. They agreed to revisit the topic next week after further follow-up discussion on the mailing list.

James Laska reported that he and Adam Miller had forgotten to contact the sectool team regarding the security spin QA proposal, but would do so immediately following the meeting.

James Laska noted that the fourth Alpha release candidate build was now available for testing, and linked to the test matrices^[5] ^[6]. Adam Miller said he would try to run the desktop tests for Xfce. The group discussed the two potential blocker bugs that testing had so far uncovered, an update installation issue #567346^[7] and a traditional CD installer disc swapping issue #569377^[8]. They agreed that testing should continue to isolate the conditions that would trigger 567346, and that 569377 should be moved to blocking the Beta. The group also discussed two dependency issues Kamil Paral had noticed during installation validation but had not yet nominated as blockers, and agreed they did not need to block the release as they did not affect the packages on the physical media.

James Laska reviewed a topic from the Bugzappers group, where a decision had been taken to rebase open Rawhide bugs to Fedora 13.

Will Woods and Kamil Paral gave an update on the AutoQA project. Will noted that he had sent some proposed development guidelines to the mailing list, emphasizing the use of git and suggesting small patches be submitted to the list using git-send-email. He also suggesting creating personal branches in the main public repository for anyone wanting to work on large changes. The plan had been broadly accepted, and Will planned to codify it on the AutoQA wiki soon. Will reported no progress on the dependency checker test this week, as he had been working on other things. He recapped that a working depcheck script was already available^[9] and just needed some basic testing, but the next step was to work out exactly what the test subjects should be: testing individual updates is not useful, rather some way to discover which group of updates will be pushed as a set is needed so that the set can be tested. He would work on this and report back to the next meeting. Kamil reported that the group had held another design discussion^[10] for the planned results database, and he was working on some use cases which would be available^[11] later. Josef Skladanka had provided a draft visualization^[12] of the system. James Laska noted Liam Li's progress on automated DVD installation^[13], using dogtail to pass kernel parameters into the installation. He was also looking into having the automated installation set up the necessary environment for subsequent automated GUI testing.

Kamil Paral asked how a serious bug in an accepted feature^[14] should be considered in regard to the release criteria. James Laska did not have a definitive answer, but for now recommended documenting it as a common bug.

No Bugzappers group weekly meeting was held on 2010-03-02 as there were no items needing discussion.

The next QA weekly meeting will be held on 2010-03-08 at 1600 UTC in #fedora-meeting. The next Bugzappers weekly meeting will be held (if necessary) on 2010-03-09 at 1500 UTC in #fedora-meeting.

Fedora 13 Alpha

Adam Williamson represented QA at the Alpha go/no-go meeting^[1] held on 2010-03-04 and also attended by release engineering and development representatives. The group agreed that Alpha RC4 passed the release criteria^[2] and could be released as Fedora 13 Alpha.

Fedora 12 update problems

Matthias Clasen started a discussion^[1] about the known PackageKit bug^[2] which has caused some Fedora 12 users to have problems attempting to do the first post-install update with PackageKit, asking what could be done to ensure the problem did not occur in Fedora 13. Adam Williamson tried to explain^[3] that it was currently difficult to absolutely protect against this type of problem, as there is a catch-22 involved: if PackageKit has a bug which prevents update installation working for some reason, shipping an update for PackageKit cannot resolve the problem as it will be impossible to install the update. Matthias explained^[4] that he was in this case considering the symptom rather than the cause, and was asking if potential updates could be tested in batches via AutoQA before being released.

yum-langpack Test Day recap

Rui He posted a recap^[1] of the 2010-02-25 yum-langpack Test Day^[2], thanking those who had attended and listing the bugs that had been uncovered by the testing. Jens Petersen thanked her^[3] for her work on the event.

Updates-testing karma reporting script - fedora-easy-karma

Till Maas announced^[1] his new tool fedora-easy-karma^[2], which greatly asssists in the process of filing feedback on packages in updates-testing via Bodhi^[3]. Many group members thanked Till for the script and reported success in using it. Adam Williamson documented the tool on the QA Tools wiki page^[4] and the page on updates-testing^[5]. Some testers reported bugs in the script, which Till promptly addressed. Till also noted^[6] that he had built a package for the script and filed a review request^[7] to have it added to the repositories.

[1] ttp://fedoraproject.org/wiki/QA

[2] ttp://fedoraproject.org/wiki/Features/SSSDByDefault

[3] ttp://fedoraproject.org/wiki/Test_Day:2010-03-11_webcams

[4] ttp://fedorahosted.org/fedora-qa/

[5] ttp://fedoraproject.org/wiki/QA/Meetings

[6] ttp://fedoraproject.org/wiki/QA/Meetings/20100301

[7] ttp://fedoraproject.org/wiki/QA/JoinCriticalPathWranglers:Draft

[8] ttp://lists.fedoraproject.org/pipermail/test/2010-February/088824.html

[9] ttp://fedoraproject.org/wiki/Test_Results:Fedora_13_Alpha_RC4_Install

[10] ttp://fedoraproject.org/wiki/Test_Results:Fedora_13_Alpha_RC4_Desktop

[11] ttp://bugzilla.redhat.com/show_bug.cgi?id=567346

[12] ttp://bugzilla.redhat.com/show_bug.cgi?id=569377

[13] ttp://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck

[14] ttp://fedorahosted.org/pipermail/autoqa-devel/2010-February/000234.html

[15] ttp://fedoraproject.org/wiki/AutoQA_resultsdb_use_cases

[16] ttp://jskladan.fedorapeople.org/dbschema.png

[17] ttps://fedorahosted.org/autoqa/ticket/107#comment:4

[18] ttp://bugzilla.redhat.com/show_bug.cgi?id=569352

[19] ttp://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.log.html

[20] ttp://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria

[21] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088922.html

[22] ttps://bugzilla.redhat.com/show_bug.cgi?id=553115

[23] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088934.html

[24] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088935.html

[25] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088966.html

[26] ttp://fedoraproject.org/wiki/Test_Day:2010-02-25_YumLangpackPlugin

[27] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088968.html

[28] ttp://lists.fedoraproject.org/pipermail/test/2010-March/088978.html

[29] ttp://fedoraproject.org/wiki/Fedora_Easy_Karma

[30] ttp://bodhi.fedoraproject.org

[31] ttp://fedoraproject.org/wiki/QA/Tools

[32] ttp://fedoraproject.org/wiki/QA/Updates_Testing

[33] ttp://lists.fedoraproject.org/pipermail/test/2010-March/089018.html

[34] ttp://bugzilla.redhat.com/show_bug.cgi?id=570771

[1]

[1]

[2]

[3]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[1]

[2]

[1]

[2]

[3]

[4]

[1]

[2]

[3]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

@@ Line 28: / Line 28: @@
 [[User:Jlaska|James Laska]] reviewed a topic from the Bugzappers group, where a decision had been taken to rebase open Rawhide bugs to Fedora 13.
-[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] gave an update on the AutoQA project. Will noted that he had sent some proposed development guidelines to the mailing list, emphasizing the use of git and suggesting small patches be submitted to the list using git-send-email. He also suggesting creating personal branches in the main public repository for anyone wanting to work on large changes. The plan had been broadly accepted, and Will planned to codify it on the AutoQA wiki soon. Will reported no progress on the dependency checker test this week, as he had been working on other things. He recapped that a working depcheck script was already available<ref>http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck</ref> and just needed some basic testing, but the next step was to work out exactly what the test subjects should be: testing individual updates is not useful, rather some way to discover which group of updates will be pushed as a set is needed so that the set can be tested. He would work on this and report back to the next meeting. Kamil reported that the group had held another design discussion<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-February/000234.html>/ref> for the planned results database, and he was working on some use cases which would be available<ref>http://fedoraproject.org/wiki/AutoQA_resultsdb_use_cases</ref> later. [[User:Jskladan|Josef Skladanka]] had provided a draft visualization<ref>http://jskladan.fedorapeople.org/dbschema.png</ref> of the system. [[User:Jlaska|James Laska]] noted [[User:Liam|Liam Li's]] progress on automated DVD installation<ref>https://fedorahosted.org/autoqa/ticket/107#comment:4</ref>, using dogtail to pass kernel parameters into the installation. He was also looking into having the automated installation set up the necessary environment for subsequent automated GUI testing.
+[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] gave an update on the AutoQA project. Will noted that he had sent some proposed development guidelines to the mailing list, emphasizing the use of git and suggesting small patches be submitted to the list using git-send-email. He also suggesting creating personal branches in the main public repository for anyone wanting to work on large changes. The plan had been broadly accepted, and Will planned to codify it on the AutoQA wiki soon. Will reported no progress on the dependency checker test this week, as he had been working on other things. He recapped that a working depcheck script was already available<ref>http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck</ref> and just needed some basic testing, but the next step was to work out exactly what the test subjects should be: testing individual updates is not useful, rather some way to discover which group of updates will be pushed as a set is needed so that the set can be tested. He would work on this and report back to the next meeting. Kamil reported that the group had held another design discussion<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-February/000234.html</ref> for the planned results database, and he was working on some use cases which would be available<ref>http://fedoraproject.org/wiki/AutoQA_resultsdb_use_cases</ref> later. [[User:Jskladan|Josef Skladanka]] had provided a draft visualization<ref>http://jskladan.fedorapeople.org/dbschema.png</ref> of the system. [[User:Jlaska|James Laska]] noted [[User:Liam|Liam Li's]] progress on automated DVD installation<ref>https://fedorahosted.org/autoqa/ticket/107#comment:4</ref>, using dogtail to pass kernel parameters into the installation. He was also looking into having the automated installation set up the necessary environment for subsequent automated GUI testing.
 [[User:Kparal|Kamil Paral]] asked how a serious bug in an accepted feature<ref>http://bugzilla.redhat.com/show_bug.cgi?id=569352</ref> should be considered in regard to the release criteria. [[User:Jlaska|James Laska]] did not have a definitive answer, but for now recommended documenting it as a common bug.

Search