The plan for Maloo (aboriginal for thunder) is that it will become a complete set of tools for creating, managing, running a tool for reporting and analyzing the results of Lustre validation testing efforts. We require that the validation tools are closed loop, with the results of the process enabling greater productivity in the future.
Because an individual cannot possibly know what each of the many hundreds of tests does, and therefor if the person therefore if a developer changes a line functional of code in Lustre has we generally have to run all the tests just to be sure , I'm thinking of how we create a test resource that can capture not only the history of the testing of Lustre, but also the history of each test. This will that all tests are run and pass. This allow analysis of the value of the tests and the test environment. Maloo allows a wide variety of searching, reporting, and analysis tools to see the history of specific tests, and trends over time.
When a developer is developingchanging code, the test environment should deliver a test set that is customised customized to the particular development activity. This might mean for example that the Ideally, the test environment can produce a directed minimilalist minimalist test set, that automatically runs those tests most likely to fail first.Lots more to follow, my first step is to capture the test results into a database and then work forwards from there.