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

Re: Issue #2064: regression test

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-11-17 22:34:22 CET

"Peter N. Lundblad" <peter@famlundblad.se> writes:

> I'm not checking the output of svn in each step, but instead checking the
> final contents of the files. I think this should be enough, but please
> tell me if it isn't for some reasons.

In general I prefer run_and_verify_commit over run_and_verify_svn
simply because it's less likely that a future change will cause the
test to pass when it should fail, e.g. consider what would happen if
merge failed to make the new file schedule add. Occasionally I use
run_and_verify_status when I feel that run_and_verify_commit would be

In this particular case run_and_verify_merge, which automatically
checks the dry-run merge, is *much* better than run_and_verify_svn.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 17 22:35:10 2004

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.