Fedora Automated Testing State of the Art: Not Quite CI for Distributions, but...
summary
Fedora uses openQA and Fedora CI: openQA runs 100+ parallel tests on real machines and has executed over 3 million tests, focusing on functional compose and update testing and catching several hundred release-critical bugs. Fedora CI tests package builds via TMT and reports on pull requests, helping catch failures before updates. About 75% of the release validation suite is automated and roughly 50–60 update tests run every ten minutes, but full CI is blocked by capacity, hardware and reliability limits.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:43TESTING AN OPERATING SYSTEM
- 10:53OPENQA TEST COVERAGE
- 16:08OPENQA RESOURCES
- 29:21BODHI
- 33:30BEHIND THE SCENES
- 37:05OPENQA PLANS
- 38:21FEDORA CI PLANS
- 39:29OTHER PLANS
related talks
39mCI and automated testing in Fedora: where we're at
20mGetting Started in Fedora QA
29mTowards stronger checks on dependencies and compose inputs in Fedora
51mWrite tests for the Always Ready Operating System
26mTesting Github PRs on Fedora/Centos with Packit
35mTesting GUI with Fedora and openQA
38mopenQA - end to end testing of operating systems
25mIdentical Testing Environments from Laptop to CI with tmt and Testing Farm