2009/11/12 Ralph Johnson <johnson at cs.uiuc.edu>:
>> All tests in CollectionTests are green except one unrelated
>> (ArrayTest>>testPrinting)
>
> But that is boring and obvious.
>
not for those who cares, and changed the printing behavior. But it was not me.

> What I want to know is that you don't break any tests on any published
> Squeak -based system.  I don't just mean all the tests in the standard
> Squeak images, I mean all the applications, too.
>
> I imagine that a change of this magnitude WILL break things.  Then we
> can discuss how badly it breaks things and how hard it is to fix.  If
> it only breaks a few applications, and they are easy to fix, then it
> is no big deal.  But the main problem with your proposal is that
> changing fundamental behavior of base classes is likely to break
> applications, and you won't address that questions with tests of
> collection classes.
>

Ralph, by putting such high demands you can kill any potential
initiative to see any changes in
existing core classes, not only mine.
Tests and only tests should cover all the cases, needed to be tested
against correct behavior.
If some application breaking up, it would mean only that either
current set of tests not sufficient, and therefore we
need better test coverage, or application plays against the rules and
breaking an encapsulation.
Testing against virtually every existing application is unreasonable
demand and nobody having time to do that.

> -Ralph
>
>



-- 
Best regards,
Igor Stasenko AKA sig.