From Fedora Project Wiki

< FWN‎ | Beats

m (fix a bad tag)
(create fwn 260 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Next week sees 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. On compatible systems, Fedora 15 will use biosdevname<ref>http://linux.dell.com/biosdevname/</ref> to name the network interfaces; this provides a fully deterministic naming scheme on such systems, as opposed to the current system, where you cannot be sure that a given interface's name in Fedora will reflect its physical location or label. The Test Day will ensure this system is working correctly and also that it does not override existing preferred names on upgrades, so if you want to make sure this change has no unexpected consequences for you, make sure to come along to the Test Day! The testing involved will be easy and possible from a live image, and the Test Day page has instructions to find out if your hardware is involved in this change.
This week sees the first Fedora 15 Test Day on 2011-01-27<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. On compatible systems, Fedora 15 will use biosdevname<ref>http://linux.dell.com/biosdevname/</ref> to name the network interfaces; this provides a fully deterministic naming scheme on such systems, as opposed to the current system, where you cannot be sure that a given interface's name in Fedora will reflect its physical location or label. The Test Day will ensure this system is working correctly and also that it does not override existing preferred names on upgrades, so if you want to make sure this change has no unexpected consequences for you, make sure to come along to the Test Day! The testing involved will be easy and possible from a live image, and the Test Day page has instructions to find out if your hardware is involved in this change.


[[User:Adamwill|Adam Williamson]] reported that he had revised the set of X test cases and the Wiki pages for the X Test Week coming in February<ref>http://fedorahosted.org/fedora-qa/ticket/156#comment:8</ref>.
Next Thursday, 2011-02-03, will see 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. Mark it on your calendar!


<references/>
<references/>


=== Package-specific and critical path test case process ===
=== Refining Bugzilla messages on updated packages ===
 
[[User:Lmacken|Luke Macken]] applied the patch from [[User:Fcami|François Cami]]<ref>http://fedorahosted.org/fedora-infrastructure/ticket/701</ref> to improve the comments Bodhi leaves on bugs when the status of an update changes.
 
<references/>
 
=== Test case management system proposal and requirements ===


[[User:Adamwill|Adam Williamson]] announced that the process for categorizing package-specific and critical path test cases had gone live<ref>http://lists.fedoraproject.org/pipermail/test/2011-January/096368.html</ref>, and called for QA and development group members to help out with contributing new test cases and converting existing ones to the new system.
During the QA weekly meeting of 2011-01-24<ref>http://fedoraproject.org/wiki/QA/Meetings/20110124</ref>, [[User:Rhe|Rui He]] reported that she had completed the review of use cases<ref>http://fedoraproject.org/wiki/Tcms_use_cases</ref> and features<ref>http://fedoraproject.org/wiki/Tcms_use_cases</ref> in comparing the current Wiki-based system for managing test cases and the potential replacement, Nitrate<ref>http://fedoraproject.org/wiki/Nitrate</ref>. The next step is to identify must-have and nice-to-have features to see if any are missing from Nitrate, and write scripts to convert Wiki test cases into Nitrate test cases.


<references/>
<references/>


=== Testing Xen dom0 support ===
=== Multi-spin DVD review ===


Steven Haigh tested out Michael Young's side repo<ref>http://fedorapeople.org/~myoung/dom0</ref> containing kernels intended to add (technically, restore) Xen Dom0 support to Fedora, and reported his findings<ref>http://lists.fedoraproject.org/pipermail/test/2011-January/096366.html</ref>. He was not able to get the kernel to boot correctly.
On a request from David Nalley, some group members reviewed the proposed multi-spin DVD<ref>http://fedorahosted.org/fedora-qa/ticket/164</ref>. [[User:Johannbg|Jóhann Guðmundsson]] suggested testing boot and installation of each live environment on the DVD. [[User:Cwickert|Christoph Wickert]], the main proposer of the spin, agreed that this would be a good idea, but did not expect to hit any problems.


<references/>
<references/>


=== AutoQA ===
=== Smolt graphics card generation extraction ===
 
[[User:Adamwill|Adam Williamson]] suggested a project for anyone looking for one - extracting information on graphics card generations from Smolt<ref>http://www.happyassassin.net/2011/01/17/potential-project-for-someone-graphics-card-generations-in-smolt/</ref>. He explained that this would be useful for assessing the overall level of support for GNOME Shell in Fedora 15.
 
<references/>


It was a busy week in AutoQA. [[User:Kparal|Kamil Paral]] simplified the test object template<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001494.html</ref> and claimed that a three year old could now write an AutoQA test object...as long as the three year old had a grasp of basic Python!
=== Package-specific and critical path test case process ===


[[User:Clumens|Chris Lumens]] added a git-post-receive hook<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001473.html</ref>, which triggers every time a new commit is made into a git repository. He also submitted three new tests, including one to automate many of the installation test matrix<ref>http://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template#Test_Matrix</ref> tests.
[[User:Jlaska|James Laska]] provided a script<ref>http://fedorahosted.org/fedora-qa/ticket/154#comment:39</ref> implementing searching for package-specific test cases meeting the categorization guidelines recently put into practice.


Martin Krizek implemented support for standardized logging<ref>http://fedorahosted.org/autoqa/ticket/196</ref> and unittest execution<ref>http://fedorahosted.org/autoqa/ticket/258</ref>.
<references/>


[[User:Jskladan|Josef Skladanka]] submitted a new implementation of the koji watcher for review<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001485.html</ref>. There was some debate, but overall consensus that the new approach was an improvement and when fully implemented should improve the speed, accuracy and thoroughness of the watcher.
=== AutoQA ===


[[User:Wwoods|Will Woods]] submitted his dependency checking test for review<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001512.html</ref>, and [[User:Jlaska|James Laska]] posted his thoughts on it<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001521.html</ref>.
The new koji watcher implementation submitted for review last week by [[User:Jskladan|Josef Skladanka]], and the dependency checking test submitted by [[User:Wwoods|Will Woods]], were both reviewed this week<ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001521.html</ref> <ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001526.html</ref> <ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001503.html</ref> <ref>http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001522.html</ref>. The AutoQA team also identified an issue in Bodhi's use of -pending tags, which [[User:Lmacken|Luke Macken]] rapidly fixed.


<references/>
<references/>

Revision as of 06:39, 27 January 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

This week sees the first Fedora 15 Test Day on 2011-01-27[1], on network device naming changes upcoming in Fedora 15. On compatible systems, Fedora 15 will use biosdevname[2] to name the network interfaces; this provides a fully deterministic naming scheme on such systems, as opposed to the current system, where you cannot be sure that a given interface's name in Fedora will reflect its physical location or label. The Test Day will ensure this system is working correctly and also that it does not override existing preferred names on upgrades, so if you want to make sure this change has no unexpected consequences for you, make sure to come along to the Test Day! The testing involved will be easy and possible from a live image, and the Test Day page has instructions to find out if your hardware is involved in this change.

Next Thursday, 2011-02-03, will see the first of three planned Test Days on the GNOME 3 desktop[3], which is landing in Fedora 15. Mark it on your calendar!

Refining Bugzilla messages on updated packages

Luke Macken applied the patch from François Cami[1] to improve the comments Bodhi leaves on bugs when the status of an update changes.

Test case management system proposal and requirements

During the QA weekly meeting of 2011-01-24[1], Rui He reported that she had completed the review of use cases[2] and features[3] in comparing the current Wiki-based system for managing test cases and the potential replacement, Nitrate[4]. The next step is to identify must-have and nice-to-have features to see if any are missing from Nitrate, and write scripts to convert Wiki test cases into Nitrate test cases.

Multi-spin DVD review

On a request from David Nalley, some group members reviewed the proposed multi-spin DVD[1]. Jóhann Guðmundsson suggested testing boot and installation of each live environment on the DVD. Christoph Wickert, the main proposer of the spin, agreed that this would be a good idea, but did not expect to hit any problems.

Smolt graphics card generation extraction

Adam Williamson suggested a project for anyone looking for one - extracting information on graphics card generations from Smolt[1]. He explained that this would be useful for assessing the overall level of support for GNOME Shell in Fedora 15.

Package-specific and critical path test case process

James Laska provided a script[1] implementing searching for package-specific test cases meeting the categorization guidelines recently put into practice.

AutoQA

The new koji watcher implementation submitted for review last week by Josef Skladanka, and the dependency checking test submitted by Will Woods, were both reviewed this week[1] [2] [3] [4]. The AutoQA team also identified an issue in Bodhi's use of -pending tags, which Luke Macken rapidly fixed.