I am +1 on separating integration tests... actually if we could have a category of tests that only runs on demand it would be nice (large tests below)
On Mon, Mar 25, 2013 at 11:57 AM, Andrew Purtell <[email protected]>wrote: > I think this is a good idea and you should look to Apache Whirr for the > launch automation. > > > On Mon, Mar 25, 2013 at 7:53 PM, Nick Dimiduk <[email protected]> wrote: > > > Heya, > > > > I'm interested in running integration tests that require a (small) > > distributed cluster via the regular jenkins build. Any advice on how to > go > > about doing thing? Launch the jobs via maven doesn't produce a realistic > > runtime, so this would be launching jobs with a bash script and > validating > > the exit code. It will probably involve deploying and tearing down a > > pseudo-distributed cluster too. > > > > I'm also thinking of changing the IntegrationTests category, breaking it > > into {Small,Large}IntegrationTests. Small are tests that require a > > distributed cluster to run but don't require lots of nodes or process > huge > > amounts of data. Think 10-20 minutes to run on a single > pseudo-distributed > > deployment. Large would be the catch-all bucket for everything else. > > > > This would also give us a harness from which we can automate the RC build > > validation. > > > > What do you guys think? > > > > -n > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
