Hello Peter
Le 29/09/12 17:50, Peter K a écrit :
For tests I would go mainstream, so pure junit or pure testng. One
approach would be using testng for some modules and testng for others
like Chris suggested.
So e.g. in SIS use testng only where it is really necessary. I for
myself cannot live without unit tests but I'm comfortable with junit as
well as testng.
Thanks for the feedback. So I'm tempted to stick with JUnit (without
external extensions) and copies (with adaptations) the 2
Apache2-licensed classes from "junit-team/junit.contrib" under the
sis-utility/src/test of Apache SIS. Those classes are about 200 lines of
code all together, which seems reasonable to me. With the
functionalities of a @Dependency annotation, I would have no more
technical reasons to go for TestNG.
Any objections?
Martin
