Paul Spencer <[EMAIL PROTECTED]> writes: > Arnaud, > 1) I have several test, 100+, and the number grows, so from a > management perspective extending each abstract test in each > implementation is not practical.
Paul, Maybe I am becoming intrusive (or is it obstrusive ? elusive ?) but this first statement seems strange to me and I don't understand why inheritance should entail project management problems. After all, this is the point of OO concept: write once and inherit behaviour. OF course I am not aware of your particular architecture but I believe that this is a matter of inheriting a single Suite class that will group all your test cases. Testing is designed in one place (the interface) and executed in many places. > > 2) I believe a testing project can be created the will use profiles to > test each implementation individually. This is a manageable > workaround, although it requires an additional step to prevent a > failing implementation from being deployed to the repository. Ignoring test failures in multiproject builds (only) ? Once again, not sure I understand stakes at odd and problems specific to your project. This does not seems to be a problem to me. 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]
