Issue 1: Converting a junit project to TestNG should generate a static import.
Project Member Reported by the.mind...@gmail.com, Sep 2, 2006
In eciplse I use the ctl-1 to convert my JUnit test class into a TestNG
test class. The generated code usually includes the statement:

import org.testng.AssertJUnit;

However to make my code work in Java 5.0 I need to change the import to

import static org.testng.AssertJUnit.*;


Since the converter already knows that my target environemnt in Java 5.0 I
think it should generate the import that way in the first place.

(submited by Paul Mendelson http://jira.opensymphony.com/browse/TESTNG-58)
Sep 2, 2006
Project Member #1 the.mind...@gmail.com
I see a possible problem: if you are on Java 5.0 you can write you assertions in 2
ways: Assert.assertEquals() (in which case it will not work) or assertEquals().
Considering that we cannot fix the first mode, maybe we can fix the 2nd one.

./alex
-- 
.w( the_mindstorm )p.
  TestNG co-founder 
Oct 13, 2010
#2 martinb...@gmail.com
There are the usual pro's and con's with Statics.

It would be great if the quick fix gave you the option of static and non-static imports

Thanks

For the great work Cedric!