Re: svn commit: rev 3311 - trunk/subversion/include trunk/subversion/libsvn_wc trunk/subversion/libsvn_subr trunk/subversion/libsvn_client trunk/subversion/tests/clients/cmdline trunk/subversion/tests

> cmpilato@collab.net writes:
> > Ick! Our notion of the "greek tree" has become a pretty consistent
> > idea over the past couple of years. Many of us I dare say know the
> > thing by heart. Is it necessary to add 'kappa' to every greek tree in
> > the universe to test this one feature (as opposed to the feature test
> > using an existing file or adding kappa as test-specific data)? If so,

hm.

initially i was just going to make 'iota' executable, but that seemed
to affect other tests in undesirable ways. of course, adding 'kappa'
ended up affecting other tests too, but in a way that was easily
generalized.

maybe 'adding kappa as test-specific data' would be the way to go...
the issue is the 'import' test. there aren't currently any 'import'
tests, because import is done in the setup code before every test.
so it seemed weird to me to add a test that would separately import
an executable file. but it might be worth it in order to not affect
the other tests (and not change the greek tree).

or, we could just add kappa to the other greek tree instances.

opinions?
i will explore the options tonight.

> > can we please add 'kappa' to the greek trees used by fs-tests and
> > repos-tests, too (see fs-helpers.c)? Oh, and the XML tests? And can
> > we update subversion/tests/greek-tree.txt?

ouch. i don't believe i didn't notice those... :-/

-brian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 02:26:05 2002