Fedora is a large project with several different teams and groups working on the distribution every day. Quality assurance, abbreviated to QA, is an important and fundamental part of what goes into making a release of Fedora successful. To make sure everything works and performance is improving, testing and quality checks are a must. In Fedora, the user experience is crucial as there are thousands and thousands of people who expect a more stable, feature-enriched operating system that gets better with each release.
The Fedora Quality Assurance (QA) team is the group of Fedora contributors that helps cover testing of the software that makes up Fedora. Through various test cases and different hardware, the team goes through important software that makes up Fedora and helps make sure it works as expected. Despite the importance of the work, getting involved isn’t too difficult.
Joining Fedora Quality Assurance
Fedora contributor and QA team member Sumantro Mukherjee recently wrote a three-part series on how to join the team. The first article mostly introduces the work and important tools for all team members. It also shows places to get involved and take part in conversations about testing and quality assurance.
The second part goes into setting up your work environment with a virtual machine and how to test new versions of packages awaiting feedback. In this article, you will be working with Rawhide, the ever-changing development version of Fedora.
The third and last part to the series reviews test cases and how to report your findings to the community. This article appears next Tuesday, so keep an eye out for the conclusion!
Get in touch with QA
Come say hello to the Fedora Quality Assurance team! You can find them on their mailing list and you can also interact with the global community on IRC.
Debug courtesy of Lemon Liu, Crash Test Dummy courtesy of James Keuning (from the Noun Project)
Link to third part is missing.
3rd part is yet to be published today so we need to stay tuned.