fs-test.c OH My

Hey,

OK so I've been moving some stuff around.

I believe that fs-test.c is going to be a problem long term however .
 For now I'll manage to get him(fs-test.c) to play nice with my current
changes. The problem will be when new FS implementations come along.
He(fs-test.c) is very closely coupled with the fs. He uses all levels
of the FS code.

Some questions:
Does the collective Subversion wisdom believe that "fs-tests.c" needs to
be this closely coupled to achieve proper validation?
If so, perhaps we should move portions of the code to libsvn_fs. The
relocated portions could be made part of a more formal testing api for
the FS. The api would then have to be implemented by all new fs
implementations.

If not, has anyone considered/sized the effort to make him use only the
FS api layer to perform his tests?

I feel like the tests should be made to use the API as much as possible.
 It seems to me that this will help to formalize the API.. If a test
case can't detect breakage externally, is anything really broken?

Anyhoo, I'll look at fs-test more later. I want to finish my current
mini-task first.

gat

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 28 21:37:32 2002