Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing

On Thu, Jul 29, 2010 at 22:11, Thomas Rast [off-list ref] wrote:

Ævar Arnfjörð Bjarmason wrote:

quoted

  - Is this worthwhile. Are there developers / packagers / other
    interested parties here who'd be interested in actually running
    smoke testers? It should be really easy to set one up.

I'm all for it!

I think I could put a cronjob on a RHEL5.4 machine, and regularly run
it on my own openSuSE 11.3 install.

That's at least three smokers there. And since your RHEL5.4 machine
already turned up a gettext bug..

quoted

Tarball contents:

    $ tar xzvf git-smoke.tar.gz
    t0004-unwritable.sh
    t0001-init.sh
    t0002-gitfile.sh
    t0005-signals.sh
    t0000-basic.sh
    t0003-attributes.sh
    t0006-date.sh
    meta.yml

That's the only thing I found confusing about this: why are they named
as if they were shellscripts?

The output file names just match the test names, which in this case
are shellscripts.

Also, installing TAP::Harness::Archive was a bit hairy but that's
CPAN's fault...

This is something we can probably make really easy if we write some
supporting scripts with cpanminus + local::lib. I.e. just have a
config file like:

  ~/.gitsmoker:
    repository = ~/g/git
    data       = ~/g/git-smoker

Where the git-smoker would maintain the state, dependencies etc. It
needs.