Clayton's responding message is also attached.
It seems as if we are in agreement that a testing setup can be
achieved. As for the network I have here, I can set up the CVS server
here on Linux or Win2k, but I can not provide access to the outside
I not familiar with nant, though I am not adverse to learning
something else new. And seeing that it is a .NET build tool, I guess I
will probably need it anyway.
I will take some time over the next week to look at a possible
solution to setting up this enviroment and get back with you.
Gerald Evans wrote:
> Yes, that's along the lines I was thinking.
> Must admit I hadn't really thought about the Mac. I would consider
> this low priority for now, but would be nice to add to the
> compatibility list at some point.
> I don't know what sort of network setup you have, but the ideal
> situation would be to have a cvs server running on your LAN.
> Preferably *nix with a standard cvs distribution, but at some point
> will also need to test with CVSNT as well. This then avoids the
> problem of needing shell access to an internet server.
> At 11:18 30/09/2003 -0400, JAW wrote:
>> I understand the need for setting up a 'known' base for testing. May
>> I suggest the following:
>> * 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.
>> * 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/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.
>> * Provide documentation for the setup and use of the testing suite.
>> Any other suggestions ? Comments ?
>> Gerald Evans wrote:
>>> Hi Jerry,
>>> First I've only been on the project a couple of weeks myself, so I
>>> am still finding my way around.
>>> The main area of testing that's left is testing the commands
>>> together with the requests and responses. Clayton has already added
>>> a few tests for those commands that do not modify the cvs repository.
>>> The big problem is testing the commands that do update the
>>> repository. It's still early days, but the current plan is to attack
>>> this at 2 levels.
>>> First we need the ability to intercept the output of the commands
>>> and to inject our own responses. (Clayton has been looking to see if
>>> the current code can be changed to make use of delegates to simplify
>>> Secondly, we want to be able to perform API tests using a real (but
>>> trashable) cvs repository. The current configuration class will be
>>> extended to have a test section where the location and
>>> authentication details for this repository can be specified.
>>> For each test it will be a matter of making sure that the cvs
>>> repository is in a known fixed state possibly using external cvs
>>> commands, doing the actual test and then checking that the
>>> repository is in the expected state.
>>> I'm busy on other work this week, so I'm not going to make any
>>> progress on either of these untill next week. If you want to tackle
>>> one of these then please do.
>>> Alternatively you could do some unit tests for the requests and
>>> responses. These are all very small trivial classes, but would be
>>> nice to have unit tests for them even if it's just for completeness.
>>> Hope there is something suitable here for you to look into,
>>> At 09:11 30/09/2003 -0400, JAW wrote:
>>>> Clayton ask me to ping this list to offer my services for helping
>>>> out. He had mentioned that there is a need in the unit testing
>>>> area. I also see that Gerald Evans is the coordinator of this
>>>> effort. Gerald, let me know what areas are available and I will
>>>> start to look into them.
>>>> Thanks !
>>>> This sf.net email is sponsored by:ThinkGeek
>>>> Welcome to geek heaven.
>>>> Sharpcvslib-developers mailing list
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> Sharpcvslib-developers mailing list