Contents
Summary
Testing is hard and expensive. The more we can automate testing at the distribution level, the earliest we can detect problems and fix them. This feature proposal is about imagining various ways to automatically test the stability and quality of Mageia at a given moment.
Note that we already have in Mageia some ways we do automated tests for cauldron: rpmlint, youri-check, dose3. We can do better.
Owner
- Name: Malo
- Email: malo AT mageia DOT org
Resources
- sysadm
- packagers
Current status
- Targeted release: Mageia 4
- Last updated: 2025/05/05
- Percentage of completion: 0%
Detailed Description
This feature proposal is an exploratory proposal: it is about trying out several automated testing methods for Mageia.
Some ideas can be:
- integrate autobuild in the main infrastructure to run automatically every 2 days (hopefully every day soon): it checks that the development tools are working
- packages that can run tests when they build on the Build System
- develop a test-bed which runs VMs and checks test results with libvirt
- package a test-suite than anyone can run on his own machine
- use autoinstallation method on a VM to test automatically the quality of produced ISOs
- run a set of automated benchmarks to notice early performance regression (notably boot time, etc)
Inspirations:
Why it would be good for Mageia to include it
It would increase the overall quality, and potentially decrease QA's work when release time comes.
Software / Packages Dependencies
Potentially all packages are implicated, but I propose to start with only a few.
What could disrupt development of this new feature
Low number of people in the sysadm team
Planning
Any test happening before release will be good.
Contingency
No contingency.
Release Notes
Documentation
When tools are produced, they can be documented on the wiki.
