Testing against a huge repository is a slow proposition, even at a rate of 3 to 4 revisions per second.
Create a test runner that accepts short subversion dumps, replays them with a variety of back ends, and verifies that (a) the program didn't blow up; (b) the results match expectations.
Creating a test might go something like this:
Initialize a test Subversion repository.
Check it out to a working directory.
Perform the test-case operations in the working directory, committing as needed.
Dump the test repository.
Submit the dump for inclusion in the test suite.
The test suite might:
Load the dump into a temporary repository.
Walk the dump file, comparing each revision after commit against the corresponding Subversion revision.
Testing against a huge repository is a slow proposition, even at a rate of 3 to 4 revisions per second.
Create a test runner that accepts short subversion dumps, replays them with a variety of back ends, and verifies that (a) the program didn't blow up; (b) the results match expectations.
Creating a test might go something like this:
The test suite might: