There are a lot of things that still need to be done to make this a complete kernel testing system. The following sections will discuss some of the to do items in detail.
While the number of configuration options for the Linux kernel is seen as a strength to developers and users alike, it is a curse to testers. To create a powerful automated testing system, we need to be able to determine what the configuration on the booted box is and then determine which tests should be run on that box.
The Linux kernel has hundreds of configuration options that can be set to compile the kernel. There are more options that can be set when you boot the kernel and while it is running. There are also many patches that can be applied to the kernel to add functionality or change behavior.
A lot of testing will be done in the life of the Linux Test Project. Keeping track of the results from all the testing will require some infrastructure. It would be nice to take that output from a test machine, feed it to a program and receive a list of items that broke since the last run on that machine, or were fixed, or work on another test machine but not on this one.