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

Checking for specific error messages (was: Re: svn trunk r16292: FAIL (x86_64-unknown-linux-gnu shared ra_dav bdb))

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-09-27 14:05:53 CEST

On Tue, 27 Sep 2005 svntest@jaa.iki.fi wrote:

> Running all tests in lock_tests.py...FAILURE

This is my new lock_tests 29 test, that expects a specific error message
that ra_dav doesn't produce. I'll fix this by extending the regex to
allow the DAV response as well.

While looking into this, I checked a lot of other invocations of
run_and_verify_svn, where an error is expected. Many (most?) places just
use SVNAnyOutput, and a few uses a specific error message. The former way
has the benefit that it that it doesn't break if an error message is
changed (or different in some RA/FS implementation), while it obviously
doesn't really check that the acutal error was the expected. Does anyone
have a good advise on how to handle this in general? Maybe we should have
a way to test for specific error codes, not just specific strings. That
might be useful for scripts as well (i.e. an option to always output error
codes with error messages.)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 27 14:07:52 2005

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