Paul Spencer <[EMAIL PROTECTED]> writes:
> Arnaud,
> In my case, I have an interface with several implementations. The
> intent is it to have an attached test which verifies that the
> implementation conforms to the interface. So each implementation will
> include the interface's attached test in addition to it's own unit
> test. By including the attached test in each implementation, then
> anytime an implementation is successfully built, by Continuum for
> example, you can me assured it also confirms to the interface.
>
> Paul Spencer
>
Paul,
That's nice and I think I would do the same. But then, why don't you
make four interfaces tests abstract and extends them in each module
for concrete implementations ?
abstract class ITest extends TestCase {
abstract void setImplem(I i0);
ITest(STring n) { super(n); }
public void testXXX() ...
}
class ImplemTest extends ITest {
ImplemTest(String n) {
super(n);
setImplem(this);
}
...
}
Your attached tests will not be considered for execution, which is ok.
Regards,
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
