So, we started this thread at github: https://github.com/autotest/autotest/issues/273
But we feel like it's a better idea to move it here. Bottom line, we'd like to separate the test modules (both client and server side) in separate repositories. We have obviously the pros and cons. Here are some of the points previously raised by Ademar: """ Pros: - Scalability: we want autotest to grow orders of magnitude, and the current model simply doesn't scale. Right now Lucas spends a good amount of his time reviewing tests and maintaining the good quality of the autotest codebase. Once we move the tests out of autotest.git, we get a clear separation and different patch queues with different priorities (and lots of different maintainers). - If we want autotest to be used by 3rd parties (and we do), we have to consider tests written outside of autotest.git as first class citizens. One of the best ways to do that is by leveraging the playing field and eating our own dogfood: tests written by us should work under the same scenario and cirscunstances of the 3rd parties tests and that means outside of the autotest repository. And this should be the default. It will help us keep the API stable, enforce a clear separation between tests and the framework/library and give us a clear understanding of any usability problems or breakage. Think of multiple releases of autotest: you'll need to declare compatibility between releases and some tests will require Autotest >= X. One of the best ways to keep track of these changes is by having tests separated from the framework. - 3rd party developers, most of the time, are not interested in contributing to autotest itself. They want to use autotest to write their tests, but get scared of the complexity of the codebase. KISS is king here: we need a clean, intuitive and self descriptive directory strucutre on autotest.git to attract new contributors, and having tests there, with control files, output dirs, reference files and a changelog with test changes just doesn't help. Ditto for people writting new tests. - I've heard this request multiple times during meetings with managers or developers from other teams: they want to have their own tests inside their own repository. Submitting and maintaining their tests to autotest.git is a burden. Cons: - It's a change and it's natural for us to resist it. - For people already familiar with the codebase, writing new tests or fixing current tests will require more work, as we may have to submit patches to multiple repositories. But this is a good thing: it'll help us keep in mind the API stability and better document and understand the changes that get into autotest.git. """ That was the most comprehensive take on the subject so far. So, if you care about giving your opinion, please give us a word here on this email thread! _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
