Currently we often have a fairly big disconnect between generic testing and quality efforts and the work of developers and maintainers. There is a lot of testing that is done by people working on the kernel that is not covered by what the general testing efforts do, and conversely it is often hard for developers and maintainers to access broader community resources when extra testing is needed. This impacts both development but also downstream users like stable kernels.
How can we join these efforts together?
Areas with successful reuse include:
Other testing efforts more confined to their domains:
- Intel's audio testing setup
- Filesystem coverage (xfstests and so on)
Ideas/topics for discussion:
- Improved tooling
- Testsuite/system configuration
- Proposals from Cyril for describing hardware for tests
- Test interface standards
|I agree to abide by the anti-harassment policy||Yes|