[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Initial version of svntest regression test framework is ready.

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2001-04-15 16:24:35 CEST

I may have mistaken the context of the argument, such that my last
message looks like an argument against Python as well as tcl. I
didn't realize that Mo's test framework was supposed to replace the
recent Python work as well as the C test framework.

Just to make myself clear:

        * I'd like to keep the number of languages in use in
          Subversion to a minimum. Even if only one language (C) is
          required to build and run the thing, developers should not
          have to learn more languages than necessary to hack on it.
          (Even if a language is simple, the tools to use and debug it
          are generally not.)

        * We definitely need tests written in C for unit testing.

        * I think people have made a convincing argument that we need
          some kind of high-level scripting language for black-box
          testing of programs, and that sh/awk is a poor choice
          because of portability to Windows and because sh/awk isn't
          good at poking around in XML format files. (Not that I
          would have chosen to use XML format files if the decision
          were mine, but that's neither here nor there.)

        * But I'd really hate to see two such languages introduced
          for that purpose because of developer preferences or to
          avoid a little bit of work.

I guess I'm a little concerned that cvs2svn (what we have of it) is
written in Perl and the test framework looks like it will be written
in python or (god forbid) tcl. Will a person working on cvs2svn need
to know both perl to hack on cvs2svn and python to write tests for the
features they add?
Received on Sat Oct 21 14:36:28 2006

This is an archived mail posted to the Subversion Dev mailing list.