On Mon, 05 Jun 2006 20:01:28 +0530, Garrett Rooney
<rooneg@electricjellyfish.net> wrote:
> On 6/5/06, C. Michael Pilato <cmpilato@collab.net> wrote:
>> Madan U Sreenivasan wrote:
>> > - There are some existing test cases in
>> > subversion/bindings/swig/python/tests/. But, these are not
>> comprehensive
>> > (IMHO), and more importantly use imports from trac modules. Is there
>> some
>> > specific purpose for making the tests dependant on trac?
>>
>> We are using Trac's python bindings test suite.
>
> Last summer we imported part of the trac test suite, because it was
> the only available test suite for the python code, and they were
> willing to give it to us. It's not actually dependent on trac, it's
> stand alone, just depending on the code we have in the tree.
>
I see..
>> > - The tests only test on file:// based urls. I think we should have
>> tests
>> > like our existing cmdline tests, that can be run selectively on
>> file://,
>> > http:// and svn://
>>
>> Our python bindings are a test of the bindings themselves, not of the C
>> code
>> behind the bindings. I think it is sufficient to only perform file://
>> testing in the bindings tests because that will exercise the Python-to-C
>> translation code in exactly the same way testing over the other RA
>> layers would.
>
> +1
okay.
Thank you guys for clarifying :)
Regards,
Madan.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 5 16:37:04 2006