Storing and Outputting Test Information: KUnit Attributes and KTAPv2
summary
Creates KUnit test attributes upstream to store supplemental data (speed and module name today) using flexible void-pointer attributes, exposes a struct and helper macros, and hooks into kunit filtering (k.filter and Python tooling). Outputs attribute blocks as proposed KTAP metadata lines so parsers can ignore or consume them. Practical result: filtering six slow tests cuts a 312-test run from ~10s to ~4s (and similar examples show 7s to 1s, ~89% faster).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:42Background on KUnit
- 2:29What is test information
- 4:37KUnit attributes project
- 6:41Benefits of filtering slow tests
- 7:48Potential KUnit attributes
- 8:28KTAPv2 and metadata proposal
- 11:58Q&A on KTAPv2 development
related talks
45mKUnit: Past, Present, and Future
45m"KUnit: Past, Present, and Future"
30mKernel Testing with KUnit: Bridging the Gap
18mKUnit: Function Redirection and More
16mHow do we make KUnit work for us?
30mIntegrating testing with maintainer flows
44mKUnit - Unit Testing for the Linux Kernel
21mUAPI testing with KUnit
