From Fedora Project Wiki

Well I have been in the QA group for a little over a year now. Mostly I have been running the standard test procedures on the nightly drops and running the canned regression tests on new versions of the Kernel. I've occasionally tested updates when I can recognize what a particular update was and had an idea how to test it. I've also done some tagging of packages.

For now I'm limiting my testing on fedora releases to Workstation Live because that is what I am familiar with as a user / maintainer (for a small group of users). I am quite familiar with PC hardware so I always do the testing on bare metal. I have dedicated a hardware PC for testing (Lenovo M58P with an E8400 processor). It is a fairly old dual core 3Ghz 4Gb machine with a 160Gb disk. It's main virtues are that it's in good condition and it was available.

When I test a drop, after checking the ISO's checksum, I burn it to DVD and use the DVD to boot my test machine. I always choose the (I want to make space available) and pick the (Delete All) followed by (Reclaim Space). I do this to avoid any possible issues with the last installation. After the installation is complete and the PC has been restarted, I set the display to a resolution that works with the monitor using the Settings application. Then I install Gnome-Tweaks and set the fonts to sizes that I am used to and I use the Gnome Settings to set a screen resolution that works for me. Then the testing begins; Besides the official test cases, I also run other tests to see if various tools and applications are working (beyond the start / stop tests).

For the standard testing of a Branched pre-release version I generally run the ones that Coconut does not run; though there have been exceptions when I run more of them. When I'm testing a Rawhide drop I tend to run the standard tests and some of my own tests on various tools.


If you'd like to comment or send some advice, please feel free to do so.