I don&#39;t think it is a good idea to have hierarchies with test cases... depending on how you are doing it, it could couple the test hierarchy with the model hierarchy and I don&#39;t think that is a good idea...<div>It also introduces some complexity, for example the number of tests are not only the test methods but for each concrete test class, the test methods on it plus the test methods of the abstract superclasses... hmmm I don&#39;t know, it is not natural at least for me too user inheritance with tests...<br>
<br><div class="gmail_quote">On Wed, Apr 29, 2009 at 4:46 PM, St�phane Ducasse <span dir="ltr">&lt;<a href="mailto:stephane.ducasse@inria.fr">stephane.ducasse@inria.fr</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
HI guys<br>
<br>
I was coding this afternoon with Cyrille who is working a lot to<br>
improve the test coverage of collections.<br>
And we found a bit strange that when a testcase inherits from another<br>
one the tests of the superclass are not run.<br>
I checked a bit SUnit code and superclass testmethods are only run is<br>
the superclass is abstract or if there are not testmethods.<br>
Imagine<br>
 � � � �BagTest<br>
 � � � � � � � �IdentityBagTest<br>
<br>
<br>
We could redefine buildSuite on BagTest to invoke allSelectors<br>
but this means in essence that we could do it on a lot of potential<br>
testcase classes that may be subclasses.<br>
<br>
Or we could redefine buildSuite on IdentyBagTest but this means that<br>
the subclasses should specify it.<br>
May be this solution is the best but I wanted to get your thoughts.<br>
<br>
Of course this idea of inheriting test case make sense when superclass<br>
setup can be reused in subclasses one.<br>
So the default behavior of buildSuite always invoking all testmethods<br>
may not be so good but then<br>
via subclassing from BagTest if this is not to reuse it.<br>
<br>
Stef<br>
<div><div></div><div class="h5"><br>
<br>
On Apr 29, 2009, at 6:04 PM, Cyrille Delaunay wrote:<br>
<br>
&gt; A change have been saved in &#39;PharoInBox&#39; for class TestCase in<br>
&gt; package SUnit<br>
&gt; so that suite are now built from allSelectors.<br>
&gt; This makes sense when you have testcase classes which inherits from<br>
&gt; each other and have parametrized (hook-based) setup.<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Pharo-project mailing list<br>
&gt; <a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a><br>
&gt; <a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br>
&gt;<br>
<br>
<br>
_______________________________________________<br>
Pharo-project mailing list<br>
<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a><br>
<a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br>
</div></div></blockquote></div><br></div>