On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which is run twice - once for the
deprecated code and once for the new code.
Would it make sense to exclude the long-running tests of deprecated
classes by default?
Or maybe all the tests of deprecated classes should be skipped by
default?
In the case where entire packages have been deprecated, that would be
fairly easy.
By @Ignore'ing the tests for the deprecated classes, we'd run the
risk that a release contains failing code.
Sometimes deprecated code must be touched, e.g. to redirect the
internals toward new implementations (delegation). Bugs could be
introduced unknowingly.
Also the conversion of unit tests is not always trivial, and it is
very useful to see that converted units tests run in the same way
as those of the deprecated code.
Isn't it possible to tell Junit to not run some tests (i.e. the
opposite of "-Dtest=SomeTest")?
Regards,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
