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

svnadmin dump/load, svndumpfilter regression tests

From: Alexander Sabourenkov <screwdriver_at_lxnt.info>
Date: 2003-07-17 11:12:23 CEST


I thought on how to check and be exactly sure that the svndumpfilter ( and
svnadmin dump too) work as expected and came up with the following:

1. Create a test repository. Stuff there several revisions, with
modifications, copies and deletes.

2. Do a dump/load into another repository.

3. Check out every revision out of both repositories and compare resulting
working copies. Or maybe export instead of checkout.

4. Repeat step 2 using svndumpfilter. For example:
- filter out a node that has only been modified.
- filter out a node that has been copied
- filter out a node that has been moved
- filter out a node that has been moved and another node was created with the
same name in later revision
- etc

5. Repeat step 3.

This tests both dump and load operations simultaneously. If there is a bug in
one of them, somebody will have a harder than possible time hunting it down.

One way to test them separately is to
for load - generate dumpstream, load, query the repo via cmdline client, compare.

for dump - create repo, do some commits with cmdline client, dump, compare.

But this requres dumpstream generator and parser in python. Which will have
their own bugs.

Any thoughts?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 17 11:13:23 2003

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

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