[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

need suggestions on managing test data

From: Chris Curvey <ccurvey_at_gmail.com>
Date: 2005-10-13 14:30:16 CEST

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.
Received on Thu Oct 13 14:32:32 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.