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

Re: [PROPOSAL] more cmdline test cases for svnsync

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-06-23 19:36:25 CEST

On 6/23/06, Bhuvaneswaran Arumugam <bhuvan@collab.net> wrote:
> Hello,
> I see couple of cmdline test cases written in python for svnsync command
> though I dont see the test cases for following commands:
> svnsync --help
> svnsync help
> svnsync help bogus-cmd
> any other cmdline test cases ?
> I prefer to write one, if it adds value to the list of test cases. If
> you prefer me to write one, let me know following information:
> shall i include them in svnsync_tests.py ? or ..
> shall i include them in getopt_tests.py ? or ..
> shall i include them in a new script (may be svnsync_help_tests.py?) ?
> In this context, if it is preferred, which is the right location to
> place the expected output (stderr & stdout) files,
> getopt_tests_data/ or
> svnsync_tests_data/ directory or
> a new directory ?

Honestly, I think the time writing tests for svnsync's help command
could easily be better spent writing tests for basically any other
part of the system, but that's just me. I mean it's not like the help
command actually changes a whole lot, if there are bugs in it, report
them, and you can be fairly sure they're going to stay fixed...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 23 19:37:16 2006

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