From Fedora Project Wiki

< FWN‎ | Beats

(qa beat for 262)
(create fwn 263 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Thursday 2011-01-27 saw the first Fedora 15 Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-01-27_Network_Device_Naming_With_Biosdevname</ref>, on network device naming changes upcoming in Fedora 15. The event went successfully and exposed some bugs in the system. [[User:Jlaska|James Laska]] provided a wrap-up of the event<ref>http://lists.fedoraproject.org/pipermail/test/2011-February/096886.html</ref>.
No Test Day took place last week due to the delay of the FreeIPA Test Day. This week two Test Days are taking place.


Thursday 2011-02-03 was the first of three planned Test Days on the GNOME 3 desktop<ref>http://fedoraproject.org/wiki/Test_Day:2011-02-03_GNOME3_Alpha</ref>, which is landing in Fedora 15. With considerable help from the desktop team, the event was a great success, with a wide range of users providing some very good testing and unearthing many bugs. [[User:Adamwill|Adam Williamson]] provided a wrap-up of the event<ref>http://lists.fedoraproject.org/pipermail/test-announce/2011-February/000180.html</ref>.
Tuesday 2011-02-15 was FreeIPA v2<ref>http://fedoraproject.org/wiki/Features/FreeIPAv2</ref> Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-02-15_FreeIPAv2</ref>. IPA is an identity server, and 2.0 is a major revision due to land in Fedora 15. The Test Day focused on checking that all the major changes work as intended. A small group of testers attended the event and exposed several issues, which the developers are now working on.


This Thursday, 2011-02-10, was due to be FreeIPA v2<ref>http://fedoraproject.org/wiki/Features/FreeIPAv2</ref> Test Day, but the event has been postponed to Tuesday 2011-02-15<ref>http://fedoraproject.org/wiki/Test_Day:2011-02-15_FreeIPAv2</ref> - update your calendars! IPA is an identity server, and 2.0 is a major revision due to land in Fedora 15. The Test Day will be checking that all the major changes work as intended. Existing IPA users are probably the most likely candidates for the event, but if you've been meaning to give IPA a try anyway, this might be the ideal time.
Thursday 2011-02-17 is Xfce 4.8<ref>http://fedoraproject.org/wiki/Features/Xfce48</ref> Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-02-17_Xfce</ref>, where we are testing out all the new features of this major Xfce release and ensuring there are no regressions. A full report on the event will be printed next week.
 
Thursday 2011-02-17 will be Xfce 4.8<ref>http://fedoraproject.org/wiki/Features/Xfce48</ref> Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2011-02-17_Xfce</ref>, where we will be testing out all the new features of this major Xfce release and ensuring there are no regressions. If you're an Xfce user or just interested in alternative desktops, please come along and help test.


<references/>
<references/>


=== FUDCon Tempe ===
=== AutoQA ===


The QA team was out in force at FUDCon Tempe<ref>http://fedoraproject.org/wiki/FUDCon:Tempe_2011</ref>. [[User:Jlaska|James Laska]] gave an AutoQA Update presentation<ref>http://fedoraproject.org/w/uploads/1/1c/FUDCon_Tempe_-_AutoQA_presentation.odp</ref> and [[User:Adamwill|Adam Williamson]] provided two wrap-up posts<ref>http://www.happyassassin.net/2011/01/30/fudcon-day-1-5/</ref> <ref>http://www.happyassassin.net/2011/02/03/fudcon-days-1-5-to-3-and-the-aftermath/</ref>.
[[User:Kparal|Kamil Paral]] reported that he had conducted an AutoQA workshop at the Developer Conference event<ref>http://fedoraproject.org/wiki/DeveloperConference2011</ref> in Brno<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-February/001623.html</ref>. He also published the sample workshop material<ref>http://kparal.fedorapeople.org/autoqa/doctest.tar.xz</ref>.


<references/>
<references/>


=== AutoQA ===
=== Test Day SOP improvements ===
 
[[User:Jlaska|James Laska]] created a patch<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001543.html</ref> to transfer AutoQA config files from the test server to the client. [[User:Wwoods|Will Woods]] posted a revised version of his dependency check test<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001552.html</ref>. [[User:Jskladan|Josef Skladanka]] updated his new koji watcher code<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001529.html</ref>.


The team also worked on making AutoQA more accessible to new developers. Josef set up a trac milestone called Finger Food<ref>http://fedorahosted.org/autoqa/milestone/Finger%20Food</ref> containing small tasks suitable for new developers, while [[User:Kparal|Kamil Paral]] wrote a wiki page documenting AutoQA development<ref>http://fedoraproject.org/wiki/AutoQA_Development</ref>.  
[[User:Adamwill|Adam Williamson]] proposed an update<ref>http://lists.fedoraproject.org/pipermail/test/2011-February/096978.html</ref> to the Test Day management SOP<ref>http://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref>, adding a paragraph recommending the creation of a 'how to debug' page for the component being tested. This was the result of a suggestion at the previous weekly meeting by [[User:Johannbg|Jóhann Guðmundsson]].


<references/>
<references/>


=== Testing old Intel graphics in Fedora 15 ===
=== Fedora 15 Alpha preparation ===


Cornel Panceac reported several problems trying to load GNOME 3 in Fedora 15 on an old Intel graphics chipset<ref>http://lists.fedoraproject.org/pipermail/test/2011-January/096723.html</ref>, and wondered if this was expected behaviour. [[User:Adamwill|Adam Williamson]] explained<ref>http://lists.fedoraproject.org/pipermail/test/2011-January/096725.html</ref> that failure to support the GNOME Shell was normal, but the system should fall back smoothly to the 'classic' desktop mode, and failure to do that would be a bug. Cornel then reported the bug<ref>http://bugzilla.redhat.com/show_bug.cgi?id=673659</ref>.
Preparation for the release of Fedora 15 Alpha began in earnest this week. The first test compose was released<ref>http://lists.fedoraproject.org/pipermail/test/2011-February/096917.html</ref> and the first blocker review meeting took place<ref>http://lists.fedoraproject.org/pipermail/test/2011-February/096955.html</ref>. TC1 testing identified some major issues in both installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_15_Alpha_TC1_Install</ref> and desktop<ref>https://fedoraproject.org/wiki/Test_Results:Fedora_15_Alpha_TC1_Desktop</ref> areas.


<references/>
<references/>

Revision as of 00:49, 18 February 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].

