----- Original Message ----- From: "David Stagner" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Wednesday, January 09, 2002 08:31 Subject: Re: Task design question
> T Master wrote: > > >>design. The task would wrap Sybase BCP in order to copy controlled test > >>data into a database table, while preserving the data that was in the > >>table to be restored later. This way, multiple developers can share a > >>single development database without so much headache during testing. > >> > > > > What if multiple developers run the test at the same time on the same > > database table? > > Then they're screwed? > > As far as i'm concerned, the only real safe way to test database code is > to give every programmer their own personal private executive database. > Unfortunately, that's impractical in this environment (one of the few > things i liked about using MySQL rather than Sybase on a previous system > was everyone getting their own database without concern for licensing fees). > > But we do what we can. I want to at least *enable* unit testing with > controlled data, even if i can't guarantee that developers won't trip > over each other. > This issue crops up with any large system, where the 'system itself' is often the test target, but it is a rack full of expensive hardware. You need some kind of locking mechanism, which could be that you use SCM tasks to lock a file as indicator you need to run the tests, or you do what we do: run jabber locally and send a message to the team when you are about to run your tests, plus an informal protocol to gain an exclusive lock on the system for an overnight load test. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
