Getting Started in Fedora QA
summary
Requires a Fedora account and Bugzilla and follows the validation test matrix for each compose (rawhide branches into releases). Validation testing links failures to Bugzilla; release blockers get discussed at blocker bugs meeting 1600 UTC. Updates testing needs three positive votes to push to stable and testing is sped up with fedora-easy-karma (10 updates in ~5 minutes vs ~1 hour). Fedora 29 numbers: 1,074 bugs, 671 matrix tests, 1,685 karma (≈17 bugs/day, 11 tests/day, 27 karma/day).
AI-written summary · about
chapters (9)
- 0:00Start
- 0:59What do you need?
- 2:49What to test?
- 3:29Validation Testing
- 6:57Bugzilla
- 7:37Blocker Bugs Meeting
- 8:48updates-testing
- 10:03fedoro-easy-karma
- 12:22How do your test results help?
related talks
48mFedora Automated Testing State of the Art: Not Quite CI for Distributions, but...
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
35mTesting GUI with Fedora and openQA
53mWhat Happens When Everyone is QA? And I Mean Everyone!
36mHow to defuse a bomb Wait, I mean a bug
26mTesting Github PRs on Fedora/Centos with Packit
41mThe magical fantasy land of Linux kernel testing
39mDay-to-day Testing of Linux 'Next' Kernel Branch - My Story