Contributing Writer: Adam Williamson

Test Days

No Test Day took place last week due to the delay of the FreeIPA Test Day. This week two Test Days are taking place.

Tuesday 2011-02-15 was FreeIPA v2[1] Test Day[2]. IPA is an identity server, and 2.0 is a major revision due to land in Fedora 15. The Test Day focused on checking that all the major changes work as intended. A small group of testers attended the event and exposed several issues, which the developers are now working on.

Thursday 2011-02-17 is Xfce 4.8[3] Test Day[4], where we are testing out all the new features of this major Xfce release and ensuring there are no regressions. A full report on the event will be printed next week.

AutoQA

Kamil Paral reported that he had conducted an AutoQA workshop at the Developer Conference event[1] in Brno[2]. He also published the sample workshop material[3].

Test Day SOP improvements

Adam Williamson proposed an update[1] to the Test Day management SOP[2], adding a paragraph recommending the creation of a 'how to debug' page for the component being tested. This was the result of a suggestion at the previous weekly meeting by Jóhann Guðmundsson.

Fedora 15 Alpha preparation

Preparation for the release of Fedora 15 Alpha began in earnest this week. The first test compose was released[1] and the first blocker review meeting took place[2]. TC1 testing identified some major issues in both installation[3] and desktop[4] areas.