Have you seen this dialog? It’s from a pretty handy utility called preupgrade. Preupgrade takes some of the complexity out of upgrading your Fedora system. But like any software, to keep running smoothly, it needs testing and maintenance.
For the past several releases, Fedora QA has hosted several test days (F14 and F13) to shake out bugs related to system upgrades using the preupgrade tool. Those same tests are also included in our regular release validation matrix. I’d like to think that regular, organized testing of preupgrade (and installer upgrades) contributes to a more reliable upgrade experience once Fedora GA’s. Thanks to Hurry for helping to organize these events. 🙂
Testing involves performing system upgrades using the latest preupgrade package. There are test instructions (including test cases) on the wiki page. Fedora QA and Richard Hughes (preupgrade maintainer) will be in the IRC channel #fedora-test-day on Freenode all day to help with testing and answer any questions you might have. If you’re not familiar with IRC, a web-based (WebIRC) client is available.
To participate, you’ll need a Fedora 14, or Fedora 13 system ready for upgrade. Test systems can be bare metal or virtualized guests, it doesn’t matter. If you don’t have a previous release handy, don’t worry … live images for previous releases are a great way to quickly install a working desktop.
Unfortunately, preupgrade doesn’t test itself, so we need your help. This is a good chance to get a head start on Fedora 15 Beta testing, and help identify preupgrade-related bugs early. See you on Thursday!
Hot off the heels of the well attended graphics test week, we have another test day queued up for several installer features. If you installed either Fedora 13 Alpha or Beta, you may have noticed the drastically different storage user-interface. This wasn’t an accident. At FUDCon Berlin 2009, several members of the installer team sat down with Mo to make it easier to find and identify the devices that you want to work with during installation. What followed was a pretty spectacular analysis of installer use cases and interaction (checkout Mo’s blog for more info). Interaction design is not something I know much about, but I know when something looks pleasing to the eye and feels well thought out. So kudos to Mo and and installer team for coming up with good ideas, and more importantly, seeing them through.
The second feature under test involves the last bit of refinements to the storage filtering code first introduced in Fedora 11. Certainly not as in your face as the user interface, but without it, you won’t be installing Fedora. Just as with the UI changes, we want to send the installer through as many different code paths as possible. This includes kickstart.
Okay, so enough prep. All that means we have something shiny to test! This Thursday, April 22, there will be a Test Day focused on the improved storage user-interface and storage filtering features. Several focus areas have been identified for testing, ranging from installation to basic devices (IDE, SCSI, USB) to more complex environments (RAID, BIOS RAID, iSCSI, Multipath, FCoE). Members of the installer development team, Fedora QA and Mo will be available to help guide testing and triage issues. Given how this event will be exercising the results of the user interaction analysis, we’re also interested in your thoughts on the improved interface. What works, what doesn’t seem quite right.
Checkout the test day wiki, and come join #fedora-test-day on irc.freenode.net to share your results. If you are new to IRC, read this page.
Just posted to test-announce list, but I thought I would pass this along for folks not subscribed.
This will be a busy week for the Fedora QA team. As Adam pointed out, beta candidate testing is underway. Kamil and Jiří Moskovčák will host a test day on the Automatic bug detection and reporting tool (aka ABRT) this Thursday. Last, but not least, there will be a Test Day this Tuesday on SSSD by default.
SSSD isn’t new to Fedora 13. In fact, it first arrived in Fedora 11 (see previous test day almost 1 year ago). However in Fedora 13, it will be the default whenever setting up network identity or authentication. Also, a new and improved graphical user interface (authconfig) configuration utility is available. The utility will be presented during firstboot, or can be accessed from the System →Administration →Authentication menu item.
As with just about every Test Day, live images and easy-to-follow test cases are available for participants. While it’s best to test your own identity & authentication services, LDAP and kerberos servers are available for test day participants. So there is no excuse for not contributing your results.
Come join #fedora-test-day on irc.freenode.net this Tuesday. SSSD and authconfig developers and testers are available to help triage problems.
This Thursday, 2010-02-25, come join the Yum Langpack Plugin Test Day.
The event will focus on a yum plugin that allows langpacks to be automatically installed for your native language. Testers who frequently install Fedora with additional languages are encouraged to join.
In the past, one had to manually apply the langpack packages for any post-install software additions. For example, if you installed your system with the Polish locale, and at a later date you want to install KDE or Openoffice.org, additional steps were required. You had to remember to install the appropriate language package (e.g. kde-i18n-Polish or openoffice.org-langpack-pl_PL). However, with yum-langpacks installed, additional language packs will installed as needed when installing new software.
The test day prescribes several test cases that can be easily followed on a Fedora 12 system. Additionally, for those interested in helping test Fedora 13 Alpha, further tests are available. The Test Day runs all day in freenode IRC #fedora-test-day. As with any test day, if you can’t make it to the live event, you can always provide feedback at a later date.
Adam and I have jumped into a higher gear when it comes to mapping out test days for Fedora 13. Given the large number of features in Fedora 11 and 12, I was expecting a reprieve for Fedora 13. While it’s not the largest release in terms of the features, it’s not the smallest either.
Unfortunately, there are only so many events the QA team can scope out for a release. We need community input. Not only for planning events, but also during execution. A successful test day requires prep time, and a presence during the event to help triage issues and remove obstacles. If either is lacking, the event is guaranteed to be forgotten.
So, if there is a feature or focus area you’d like to see test day coverage for during Fedora 13 … please let the QA team know. Proposing a test day is pretty straight forward, for details check out the wiki. Also, take a look at current test day calendar for a list of scheduled events.
For convenience, you can propose a test day using the form below (FAS login required):
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.