How do the Linux kernel developers test their code locally and after they have it committed? Do they use some kind of unit testing, build automation? test plans?
How do the Linux kernel developers test their code locally and after they have it committed?
Do they use some kind of unit testing, build automation?
In classic sense of words, no.
E. g. Ingo Molnar is running the following workload: 1. build new kernel with random set of config options 2. boot into it 3. goto 1
Every build fail, boot fail, BUG or runtime warning is dealt with. 24/7. Multiply by several boxes, and one can uncover quite a lot of problems.
test plans?
No.
There may be misunderstanding that there is central testing facility, there is none. Everyone does what he wants.