And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so by end of [[netbeans:TestNG2012|2012]].

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so by end of [[netbeans:TestNG2012|2012]].

However, the [[JUnit]] guys struck back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such, those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offering [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then, the adoption of [[TestNG]] slowed down, at least from my point of view, as an external observer.

However, the [[JUnit]] guys struck back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such, those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offering [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then, the adoption of [[TestNG]] slowed down, at least from my point of view, as an external observer.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

Still there are reasons to use [[TestNG]]. The [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with the widely accepted [[Apache]] license.

Also [[JUnit]] claims to support primarily ''unit'' testing. Sometimes it leads to [[OrderOfElements|ridiculous stories]] when [[JUnit]] project decides to prefer enforcing test isolation even it leads to irreproducible random test failures (probably to be [[OrderOfElements#Happy End|resolved in next version]]). When one needs more than ''just unit testing'', [[TestNG]] can still be viable alternative.

Also, [[JUnit]] claims to support primarily ''unit'' testing. Sometimes it leads to [[OrderOfElements|ridiculous stories]] when the [[JUnit]] project decided to prefer enforcing test isolation even when it leads to irreproducible random test failures (probably to be [[OrderOfElements#Happy End|resolved in next version]]). When one needs more than ''just unit testing'', [[TestNG]] can still be a viable alternative.

== Migrating from [[JUnit]]4 to [[TestNG]] ==

== Migrating from [[JUnit]]4 to [[TestNG]] ==

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve the [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s) was new. For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick, and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

However the [[JUnit]] guys struck back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

However, the [[JUnit]] guys struck back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such, those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offering [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then, the adoption of [[TestNG]] slowed down, at least from my point of view, as an external observer.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

harder than writing your own code from scratch, so congratulations [[netbeans:TestNGLukas|Lukáš]].

harder than writing your own code from scratch, so congratulations [[netbeans:TestNGLukas|Lukáš]].

I fully agree and I believe these words will guarantee A for [[netbeans:TestNGLukas|Lukáš]]'s thesis!

I fully agree and I believe these words guarantee A for [[netbeans:TestNGLukas|Lukáš]]'s thesis! Which is what happened on Jun 20, 2012 [[netbeans:TestNGLukas|Lukáš]]'s thesis was accepted and as it was the best provided on that date, it has been recommended for a special prize (which I don't know what it is yet). Congratulation Lukáši!

== Time to Migrate ==

== Time to Migrate ==

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so by end of [[netbeans:TestNG2012|2012]].

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so by end of [[netbeans:TestNG2012|2012]].

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

However the [[JUnit]] guys stroked back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

However the [[JUnit]] guys struck back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

== Time to Migrate ==

== Time to Migrate ==

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so for by end of [[netbeans:TestNG2012|2012]].

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so by end of [[netbeans:TestNG2012|2012]].

The whole system works like a drop-in [[bridge]]. The [[TestNG]] is compiled against [[JUnit]]4 sources, but itself does not contain the [[JUnit]] classes (otherwise we could not get rid of the [[CPL|obsolete license]]).

The whole system works like a drop-in [[bridge]]. The [[TestNG]] is compiled against [[JUnit]]4 sources, but itself does not contain the [[JUnit]] classes (otherwise we could not get rid of the [[CPL|obsolete license]]).

If [[TestNG]] [[JAR]] is used alone, it will not care about [[JUnit]] at all. If [[JUnit]] [[JAR]] is on the classpath as well, one of the two [[JUnit]]-related subsystems is initialized.

If [[TestNG]] [[JAR]] is used alone, it will not care about [[JUnit]] at all. If a [[JUnit]] [[JAR]] is on the classpath as well, one of the two [[JUnit]]-related subsystems is initialized.

One subsystem handles execution against [[JUnit]]3 binary and is just a slightly modified version of the original code written by Cédric. This one will be instantiated if old [[JUnit]] classes are found. If you are running [[TestNG]] with [[JUnit]]3 [[JAR]], this subsystem guarantees complete [[BackwardCompatibility|compatibility]] to what you are used to.

One subsystem handles execution against [[JUnit]]3 binary and is just a slightly modified version of the original code written by Cédric. This one will be instantiated if old [[JUnit]] classes are found. If you are running [[TestNG]] with [[JUnit]]3 [[JAR]], this subsystem guarantees complete [[BackwardCompatibility|compatibility]] to what you are used to.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

However the [[JUnit]] guys stroked back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

However the [[JUnit]] guys stroked back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#Coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

[[wikipedia:TestNG|TestNG]] is a testing harness created to improve [[JUnit]]3 experience. Tests can be annotated with [[annotation]]s and as such the design looked more modern when [[Java]]5 (and support for [[annotation]]s was new). For a while it seemed [[TestNG]] would take over the [[Java]] testing market. It was new, slick and it offered a way to execute [[JUnit]]3 tests in a [[BackwardCompatibility|compatible]] way.

However the [[JUnit]] guys stroked back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

However the [[JUnit]] guys stroked back by creating [[JUnit]]4, which basically copies the way [[TestNG]] uses [[annotation]]s. As such those who had previous investments in [[JUnit]]3 could just upgrade to [[JUnit]]4, keep [[BackwardCompatibility|compatibility]] and offer [[annotation]]s to those who wished to be [[good#coolness|free-cool-in]]. Since then the adoption of [[TestNG]] slowed down, at least from point of me, an external observer.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

Still there are reason to use [[TestNG]]. [[JUnit]] project decided to stick with [[CPL|archaic license]], long time superseded by [[EPL]], and at least [[Oracle]] is not comfortable with redistributing software [[CPL|under such license]]. [[TestNG]] comes with widely accepted [[Apache]] license.

== Time to Migrate ==

== Time to Migrate ==

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it the time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so for by end of [[netbeans:TestNG2012|2012]].

And what about you? Now, when it is so [[netbeans:TestNG_MixedMode|easy to migrate]] and when [[TestNG]] has such promising contributor like [[netbeans:TestNGLukas|Lukáš]], is not it a time to start incrementallly writing your [[TestNG|new generation]] tests too? [[NetBeans]] plans to do so for by end of [[netbeans:TestNG2012|2012]].