On Thu, Apr 26, 2001 at 07:08:45PM -0500, Ben Collins-Sussman wrote:
> Sam TH <email@example.com> writes:
> > We take a regular working copy. We modify the repository it's from
> > via some other working copy. Then we update the working copy. We now
> > have a number of representations of what happend.
> > 1. The output of 'svn up'.
> > 2. The expected changes.
> > 3. The changes to the entries files.
> > 4. The changes to the actual working copy.
> > I really think that it's important that we verify that all of these
> > are consistent.
> Okay, now I understand your system. :)
> It's basically a world based on a single standardized "diff tree".
> You create "diff trees" based on the 4 situations above, and compare
> them all to each other.
> I understand that it has the advantage of potentially being more
> thorough and maintainable, but at the disadvantage of being more
> The deal is: the testing system I've been proposing is already done.
> I can compare "wc trees" to static expected ones, and I can compare
> "output trees" to static expected ones. That's *all I need* to write
> the tests we so desperately need, so I'm going to stop searching for
> the perfect design now.
Sounds totally reasonable. Once you get your stuff committed, I'll
work on extending the tree stuff so that it can handle all the stuff I
talked about. But by all means, get working tests going sooner rather
I'm looking forward to your next commit, so that I can get hacking.
sam th --- sam_at_uchicago.edu --- http://www.abisource.com/~sam/
OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key
Received on Sat Oct 21 14:36:29 2006
- application/pgp-signature attachment: stored