Write tests for the Always Ready Operating System
summary
Claims an “always ready” Fedora by making tests mandatory before changes merge, using Ansible standard-test roles to run tests and produce required test logs, a CI pipeline on OpenShift that consumes Koji scratch builds, and FMF metadata filters to pick relevant tests. Examples include a single smoke test exercising ~10–12 Python-related packages and about 120 components currently covered. The pipeline runs scratch builds, fetches tests, and gates failing changes; live demos show tests executing and producing pass/fail artifacts.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:18AGENDA
- 0:58INTRODUCTION
- 5:57VISION
- 7:19OVERVIEW
- 12:10PIPELINE
- 18:36Gating Bodhi updates
- 19:15STANDARD TEST ROLES
- 21:08DOCUMENTATION
- 24:33BASIC ROLE: DID
- 25:42BASIC ROLE: PYTHON
- 31:06EXPERIMENT
- 42:26FUTURE
related talks
40mEasily enable tests in Fedora, RHEL, GitHub
48mFedora Automated Testing State of the Art: Not Quite CI for Distributions, but...
14mUsing packit and testing farm for CI/CD and automation in an upstream project
29mTowards stronger checks on dependencies and compose inputs in Fedora
31m#testedAF: Test All the Things (Not Just Your Units)
16mTesting All The Way To Production
47mInfrastructure under Test in OpenShift
01h 05mFedora CI Meetup