On Sun, 2011-05-01 at 08:41 +1000, Steve Barnes wrote: > Hi list > > A few questions regarding the scope of test scripts that have been requested: > > - is there a git repository or similar source that contains all of the currently available test scripts? It would be helpful to know that, given my copious spare time, I'm not re-inventing any > wheels or contributing the 57th LAMP install script. > > - relating to package installation test scripts, would there be any appreciable benefit to simply throwing everything + kitchen sink at the wall and see what _doesn't_ stick? (i.e., yum install > every single available package one after the other and record any failures?) This seems like a more...comprehensive method of uncovering package installation issues than me simply picking "my top 10 > favourite/most well known" yum packages. > > - is the scope for test scripts "anything you can think of that performs some kind of configuration change with a measurable return value" - e.g, tests that cover (for example) networking > configuration, partition/filesystem creation, package installation, firewall configuration, user/group account creation/deletion/editing, SSH key generation etc etc etc? > > - at present, each test script needs to be self-contained. To reduce the amount of code duplication/maintenance is there any intention (or objection) to developing a library of helper functions? > > Thank you! > > Steve > > > +1 I look forward to some comprehensive discussion with regards to this! I do like the kitchen sink idea - But not all packages can co exist, with default setups, like MTA's and such - Just my 2pence -- Mister IT Guru Blog http://solosysad.blogspot.com/ Twitter @misteritguru Follow me, I follow you - it's only fair