Sure, it’s not only the answer to the ultimate question of life, the universe, and everything, it’s also the next milestone for the QA team on the fedora quality schedule. So, while beta testing and triage of reported issues continues, fixes to blocker bugs (and non-critical path components) are arriving daily. In case you don’t regularly follow fedora-test-list, Liam Li sent out a request for testing today. If you’d like to get involved, here’s a few areas in need of extra eyes.
Test the latest installer
With a spare laptop or workstation (or just a virtual guest), you can provide feedback on how the installer is doing by sharing results on https://fedoraproject.org/wiki/Test_Results:Fedora_12_Pre-RC_Install. The installer continues to improve since the beta. Take a look at recent anaconda changes for a change that may impact your system(s).
Test a bug fix
Help a maintainer by verifying a recent bug fix. A good place to start is by choosing a MODIFIED bug from the F12Blocker list. The list of MODIFIED bugs will be growing as issues are triaged and patches come in.
This Thursday, October 22, 2009 #fedora-test-day will be host to another test day focused on Power Management improvements in Fedora 12. This round features improvements to the tuned service along with a merge of another performance monitoring tool ktune. Testing is requested against several environments, including X, laptops and single-user mode.
When we first started the Test Day format in Fedora, there was hope that eventually this would provide a forum for test scripts and automation. If you participated in the previous Power Management event, you may notice a few improvements along these lines. Phil Knirsch, Marcela Maslanova, Petr Lautrbach and Jiri Skala have combined forces (think transformers) and are offering a test day package available for download that contains several scripts to aid testing and packaging test results. According to the wiki, once you follow the instructions to install the required package, running a test should be as simple as running the command:
testday-run-testname. Following each test, package up the results with the
testday-pack-results command, and upload the resulting .tar.gz file.
I’m looking forward to joining and hope others have time to share their power management results. As always, check out the test day wiki for more information.
"Really, a RAID test day? Thanks sounds boring." Well, if you don’t like baby seals, or don’t care about disk redundancy, than you might not be interested.
But the good news about a Fedora Test Day is that it offers an opportunity to test drive the upcoming release. Whether testing the focus of the day, a previous test day topic, or just a use case/environment you are familiar with, any feedback is good feedback. To get started …
- Download an image – Thanks to Kevin Fenzi, live images of Rawhide are built daily and available for download. If a live image doesn’t strike your fancy, download a rawhide boot.iso instead.
- Prepare your media – There are several different ways you can make use of the live image, including burning to a CD/DVD, writing to a USB stick, or booting under a virtual guest. I’m lazy, so unless my tests require physical hardware … I always go virtual.
- Tell us what works – Join IRC and tell us what works and what could be improved. File a bug.
Additionally, if you’re interesting in improving the install experience for RAID users, please do stop by. Members of the installer development team are at the ready and in need of your feedback. If you have a system with BIOS RAID or hardware RAID, or just a frequent user of software RAID, your feedback is important.
See you on #fedora-test-day on irc.freenode.net this Thursday, October 8, 2009.