sharpcvslib-developers

[Clayton H. <cla...@sp...>]

Hi,=20

I agree that we are going to need a way to load a repository to a
"known" state, two general comments:
     - I would like to push as much of this loading on the API as
possible. =20
     - Scripting can be accomplished with a nant.
     - Where the loading is not possible we should script a call to a
cvs binary with ant and flag that as a to-be-removed


Inline comments/ suggestions below.

>    * In the testing folder set up a subfolder of  files to be posted /
>      retreived for testing purposes. These can be anything we  (or the
>      user) wants to use.

I would suggest using a cvs module in the sharpcvslib repository on
sf.net, read only as far as the application is concerned.  We could
create a task called say "import-to-local" that would checkout from this
location and import into a local repository.

>    * Also create a setup folder, that contains the scripts needed to
>      setup/delete the test module on the CVS server. These scripts
>      would be ran before the tes suite was ran, so we know where we
are
>      starting from. We would have to provide scripts for all platforms
>      (*nix, Mac, and Win).

We could use nant to script this quite easily.  There is support there
for *nix and Win (maybe Mac too, although I don't think that has been
tested) and it will help test the tasks/ interface we are providing for
them.

>    * We could use/setup a local cvs server for testing purposes,
though
>      this might not test all the protocol interfaces that would be
>      needed. I do not know if there is a Mac server module either.

I think this would work and we should be able to test all protocols.

>    * Provide documentation for the setup and use of the testing suite.

I really like the documentation idea :-)!



Cheers,


Clayton