[Mono-list] Need feedback on NUnit testcase
Tue, 7 May 2002 13:15:21 -0700 (PDT)
--- Brad Wilson <email@example.com> wrote:
> Miguel de Icaza wrote:
> > Ideally, yes. The idea is to make sure that our
> implementation does
> > what it advertises it does. Sometimes a change on
> the code will have
> > side effects, and this will help catch those side
> effects right away,
> > rather than a few weeks or months down the line
> when it will be harder
> > to debug.
> +1. I think "Unit testing for compliance" is a whole
> different thing from
> the typical "unit testing for catching the majority
> of bugs".
Yes, I agree with Brad. Those are two different
animals. It could be bug free but only 80%-90%
compatible with Microsoft or ECMA .NET behavior. Maybe
in the future will be needed a 'Compatibility Team'.
*Roughly* similar to what IBM did when they ported to
Java its "San Francisco" Financial framework, I also
like the history and archeology of SW projects. They
created a Performance team along with the Design &
Development team. With the performance team focused on
that, they shared their recommendations and
discoveries with other teams, that's waaay back in the
early Java days.
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness