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

Re: Issue tracker housecleaning: SVN-1722

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Thu, 17 Oct 2019 07:43:09 -0400

On Wed, Oct 16, 2019 at 4:46 AM Julian Foad <julianfoad_at_apache.org> wrote:

> Of course, ideally, it is lovely to improve the test coverage, if you
> have spare time and spare enthusiasm, or can do so really quickly so it
> doesn't impact other activities. However, it's not required and not
> necessarily worth it. A perfectly valid choice would be to prioritize
> moving on instead to reviewing another old open issue.

I have the enthusiasm:-)

More importantly this is an opportunity to learn more about the test

Is it possible, through some incantation that I've overlooked, to run the
cmdline tests against an arbitrary svn binary?

Or, perhaps a better question is: how do you verify that a test fails on an
old version and passes on a new version? (I happen to have 1.8 installed so
I'd like to verify that my new test fails on the 1.8 client and passes on

Received on 2019-10-17 13:43:26 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.