Linux kernel community has formed a virtual QA team and testing process gradually, from developing unit testing, to testing service (various CI that covers build, fuzzing and runtime), to result consolidation (KCIDB) to bug scrub (regzbot), which largely formalize the testing effort in community wide. 0-Day CI is glad to be part of this progress.
In this topic, we will talk about the status of such trend, and how each part work together. And a few words regarding 0-Day CI’s current effort in this trend. Then we want to exchange the ideas and have the discussion around any enhancements or missing parts of this virtual team, like
- Common testing methodology, such as bisection optimization, selective testing to reduce overall tests based on what is really changed.
- Test matrix to map feature and tests so to know whether a feature is covered and enough
- The connection with OSV, user and feature developer to convert their tests to be in the test pool like kselftests
- Reduce breakage between different architectures to avoid test bias
- Roadmap to adopt new test tools such as kismet
- Extend the shift left testing to detect issue earlier so likely to reduce the overall Reported-by tags on mainline
We look forward to having more collaboration with other players in the community to jointly move this trend forward.
|I agree to abide by the anti-harassment policy||Yes|