RE: need suggestions on managing test data

Chris,

It might be better to have all your test code under a separate top-level directory, /test, then enable it via svn:externals. That way, if you wish to avoid the test directory, you'll be able to just call "svn co --ignore-externals".

Dale

-----Original Message-----
From: Chris Curvey [mailto:ccurvey@gmail.com]
Sent: Thursday, October 13, 2005 5:30 AM
To: Users Subversion
Subject: need suggestions on managing test data

Hi all,

My team has been using subversion successfully for a while now, but we're starting to run into a problem with the way we've arranged our repository.

We have the usual /trunk, /branches, /tags at the top level. Within trunk, we have /model, /controller, /util, and /tests. The /tests directory contains subdirectories that hold copies of various real-world datasets that we use for testing. (We want the copies in all their blemished glory.) But the datasets themselves can get pretty big (quite a bit bigger than the entire codeset), and while it's not terribly slow to add a single dataset to the repository, it's getting to be a pain to do a fresh checkout or export of the code (to integration or production).

So I was thinking about putting the tests in a directory that was not under /trunk, but I like being able to just export or checkout the entire project at once. Is there a way to say "export all the directories under /trunk *except* the one called /test" ? (I'd also like to do this so that we don't leave test code laying around in production.)

Thanks in advance.

-- 
Nervous passengers are advised to wear a blindfold. 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org