On Thu, Apr 26, 2012 at 3:03 PM, Spear, Raymond (Mission Critical Linux) <[email protected]> wrote: > I have been following the discussion about splitting out the tests from the > source. > > My organization is thinking about putting tests into autotest for our code > and hardware base. > Given the changes that have been discussed, where is a good reference on how > to insert a test set into autotest>
So, we want to go forward with splitting tests. However, we are still in the process of figuring out how this split should be done. In any case, the test modules in the autotest tree right now will continue to be maintained by the maintainers, the idea is just splitting repositories, really. Therefore, if you guys plan on contributing tests, you can just do the usual procedure, which involves patchsets adding new directories to client/tests which the contents of the test module. https://github.com/autotest/autotest/wiki/TestDeveloper The above, although some sections might be dated, is a good reference into contributing new test modules. The idea with the whole test separation thing is that organizations have the choice of sending the tests upstream or maintain their own repositories (I hope publicly, at least for stuff that can be open sourced) with tests, say project Z wants to have a bunch of autotest based tests on their source repository. -- Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
