Re: Making tests execute on multiple databases

[prev] [thread] [next] [Date index for 2005/05/04]

From: Matt S Trout
Subject: Re: Making tests execute on multiple databases
Date: 23:34 on 04 May 2005
On Wed, May 04, 2005 at 01:58:54PM -0400, Jim Brandt wrote:
> However, I found I wanted to run the same tests against Oracle. I was 
> able to modify some of the Films tests to do this, but it took some 
> work. It seems to me it would be really useful to be able to set some 
> configuration parameters to run the entire test suite against a 
> particular database. So when a new release was available, for example, 
> I could give it a connect_string, username, and password of a database 
> where the user would have privileges to create tables, etc. Then I 
> could run all the tests against Oracle. Other users could run against 
> their DBs.

Did you have to modify the running SQL or just the table creation statements.
If only the latter, maybe you could look at SQL::Translator for a means of
converting them to whatever database you prefer.

        -- 
            Matt S Trout            Brag sheet:    http://trout.me.uk/services.html
LAMP, Infrastructure        Contact:       services@xxxxx.xx.xx
   and Automation
     specialist                                       Do it once. Do it right.

Making tests execute on multiple databases
Jim Brandt 17:58 on 04 May 2005

Re: Making tests execute on multiple databases
Matt S Trout 23:34 on 04 May 2005

Re: Making tests execute on multiple databases
Tony Bowden 06:18 on 05 May 2005

Re: Making tests execute on multiple databases
Jim Brandt 11:53 on 05 May 2005

Generated at 11:49 on 06 May 2005 by mariachi v0.52