It is a must. We have to got all the tests in green. But actually that isn't tested.

I'll make the tests, I'll fix them, and then I'll send the whole changes to merge in the baseline.

Cheers,

Mariano.


On Sat, May 22, 2010 at 2:58 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
the key point is that we would like to avoid to have red tests all the time
so fixing the as yet unclassified should be done before.


BTW Does anybody use
� � � �BadEqualer
� � � �HashTester
� � � �PrototypeTester

because so far I do not see anybody user of them.
They look like experiment code to me.

Stef

On May 22, 2010, at 7:31 PM, Mariano Abel Coca wrote:

> Hi, I want to make global the checks included in ClassTestCase, and remove it. That is because actually it's only being tested for it's subclasses. And also, it's declaring that a subclass will be a class test instead of just a test, but no one of it's subclasses actually test the class, but the instances, therefore is a TestCase, not a ClassTestCase. See TimespanTest as an example.
>
> What Im saying is that I'm trying to force a run of a suit of Code Standards and Code Quality tests before sending something to merge to a baseline of a project.
>
> What do you think? Are you agree with that?
>
> Cheers,
>
> Mariano.
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project