testng integration problems in 11.1

Hi,

11.1 has some issues related to testng integration.

  • i have defined in my pom.xml testng version 6.5.1
  • when i initially ran my tests i got a red popup about "!!! TestNG protocol incompatibility !!!". The tests still ran however
  • on a subsequent run i clicked the 'copy' link to make intellij copy my project testng to its plugin lib directory, then restarted
  • since then all test runs hang, nomatter what i change in plugin/lib directory or what version i have in pom.xml


I would like to get back to a state where i can at least run the tests, regardless of testng plugin version. Can i reset this somehow ? I've restarted the ide countless times and updated plugin/lib with all versions of testng i had in my local maven repo. I have read the relevant threads in the testng mailing lists, it would be nice if once and for all this integration would just 'work' out of the box.

Thanks
Jorg

4 comments
Comment actions Permalink

forgot to mention, the logs always show this when a test run is invoked:

012-04-16 11:03:21,686 [ 173345]   INFO -                  TestNG Runner - Language level is JDK_1_6
2012-04-16 11:03:21,686 [ 173345]   INFO -                  TestNG Runner - is15 is true
2012-04-16 11:03:21,686 [ 173345]   INFO -                  TestNG Runner - Test scope is: MODULE_WITH_DEPENDENCIES
2012-04-16 11:03:21,686 [ 173345]   INFO -                  TestNG Runner - Configuring for module:rdis2-workflow
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - com/beust/jcommander/ParameterException
java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException
 at org.testng.remote.strprotocol.BaseMessageSender.p(BaseMessageSender.java:204)
 at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:124)
 at com.theoryinpractice.testng.model.IDEARemoteTestRunnerClient$1.run(IDEARemoteTestRunnerClient.java:49)
Caused by: java.lang.ClassNotFoundException: com.beust.jcommander.ParameterException PluginClassLoader[TestNG-J, 8.0]
 at com.intellij.ide.plugins.cl.PluginClassLoader.loadClass(PluginClassLoader.java:77)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 ... 3 more
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - IntelliJ IDEA 11.1.1  Build #IU-117.117
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - JDK: 1.6.0_31
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - VM: Java HotSpot(TM) Client VM
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - Vendor: Sun Microsystems Inc.
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - OS: Windows XP
2012-04-16 11:03:22,014 [ 173673]  ERROR - llij.ide.plugins.PluginManager - Last Action: RunClass
2012-04-16 11:03:22,029 [ 173688]  ERROR - llij.ide.plugins.PluginManager - Original exception:  
java.lang.ClassNotFoundException: com.beust.jcommander.ParameterException PluginClassLoader[TestNG-J, 8.0]
 at com.intellij.ide.plugins.cl.PluginClassLoader.loadClass(PluginClassLoader.java:77)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at org.testng.remote.strprotocol.BaseMessageSender.p(BaseMessageSender.java:204)
 at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:124)
 at com.theoryinpractice.testng.model.IDEARemoteTestRunnerClient$1.run(IDEARemoteTestRunnerClient.java:49)

0
Comment actions Permalink

Jorg,

At the first time IDEA was running your tests with the bundled jar (so actually you didn't update the testng version). After you accept to copy your jar in the IDEA's plugin, IDEA run the tests with that jar. As that jar doesn't contain classes to start testng, you need to download the complete jar from testng.org in order to run your tests with the new version

Thanks

0
Comment actions Permalink

Thanks for the fast reply Anna, indeed that did the trick ! Integration with 6.4 works fine now, also tested with 6.5.1 that one seems ok as well.

One could argue then that the balloon text should not offer to copy the project testng dependency because that one will never contain the necessary classes to replace the bundled version.

0
Comment actions Permalink

Yes, I'll disable the link in this case. Thanks

0

Please sign in to leave a comment.