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

Re: svntest and directory structure

From: Madan U Sreenivasan <madan_at_collab.net>
Date: 2006-06-20 08:53:13 CEST

On Tue, 20 Jun 2006 02:15:55 +0530, David James <djames@collab.net> wrote:

> On 6/19/06, Madan U Sreenivasan <madan@collab.net> wrote:
> Currently, the Python core unittest framework does not directly
> support XFail or Skipped tests, but it's quite possible to extend it
> to support these features. For an example, see
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/466288

Sure, but we already have that functionality in svntest. My point was to
have a single common framework for python testing that gave these features.

But your summarization below neatly sums it up, so, am not insisting on
this point. :)

> Note that the above recipe uses decorators and therefore requires
> Python 2.4. We could probably tweak the above recipe to work with
> Python 2.2 with a little bit of thinking.
> In general, I don't see a compelling reason to switch the Python
> bindings tests to use svntest. The svntest test suite is mainly
> designed for testing the output of command-line programs. PyUnit is
> designed to test Python programs.
> PyUnit has many useful features which svntest does not. For example:
> assertRaises
> assertEqual
> failUnless
> If svntest used PyUnit (the standard Python test framework), then we
> might be able to make use of its features in the Python bindings. But,
> right now, we don't do that -- instead, we rolled our own custom test
> framework, which has some nice features, but is not as powerful in
> general as PyUnit.

I Agree.

> Some options for future work:
> - Extend the Python bindings test framework to support XFail tests
> Some more controversial options:
> - Upgrade the 'svntest' framework to use PyUnit (NOTE: This switch
> will require some careful design before we write any patches.)
> - Upgrade both the Python bindings test framework and the svntest
> framework to share common code.

Bravo! neatly summed up, an in easier to approach steps. :)

> Madan, I think it'd be more useful if we focused on the simple things
> first: Let's upgrade the Python bindings to support XFail tests, and
> then write tests for any missing functionality using this feature.

sure, David. I just couldn't help raising the red-flag before I went on to
implement XFail() (read reinvent the wheel) again.
Now I can do that in peace! :) Amen.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 20 08:23:01 2006

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