OK, thanks.
So TestNG replaces JUnit in tapestry testing. I was a bit confused
because JUnit dependency was imported to tapestry project. But itself it
is a transitive dependency of TestNG (see maven pom.xml). Most likely it
does so for the transformation feature (JUnit->TestNG).
So far only worked with JUnit, but TestNG looks very promising.
Especially because it explicitly introduces integration test type. I
have seen JUnit often misused to test too much in one test case.
Thiago H. de Paula Figueiredo schrieb:
On Fri, Feb 20, 2009 at 10:49 PM, manuel aldana <[email protected]> wrote:
Hi,
Hi!
am testing around, what I noticed is that for unit tests imports (@Test,
asserts) testng is imported instead of junit packages. Afaik testng is about
integration tests,
Not true. From TestNG's website: "TestNG is designed to cover all
categories of tests: unit, functional, end-to-end, integration,
etc..."
--
manuel aldana
[email protected]
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
