This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.
Next steps towards Fedora Quality Assurance (QA)
This is a continuation of the previous post in this series of how to get involved with the Fedora Quality Assurance (QA) team. Make sure you have the Bugzilla, FAS account, and email alias set up before following these steps. You can find more information about how to get those accounts in the earlier post.
There are several different tools and services available to help us test Fedora. This helps us insure the quality of software and stay on target for a stable release. One of the easiest ways to get involved is to run Rawhide, the ever-changing development version of Fedora, or a pre-release version like the Alpha or Beta. While you are able to upgrade your system directly to these versions, sometimes you may want to use a virtual machine (VM) to work in. We’ll cover some of the Fedora-specific tools for quality assurance testing as well as setting up your environment for testing.