[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] more on the merge-fest

From: zander
Subject: Re: [Gnu-arch-users] more on the merge-fest
Date: Tue, 25 Nov 2003 20:11:32 +0100

On Tue, Nov 25, 2003 at 10:40:43AM -0800, Tom Lord wrote:
> I've now merged and tweaked (as per discussion):

Looking forward to a new release tarball.
ps. Please make that one have an easiliy parsable version number so
front-ends can check for versions! Thanx.

> ~ confidence was greatly increased
>   What I got from rob was code that passed the test suite and
>   that at least some bleeding-edgers had been using.   This 
>   made it much easier to tweak the code to fix the glitches.
>   For example, when removing the ".arch-inventory has a names
>   tag" functionality the process was:
>       1) fix the code
>         2) verify that it broke the test suite
>         3) study and fix the test suite

I may misunderstand the point here since I dont know the context, but this
seems a bit strange to me.
All the docu for java test suites tell it the other way around; if there
is a bug or a change in behavior you define the way it should work by
programming the test suite to do what you expect the API to do.
If the testsuite breaks (it will) then you fix the sources to make the
test suite pass.

I can point to some interresting documents that discuss this way of working,
but if I misuderstood then its not needed.
Let me know if you are interrested in documents describing best-methods for
unit testing..

Thomas Zander

reply via email to

[Prev in Thread] Current Thread [Next in Thread]