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
Next week sees the first Fedora 15 Test Day[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.
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[3].
Package-specific and critical path test case process
Adam Williamson announced that the process for categorizing package-specific and critical path test cases had gone live[1], and called for QA and development group members to help out with contributing new test cases and converting existing ones to the new system.
Testing Xen dom0 support
Steven Haigh tested out Michael Young's side repo[1] containing kernels intended to add (technically, restore) Xen Dom0 support to Fedora, and reported his findings[2]. He was not able to get the kernel to boot correctly.
AutoQA
It was a busy week in AutoQA. Kamil Paral simplified the test object templateCite error: Closing </ref> missing for <ref> tag, 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[1] tests.
Martin Krizek implemented support for standardized logging[2] and unittest execution[3].
Josef Skladanka submitted a new implementation of the koji watcher for review[4]. 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.
Will Woods submitted his dependency checking test for review[5], and James Laska posted his thoughts on it[6].
- ↑ http://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template#Test_Matrix
- ↑ http://fedorahosted.org/autoqa/ticket/196
- ↑ http://fedorahosted.org/autoqa/ticket/258
- ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001485.html
- ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001512.html
- ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-January/001521.html