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

Re: CVS update: subversion/subversion/tests/clients/cmdline README common.sh

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-03-27 12:25:18 CEST

On Mon, Mar 26, 2001 at 05:19:24PM -0800, Mo DeJong wrote:
>...
> Can folks take a look at these requirements and suggest
> any revisions or clarifications you think might be needed?

I like it, but for a couple nits:

*) automatic recovery is kind of a "3rd generation" type of thing for a test
   harness. that can get difficult. not saying it shouldn't be there, but
   our expectations should be set property to "probably not for a while"

*) the "Platform Specific Results" section is very unclear, and I think not
   entirely correct/appropriate. Specifically, I would think that we would
   NOT have platform-specific results -- that all platforms should end up
   the same. if there *are* differences, then CVS should have separate
   copies of each platform's expected output (where that differs from the
   "portable, expected output")

*) you imply that a set of information is saved from "the last run". I'm not
   sure that I buy into saving info about the last run. Essentially, I think
   each test suite run should be stateless. But if we *do* have a need for
   retaining state, then the doc might want to discuss where that is
   properly kept.

*) what's with the 40 column formatting? do you use really huge fonts or
   something, and so you have fewer columns on your screen? I'm finding it
   is actually harder to read the text when there is a newline every five
   words or so. (in the past, I've actually reformatted your emails before
   reading them)

I'd like to see your next draft checked into source control. I think it is
very well done, overall.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006

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.