<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 1/16/14 11:36 AM, Tom Zeller wrote:<br>
</div>
<blockquote
cite="mid:CAMNmQDRtBRGRCahCD+wwKd-H0oXce2RUg=rNCqWU6fL-qiFKkw@mail.gmail.com"
type="cite">
<pre wrap="">
I ask because the Spring test class extends JUnit,
</pre>
</blockquote>
<br>
I just wanted to note that for v3, based on Chad's intentions and
IIRC strong opinion on the matter, we have gone to great lengths to
eliminate any actual dependency and use of JUnit (some of our
dependencies might have a formal Maven dependency on it, but I
thought we were generally using Maven 'excludes' to exclude it.
Possible we missed something somewhere though). For example, for
XMLUnit we even cloned their JUnit-based assert class code and
produced our own that uses TestNG asserts instead so we could
exclude the JUnit dependency.<br>
<br>
Not saying we can't go down the JUnit road if that makes sense, if
it simplifies WebFlow testing etc.... But one practical point is
that if we have both TestNG and JUnit tests, especially mixed in the
same project, that might complicate how our test suites run, and
results reported, etc. Not sure how that works, never tried to mix
the two.<br>
<br>
<br>
</body>
</html>