lanbeier / testng-eclipse Goto Github PK

What steps will reproduce the problem?
1. Install the plugin Eclipse 3.3
2a. Try to run a test with Alt+Shift+X->N *** OR ***
2b. Try to run a test with right click on file -> Run As...

What is the expected output? What do you see instead?
2a. The test doesn't start
2b. I don't see the TestNG category under Run As...

What version of the product are you using? On what operating system?
Eclipse 3.3, with the latest plugin, on Windows Xp.

Please provide any additional information below.
Please fix it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

See http://jira.codehaus.org/browse/GRECLIPSE-476

Testng occasionally throws npes when looking for tests inside groovy files.
 This is because IType.getSource() for groovy files occasionally returns
null (this is OK according to the spec of that method.  However, this is
not handled in testng code.

I am attaching a patch to fix this problem.

What steps will reproduce the problem?
1. run a test case after another develper with committ rights changed a
.jar or alike.

What is the expected output? 
   The test case is executed OR there is an error message that better helps
resolving the problem

What do you see instead?
<<Parser] Running:
  /home/dev/workspace/proj1/temp-testng-customsuite.xml

[ClassHelper] Could not instantiate
com.company.product.test.mail.MailPdfTest:
com.company.product.test.mail.MailPdfTest
[ClassHelper] Could not instantiate
com.privasphere.privalope.test.mail.MailPdfTest:
com.privasphere.privalope.test.mail.MailPdfTest

===============================================
testPSPH
Total tests run: 0, Failures: 0, Skips: 0
===============================================

org.testng.TestNGException: 
Cannot find class in classpath: com.company.product.test.mail.MailPdfTest
    at org.testng.xml.XmlClass.getSupportClass(XmlClass.java:55)
    at org.testng.internal.Utils.xmlClassesToClasses(Utils.java:76)
    at org.testng.TestRunner.initMethods(TestRunner.java:281)
    at org.testng.TestRunner.init(TestRunner.java:227)
    at org.testng.TestRunner.init(TestRunner.java:189)
    at org.testng.TestRunner.<init>(TestRunner.java:150)
    at org.testng.remote.RemoteTestNG$1.newTestRunner(RemoteTestNG.java:102)
    at
org.testng.remote.RemoteTestNG$DelegatingTestRunnerFactory.newTestRunner(RemoteT
estNG.java:154)
    at
org.testng.SuiteRunner$ProxyTestRunnerFactory.newTestRunner(SuiteRunner.java:517
)
    at org.testng.SuiteRunner.privateRun(SuiteRunner.java:244)
    at org.testng.SuiteRunner.run(SuiteRunner.java:198)
    at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823)
    at org.testng.TestNG.runSuitesLocally(TestNG.java:790)
    at org.testng.TestNG.run(TestNG.java:708)
    at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124>>  

What version of the product are you using? On what operating system?
- TestNG 5.8.0.2
- Debian stable
- Eclipse 3.2.1


Please provide any additional information below.

Since the eclipse test project has dependencies to the real product eclipse
project and each test-case can have its own class-path as well, it would be
very helpful if 
1) this error would also print out the classpath it is searching on as well as 
2) the System.getProperty("user.dir") in case there are relative paths
3) the error would name the entity that defines the class-path (test-case,
project, depentent project X, ...)
4) if the classloader cascades through multiple class-paths list them
individually ...

To reproduce the problem, write a test with a data provider that causes the
test to be run multiple times.  Run the test, and look at the "Methods:
n/n" result shown in the TestNG View.  When done with the example code that
I will provide, the result is "Methods: 3/1".  This should either be
"Method: 1/1" or "Methods: 3/3", depending on whether it is reporting the
number of test methods, or the number of test method calls that are made.

Example.java:

public class Example {

    String value;

    public Example(String value) {
        this.value = value;
    }

    public String getValue() {
        return value;
    }
}

ExampleTest.java:

import static org.testng.Assert.assertEquals;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class ExampleTest {

    @DataProvider(name = "provider")
    public Object[][] provideValues() {
        return new Object[][]{{"foo"}, {"42"}, {"bar"}};
    }

    @Test(groups = {"unit"}, dataProvider = "provider")
    public void testValue(String value) {
        Example testObject = new Example(value);
        assertEquals(value, testObject.getValue());
    }
}

I am an avid user of the "run all tests in the selected project, package or
source folder" facility of the JUnit plugin.

Such a facility would be a great time-saver for this plugin.

What steps will reproduce the problem?
1. Create a test class in one package and "Run as test" -
temp-testng-customsuite.xml gets generated and tests run well
2. Refactor test class by changing it's package, e.g. add another
subpackage and move the test class there; delete temp-testng-customsuite.xml
3. "Run as test" on test class will create temp-testng-customsuite.xml with
old class path and test will fail, as if tho this information is cached
somewhere

What is the expected output? What do you see instead?
Expect no caching of class path.


What version of the product are you using? On what operating system?
Eclipse 3.3.2 with TestNG plugin 5.8.0.2
Java 1.6
TestNG 5.7 JDK 1.5

Please provide any additional information below.

It would be nice if you could configure the directory where this file is 
placed, and perhaps what it is called. This way, new users of a CVS / SCM 
managed project won't accidentally check it in.

Thanks :)

What steps will reproduce the problem?
1. Add new remote site (http://beust.com/eclipse)
2. Check box (http://beust.com/eclipse)
3. Hit install

What is the expected output? What do you see instead?

Expected plugin to install, instead, received this error:

Cannot complete the request.  See the details.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Unsatisfied dependency: [org.jboss.tools.birt.core 1.0.0.Alpha1]
requiredCapability: osgi.bundle/org.eclipse.birt.integration.wtp.ui/0.0.0
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.0.v3448f,3.4.0.v3448f]] and
Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt/[3.4.1.v3449c,3.4.1.v3449c]] can
be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.1.v3449c,3.4.1.v3
449c]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.100.r341_v20080814-98
9JESIEdAciFYfkZZsBfSwQ2341,3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.0.I20080610-1200,3.4.0.I20080610-1
200]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui/[3.4.1.M20080910-0800,3.4.1.M20080910-0
800]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v2008070
9,3.2.201.R34x_v20080709]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.201.R34x_v2008081
9,3.2.201.R34x_v20080819]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.100.v20080610,3.3.100.v20080610]
]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.help/[3.3.101.v20080702_34x,3.3.101.v20080
702_34x]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.101.
R34x_v20080731,1.0.101.R34x_v20080731]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.0.I20080606-1300,3.4.0.I
20080606-1300]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench/[3.4.1.M20080827-0800a,3.4.1.
M20080827-0800a]]
can be satisfied.
Cannot find a solution where both Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.0.v20080605-1900,3.4.0.v20080605
-1900]]
and Match[requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.osgi/[3.4.2.R34x_v20080826-1230,3.4.2.R34x
_v20080826-1230]]
can be satisfied.
Unsatisfied dependency: [org.maven.ide.eclipse.feature.feature.group
0.9.6.20080905-0917] requiredCapability:
org.eclipse.equinox.p2.iu/org.maven.ide.components.maven_model_edit/[1.0.0.20080
905-0917,1.0.0.20080905-0917]
Unsatisfied dependency: [org.jboss.tools.birt.feature.feature.group
1.0.0.Alpha1] requiredCapability:
org.eclipse.equinox.p2.iu/org.jboss.tools.birt.core/[1.0.0.Alpha1,1.0.0.Alpha1]
Unsatisfied dependency: [org.jboss.tools.birt.core 1.0.0.Alpha1]
requiredCapability: osgi.bundle/org.eclipse.birt.integration.wtp.ui/0.0.0
Unsatisfied dependency: [org.eclipse.rcp.feature.group
3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.update.configurator/[3.2.200.v20080417,3.2
.200.v20080417]
Unsatisfied dependency: [org.eclipse.rcp.feature.group
3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.rcp.feature.jar/[3.4.0.v20080324a-989JERhE
k-jWnd5IY8K5tjxB,3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB]
Unsatisfied dependency: [org.eclipse.rcp.feature.group
3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-200
6,3.2.200.v20080421-2006]
Unsatisfied dependency: [org.eclipse.rcp.feature.group
3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.swt.win32.win32.x86/[3.4.0.v3448f,3.4.0.v3
448f]
Unsatisfied dependency: [org.eclipse.rcp.feature.group
3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.equinox.launcher.win32.win32.x86/[1.0.100.
v20080509-1800,1.0.100.v20080509-1800]
Unsatisfied dependency: [org.maven.ide.eclipse.wtp.feature.feature.group
0.9.6.20080905-0917] requiredCapability:
org.eclipse.equinox.p2.iu/org.maven.ide.eclipse.feature.feature.group/0.0.0


What version of the product are you using? On what operating system?

Eclipse JEE 3.4.1

What steps will reproduce the problem?
1. Right click on a test method from source code
2. Select run as "testNG test"


What is the expected output? What do you see instead?
It should test only that method, and not the whole class.


What version of the product are you using? On what operating system?
5.8.0.2


Please provide any additional information below.

What steps will reproduce the problem?
1. Select a test method on testNG window
2. Rgiht click 

What is the expected output? What do you see instead?
It should appear something like "run", but I see only "go to declaration".


What version of the product are you using? On what operating system?
5.8.0.2


Please provide any additional information below.

What steps will reproduce the problem?
1. Create a testng.xml file in project
2. Right click on it, select Run As... TestNG Suite

What is the expected output? What do you see instead?

The tests should run (and were running yesterday).  Now I get an error:

'Launching src.test.java.testng.xml' has encountered a problem.
Unsupported launch configuratio [sic] type org.testng.eclipse.launchconfig

What version of the product are you using? On what operating system?
5.8.0.2 running on Eclipse 3.4.1 on OSX 10.5.

Please provide any additional information below.

What steps will reproduce the problem?

Frequently when trying to run a test by right clicking on the source editor
pane, the TestNG menu options are disabled. Typically this doesn't occur
when the Test class is first opened, but only after some modifications have
been made.

I either have to close and re-open the test or navigate to package explorer
and run the test by right clicking on the test there. 

What is the expected output? What do you see instead?
The TestNG menu should always be available from the editor pane for test
classes.

What version of the product are you using? On what operating system?
jdk1.5.0_11, 
Eclipse 3.2.1, 
TestNG eclipse plugin 5.1, 
moreUnit 0.5.2,

on Windows XP

Please provide any additional information below.

Caused by a package change ( plugin extends a JDT internal class ).

Trivial fix attached.

What steps will reproduce the problem?
1. Open eclipse
2. try to add a testng.jar to the project

What is the expected output? What do you see instead?
I expect to add a User Library to the project with source attached to it.
It should point to the latest and greatest plugin's testng.jar. (Or I could
choose from the jdk1.4 and jdk5 versions. If there will be an incompatible
update, then from the old version too. Similarly to the JUnit plugin.)
I see no choice. I have to create the jar, and the source attachement too.
Add it to the project, and do this every new release.

What version of the product are you using? On what operating system?
Europa. Linux, Windows.

Please provide any additional information below.
Usability feature request.

We are using the eclipse rcp framework a lot and missed the support for 
testing eclipse plugins (osgi bundles) using testng (integration 
testing). I have seen requests for such a feature in the past, but 
nobody seems to be working on it. Therefore I simply implemented it 
myself and here is the result. Following the open source mantra, I 
release early. This is the first version of the code I got working. 
Documentation is mostly missing and there are a few rought edges. But 
in general it fulfills my needs. The code borrows heavily from the 
org.eclipse.pde.junit.runtime and the org.eclipse.pde.ui plugins. I 
release the code under the EPL, like the original code. Please be aware 
that the copyright headers within the code are probably not correct 
yet.

In order to use the code you have to build the 
org.testng.eclipse.runtime plugin using eclipse, apply the patch
org.testng.eclipse-r125-plugin-support.patch (included in the tarball) to
the testng-eclipse plugin and install both in your ~/eclipse/dropins 
directory. After a relaunch you should have a new launch 
configuration "TestNG plugin". It works just like the JUnit Plug-in 
Test launch configuration and the TestNG configuration.

For one reason or the other, the output from svn diff has mixed line 
endings. Please be careful before committing to svn after applying the 
patch.

I hope this patch gets in after a little review.

What steps will reproduce the problem?
1. Using the TestNG plugin, create a runtime configuration based on a group
designation.
2. testng-eclipse auto-generated a temp-testng.xml file, with test
descriptor "G:<group name>" embedded in it.
3. testng-eclipse will start a test run, but fail when it is time to write
the results in the output directory.

What is the expected output? What do you see instead?
Expected output is a subdirectory utilizing the name of the group for
results. It fails to accomplish this due to "G:" being embedded in the
filename, which is illegal on a Windows-based system.

What version of the product are you using? On what operating system?
Using testng-eclipse 5.8.0.2, Eclipse 3.3, Windows XP.

I coded a patch to solve this, and tested it on my desktop with success:
Index: src/main/org/testng/eclipse/util/CustomSuite.java
===================================================================
--- src/main/org/testng/eclipse/util/CustomSuite.java   (revision 105)
+++ src/main/org/testng/eclipse/util/CustomSuite.java   (working copy)
@@ -333,7 +333,7 @@
   protected Collection/*<String>*/ m_packageNames;
   protected Collection/*<String>*/ m_classNames;
   protected Collection/*<String>*/ m_groupNames;
-  protected StringBuffer m_testName= new StringBuffer("G:");
+  protected StringBuffer m_testName= new StringBuffer("GRP-");

   public GroupListSuite(final String projectName,
                         final Collection packageNames,

Add ability to test a single method based on the cursor position within 
the editor window. Method to launch is defined by cursor position. If 
cursor is between methods the whole TestNG/JUnit class is launched.

This functionality exists in an open-source Eclipse plugin 
named "junitrunner" found here:
http://sourceforge.net/projects/junitrunner/

It's very useful since it does not force you to have to move your cursor 
to the Outline view or TestNG view to run a single method test.

What steps will reproduce the problem?
1. annotate a test method with groups = {"info request"}
2. Use the "Run" config dialog to setup a TestNG test on "Groups"
3. Browse, add the "info request" group into "Groups".

What is the expected output? What do you see instead?
If TestNG supports groups name with space, the text input/output widget may
need commas to separate the group names. However, the GUI seems to use one
word per group name so name with spaces will confuse the GUI. Should get a
warning when "Browse" is used.

What version of the product are you using? On what operating system?
  TestNG Eclipse 5.7, Eclipse 3.2.2 on Windows XP

What steps will reproduce the problem?
1. method A declared to be in group A1
2. method B declared to be in group B1 and dependsOnMethods={"A"}
3. create and run a test with only group "B1".

What is the expected output? What do you see instead?

  TestNG should catch the runtime exception and report that method "A" is
not found in the test e.g. "omitted in test setup". Exception is thrown,
the test is not run and not reported in the result as skipped.

What version of the product are you using? On what operating system?

TestNG 5.7.0.0, Eclipse 3.2.2, and Windows XP.

What steps will reproduce the problem?
1. Create a TestNG test in Project A with a @Test(groups="build")
2. Create a TestNG test in Project B with a @Test(groups="build")
3. Alter the build path of Project B so it depends on Project A
4. Open debug dialog
5. Create a new TestNG launch configuration
6. Select "Project B" for the Project
7. Click the "Groups" radio button
8. Click Browse and check the "build" group
9. Click Debug

What is the expected output? What do you see instead?
Actual: the tests in both Project A and Project B are run
Expected: just the test in Project B runs

What version of the product are you using? On what operating system?
Eclipse 3.3.0, Win XP SP2, org.testng.eclipse 5.7.0.1

Please provide any additional information below.
Alternatively, a checkbox that says "Include tests from prerequisite
packages" would be excellent.

What steps will reproduce the problem?
1. Create a run configuration, for example for the group 'util'
2. Run the test
3. Add another class to the group 'util'
4. Run the test

What is the expected output? What do you see instead?

I expect to see the already added classes + the new class test results, but
only the already added classes test results.

What steps will reproduce the problem?
1. Right click and on the 'Run As' menu select 'TestNG test'.

What is the expected output? What do you see instead?
The test should start running. Nothing happens.
If I right click and use the menu 'Test NG' > 'Run as test', it does work.

What version of the product are you using? On what operating system?
5.8.0.2

Please provide any additional information below.
Eclipse: 3.4.2

What steps will reproduce the problem?
1. Start Eclipse. Make sure you have the eclipse testing platform (TPTP)
and testng eclipse plugin installed.
2. Try and create a new profile executable

What is the expected output? What do you see instead?
The profile config dialog comes up (see attached).
I cannot locate the testng run type in the tree on the left like I can when
I create a normal or debug run profile.

What version of the product are you using? On what operating system?
TestNG 5.4.0.0
TPTP platform project 4.3.1v200701291655
Eclipse 3.2.2
Windows XP sp2

Please provide any additional information below.

Instead of statements like @Configuration(beforeMethod=true) the plugin
should generate @BeforeMethod

What steps will reproduce the problem?
1. Run any testng test inside eclipse. e.g. Right-click on class in the
Hierarchy View, select Run As TestNG Test
2. The testng test suite runs but no tests actually get executed. The
result in the console is "Total tests run: 0, Failures: 0, Skips: 0"


What is the expected output? What do you see instead?
It should run the tests in the class but the tests get ignored.

What version of the product are you using? On what operating system?
linux (Ubuntu 7.04) / eclipse 3.2.2 / testng plugin 5.5.0.1 / sun jdk 1.5.0_08

Please provide any additional information below.
I have figured out why it isn't seeing the tests. It generates the
temporary test suite xml file - temp-testng-customsuite.xml
which contains this:
<suite name="agency">
  <test verbose="2"
name="com.intuit.engine.efp.efe.agency.format.irs.payroll.ssa.SsaAckHelper_CNF_T
est"
annotations="javadoc">
    <classes>
      <class
name="com.intuit.engine.efp.efe.agency.format.irs.payroll.ssa.SsaAckHelper_CNF_T
est"/>
    </classes>
  </test>
</suite>

Note the annotations="javadoc" attribute. If I manually remove this from
the xml and then execute that xml file, it will work. So the problem is
that when it generates the xml file it has this attribute.

I don't know why it thinks I am using the javadoc style annotations. I am
using the standard jdk1.5 annotations. I have checked all the preferences
but I cannot see where I can tell it to use 1.5 annotations. Also, up until
recently my dev environment was on a WindowsXP box, the plugin worked fine
with eclipse in that environment. So maybe its a linux only bug.

How does the plugin detect the jvm? The default jvm at the OS level is a 
1.4 jvm. 
java version "1.4.2"
gij (GNU libgcj) version 4.1.2 (Ubuntu 4.1.2-0ubuntu5)

But I do not reference this jvm from inside my eclipse environment. My
eclipse environment is running on sun jdk 1.5 and my java compiler for the
entire environment is the same jdk.

Maybe the plugin thinks I'm using 1.4 becuase it incorrectly sees the 1.4
jvm on the system level path?

thanks,
Martin

After execute of this test testng plugin hangs on.
It is probably problem with "\n" char which elipse try to paint in plugin
window [testCrash("text \n")].

import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class someClassTest {
    @Test(dataProvider = "dp")
    public void testCrash(String text) {
        System.out.println( text );
    }

    @DataProvider(name = "dp")
    public Object[][] getData() {
        return new Object[][] { { "text \n" } };
    }
}

Testng plugin 5.5.0.1
Eclipse 3.2.2
Java 1.6.0_01-b06

>What steps will reproduce the problem?
1. setup test methods with some groups names
2. created a "Run" configuration with "Run..." Groups and "Browse"
3. Run the test
4. rename or delete one of the "groups" name in the test class.
5. Go back to the "Run" dialog and try to remove the old name or select new  
 name/new groups via browse

>What is the expected output? What do you see instead?

  being able to remove the old name, warning about invalid name. Also allow
new/valid names to be inserted into the configuration even with the invalid
name. Currently, it won't change the text input widget's content even it
seems to do it. After running the test, going back to the "Run" config
dialog will show that the old "Groups" were used if an invalid/old name was
in the group. Sometimes, using the GUI with renamed/delete group name will
report "null".

>What version of the product are you using? On what operating system?

TestNG Eclipse plugin 5.7, on Eclipse 3.2.2/Windows XP.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
I would like the ability change the MAIN_RUNNER from RemoteTestNG to a
custom RemoteTestNG. Primarily to Run Grails with TestNG in Eclipse.


What version of the product are you using? On what operating system?
Eclipse 3.3.x on Windows


Please provide any additional information below.
I looked at the code and found that there are a number of places that
RemoteTestNG.getClass.name() instead of using
TestNGPluginConstants.MAIN_RUNNER. I have changed that and added the
ability to change the MAIN_RUNNER through preferences for the project or
for the workspace. Changed TestNGLaunchConfigurationDelegate to get the
preference instead of the MAIN_RUNNER constant. I have attached a patch
file with my proposed changes. Please let me know if these are acceptable.

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)

What steps will reproduce the problem?
1. Create a class implementing IMethodInterceptor, and in List<IMethodInstance> 
intercept(List<IMethodInstance> method, ITestContext testContext) return a 
modified List with 
less elements 
2.
3.

What is the expected output? What do you see instead?
The plugin detected the change in size

What version of the product are you using? On what operating system?
TestNG 5.8

Please provide any additional information below.

What steps will reproduce the problem?
1. Open a TestNG .java file in editor. Hit F11 or choose Debug As... from 
toolbar.
2. See Debug As dialog with choice of TestNG Test, select TestNG Test, hit 
ok.
3. nothing happens.

What is the expected output? What do you see instead?
expected to see a new debug configuration created for testng test, but 
there is nothing in list in Debug Configurations dialog.

What version of the product are you using? On what operating system?
Eclipse 3.4.0, WinXP2

Please provide any additional information below.

What steps will reproduce the problem?
1. Try to install form help / software updates
2. Use http://beust.com/eclipse

I get this error:

An error occurred while collecting items to be installed
  No repository found containing: org.testng.eclipse/osgi.bundle/5.9.0.4
  No repository found containing:
org.testng.feature/org.eclipse.update.feature/5.9.0.4

# What steps will reproduce the problem?
The issue appears when in the XML configure the parallel="classes" attribute.
When the suite runs, the console shows:

[Parser] [WARN] Unknown value of attribute 'parallel' at suite level:
'classes'.

And all the tests not run in threads


# What is the expected output? What do you see instead?
Actual output:

[Parser] [WARN] Unknown value of attribute 'parallel' at suite level:
'classes'.
[Parser] Running:
  C:\Temp\workspace\example\testng.xml

init at main
firstB at main
init at main
secondB at main
firstA at main
tearDown at main
secondA at main
tearDown at main

Excepted output (like the command line, using threads)

>java -cp lib\testng-5.9-jdk15.jar;build org.testng.TestNG testng.xml
[Parser] Running:
  C:\Temp\workspace\example\testng.xml

init at pool-1-thread-1
init at pool-1-thread-3
firstB at pool-1-thread-1
firstA at pool-1-thread-2
secondA at pool-1-thread-3
secondB at pool-1-thread-1
tearDown at pool-1-thread-2
tearDown at pool-1-thread-1


# What version of the product are you using? On what operating system?
Eclipse IDE for Java EE Developers (163 MB) http://www.eclipse.org/downloads/
TestNG 5.9.0.2 Eclipse Plugin http://beust.com/eclipse
TestNG 5.9-jdk15
Java 1.6.0_03
Windows XP

What steps will reproduce the problem?
1. create an empty project in Eclipse, having testNg plugin installed 
"org.testng.eclipse_5.7.0.1"

2. add a new class, assign TestNg Jar "testng-jdk15.jar
" in build path of project

3. type following code in class

import org.testng.annotations.*;

public class TestNg {

    @Test
    public void test1(){
        System.out.println("Test");
    }

}

4. Right select the function in package explorer and click "RunAs" ->
"TestNg Test"

What is the expected output? What do you see instead?
Expected Output: Test (printed on console)
what i see: Exception in thread "main" java.lang.NullPointerException
    at
org.testng.xml.TestNGContentHandler.resolveEntity(TestNGContentHandler.java:73)
    at
com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(Unkn
own
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntityAsPerStax(
Unknown
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatc
h(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(Un
known
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next
(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocum
ent(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
    at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknow
n
Source)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at org.testng.xml.Parser.parseOneFile(Parser.java:261)
    at org.testng.xml.Parser.parse(Parser.java:158)
    at org.testng.TestNG.setTestSuites(TestNG.java:472)
    at org.testng.TestNG.configure(TestNG.java:882)
    at org.testng.remote.RemoteTestNG.configure(RemoteTestNG.java:49)
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:122)

What version of the product are you using? On what operating system?
Eclipse: Version: 3.3.1.1
         Build id: M20071023-1652
org.testng.eclipse_5.7.0.1
lib: testng-jdk15.jar

Please provide any additional information below.
1) Only  two libraries in build path
    - JRE System
    - TestNG

2) The xml generated by TestNg for the above test case is as follows
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Test">
  <test verbose="2" name="TestNg" annotations="JDK">
    <classes>
      <class name="TestNg"/>
    </classes>
  </test>
</suite>

screen shots attached

-VICKEY SACHDEVA

> What steps will reproduce the problem?
1. choose group, browse, select a group
2. take a test where the group is in annotation @Test(groups = { "grpHere" })
3. put a break-point inside that test
4. Run TestNG in Debug output

> What is the expected output? 
In the console, I would like to see my log.debug output and the execution
to stop at my break-point
> What do you see instead?
===============================================
    G:grpHere
    Tests run: 0, Failures: 0, Skips: 0
===============================================


===============================================
myProject by groups
Total tests run: 0, Failures: 0, Skips: 0
===============================================

What version of the product are you using? On what operating system?
5.8.0.2

>Please provide any additional information below.
jdk1.5.0_14 on Debian stable

What steps will reproduce the problem?
1. Declare a base Test class which belongs to group "init"
2. Extends BaseClass by Class2, and annotation is @Test(dependsOnGroups =
{"init.*"})
3. Run Class2, Eclipse gives warning "group dependency is skip due to plug
in limitation."

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
Eclipse3.3.0, TestNG5.7

Please provide any additional information below.
Detailed step to reproduce the issue can be found at 
http://beust.com/weblog/archives/000170.html

Attached is a patch that addresses the following details:

What steps will reproduce the problem?
1. Open an existing JUnit test case.
2. Hit Ctrl+1 (Quick Fix), and when offered choice of conversion, choose
Java 5 annotations.

What is the expected output? What do you see instead?
Expected output is the testXXX methods to be wrapped in @Test, setUp
wrapped in @BeforeMethod, tearDown wrapped in @AfterMethod, and suite
wrapped in @Factory. To make test cases stay isolated (as define in JUnit),
each TestClass should define its own group.

Actual output are deprecated annotations.

In the spirit of "funtional" vs. "broken" vs. "checkin" style (as I read on
the site's documentation), it would be useful is this grouping was prefixed
"functional". For example, in test class TestMyPOJOs, it would be useful to
markup TestMyPOJOs.setUp with
@BeforeMethod(groups="functional.TestMyPOJOs"), each testXXX method with
@Test(groups="functional.TestMyPOJOs"), and so forth. This keeps setUp from
another auto-converted TestSomeOtherPOJOs, from interfering with this test
case.

This makes it easy to write a simple, run-everything-that-was-converted, by
manually building a testng.xml, with groups="functional.*" pattern.

What version of the product are you using? On what operating system?
TestNG 5.8.0.2, TestNG Eclipse plugin 5.8.0.5b, Windows XP, Eclipse 3.3

Please provide any additional information below.

Eclipse spots a lot of unused variables. I deleted the unused variables,
and also unused methods, to reduce the number of warnings.

I am also getting reports of deprecated Eclipse libraries, but I only
removed some of them. This may need to be reviewed, depending on what
versions of Eclipse this project wishes to sustain.

Also, I discovered that the formatting of existing source code was space
based, with 2-spaces per tab. I updated my Eclipse configuration to have
that format, and made it into a project-specific configuration file. This
should be put under control, in order to allow all developers to use the
same formatting style.

What steps will reproduce the problem?
1. Try to run or debug a TestNG Test using any means on given platform
2.
3.

What is the expected output? What do you see instead?
I expect test execution to begin. Instead Vista reports that "Java(TM)
Platform SE binary has stopped working" and Eclipse logs
"java.net.SocketException: Connection reset" (see attachment).

What version of the product are you using? On what operating system?
I'm using Java 1.6 update 6, Eclipse 3.3.2 build M20080221, and TestNG
plugin 5.7.0.1, all on Vista x64 business edition.

Please provide any additional information below.
Completely same setup, running and debugging same test works well on
Windows XP. Vista firewall is not an issue, same behavior occurs with
Firewall being turned off. Eclipse and workspace are in Users folder
("C:/Users/User/Work/Java/eclipse/").

What steps will reproduce the problem?
1. Create a group 'will_remove' on a test
2. Select 'will_remove' as a group and apply
3. remove 'will_remove' from unit test
4. Try to remove 'will_remove' from run configuration groups.

What is the expected output? What do you see instead?
To remove the non-existent group.  The group is not unselectable, which is
ok, if the GUI would remove all non-existing groups from the groups list. 
Instead you cannot add items as there is always an invalid group in the list. 

What version of the product are you using? On what operating system?
Version 5.8.0.2
Windows XP
Java 1.6.0

Please provide any additional information below.

If you define the DTD with to much spaces the FileSearchQuery fails.

This works:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">


This doesn't:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >

The patch I provided enables regex at the Filesearch and changes the search
string to:
<!.*DOCTYPE.*suite.*SYSTEM.*\"http://testng.org/testng-1.0.dtd\".*>

After this all suite.xml will be found.

Thorsten

I can only create this problem at work using different Eclipse version 
with similar results.

It seems that it is locking on the PrintWriter.

I'd appreciate your help.

Thank you,
Ben 

My Eclipse project workspace is in the default location in Windows which is
C:\Documents and Settings\Raj.Tiwari\workspace\MyProject

I have created a testng suite xml file. I right click on it and bring up
the debug launch config creator. I supply all the necessary information.
However, when I hit Debug, testng fails with the following:
java.io.FileNotFoundException: C:\Documents and
Settings\Raj.Tiwari\workspace\MyProject\Documents C:\Documents and
Settings\Raj.Tiwari\workspace\MyProject\and C:\Documents and
Settings\Raj.Tiwari\workspace\MyProject\Settings\Raj.Tiwari\workspace\MyProject\
src\test\com\sharon\util\FooTest.xml
(The filename, directory name, or volume label syntax is incorrect)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at org.testng.xml.Parser.<init>(Parser.java:68)
    at org.testng.TestNG.setTestSuites(TestNG.java:475)
    at org.testng.TestNG.configure(TestNG.java:902)
    at org.testng.remote.RemoteTestNG.configure(RemoteTestNG.java:49)
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:122)
WARNING: No test suite found.  Nothing to run

I am not sure where the multiple file locations are coming from. Any ideas
what might be going wrong here?

[deleted issue]

Feature request: stack trace filtering just like in junit plugin for Eclipse

It helps keeping the stack trace clean when tests fail.

What steps will reproduce the problem?
1. Create an abstract class with test annotations:
public abstract class AbstractTestHarness {
  @Test
  public void testSomething() {
    assert "Test" == getValue();
  }
  public abstract String getValue();
}
2. Create a sub-class with no annotations that supplies the concrete value:
public class MyTest extends AbstractTestHarness {
  public String getValue() {
    return "Test";
  }
}
3. Try to run 'MyTest'. via 'Run As...'

What is the expected output? What do you see instead?
The test class will be exercised by TestNG, but will not actually find any
tests. If you try to run it again, the TestNG context item will no longer
appear under the 'Run As...' menu.

Note that if I do the same thing with a testng.xml pointing to the MyTest
class, it finds the super-class test.

What version of the product are you using? On what operating system?
Eclipse Ganymede SR2 (3.4.2)
TestNG Plug-in 5.8.0.2 (latest from update site)

Please provide any additional information below.
<none>

What steps will reproduce the problem?
1. Create string constant in your test class and use it as group name in 
your @Test annotation.

   For example:
   public class MyTest {
        public static final String GROUP_A = "groupA";

        @Test(groups = { GROUP_A })
        public void testFoo() {
            // Implementation....
        }
   }

2. Create a new TestNG run configuration and browse your available groups. 
The list contains a "GROUP_A" group name insead of "groupA". If you select 
the GROUP_A and try to run the test, then no test will be run.

What is the expected output? What do you see instead?
I want to see the "groupA" instead of variable name in the group list.

What version of the product are you using? On what operating system?
WinXP, Eclipse 3.3.2 (Build-id: M20080221-1800), TestNG 5.8.0.2. 

I'd like to be able to list listeners i want to use for a testng launch 
configuration. from what i can tell, the only way to do that now for the 
testng eclipse plugin is to create an xml manually.

Good afternoons I am new in this technology. There is very interesting
similarity to me. On the one hand it wanted to present to them possible
bug. When it is created to @DataProvider with 2 parameters works, but with
3 or but parameters no longer it works. On the other hand I need help on
JUnitConverter. 

I am using version 5.3 of testng and 1,5 of java. 
When I play my build.xml to junit-converter, does not generate the classes
automatically to me testng from junit. 
build.xml file

</target> <target name= " init " > <taskdef resource= " testngtasks "/>
</target> <target name= " junitconvert " depends= " init " > to
<junit-converter sourcedir= " $ {source} “outputdir= " $ {testng_source}”/>
</target> 

<! -- being source where I have my .java --> 

My output is

init:
junitconvert:

[junit-converter] 0 files generated      !!!!!!!!!!!!!!

BUILD SUCCESSFUL
Total time: 2 seconds

Thanks and congratulations by the project

What steps will reproduce the problem?

Try to run any TestNG test using the "Run As" context menu. 

What is the expected output? What do you see instead?

Run As TestNG should appear in the context menu, but it does not!

What version of the product are you using? On what operating system?

org.testng.eclipse 5.6.0.0
eclipse 3.3
Ubuntu Linux 7.04

Please provide any additional information below.

.metadata/.log contains:

!ENTRY org.eclipse.core.resources 2 10035 2007-07-16 10:33:33.511
!MESSAGE The workspace exited with unsaved changes in the previous session;
refreshing workspace to recover changes.
!SESSION 2007-07-16 10:33:59.970
-----------------------------------------------
eclipse.buildId=I20070621-1340
java.version=1.6.0_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86

!ENTRY org.eclipse.debug.ui 4 0 2007-07-16 11:10:17.986
!MESSAGE Launch shortcut 'org.testng.eclipse.shortcut' enablement
expression caused exception. Shortcut was removed.
!STACK 1
org.eclipse.core.runtime.CoreException: No property tester contributes a
property isTest to type class org.eclipse.core.internal.resources.File
        at
org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExten
sionManager.java:109)
        at
org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.jav
a:95)
        at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeE
xpression.java:53)
        at
org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpressi
on.java:150)
        at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeE
xpression.java:53)
        at
org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.jav
a:69)
        at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeE
xpression.java:53)
        at
org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementEx
pression.java:43)
        at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalE
nablementExpression(LaunchShortcutExtension.java:282)
        at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.ge
tApplicableConfigurationTypes(LaunchConfigurationManager.java:714)
        at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.ge
tApplicableLaunchConfigurations(LaunchConfigurationManager.java:747)
        at
org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.getResou
rceLabel(LaunchingResourceManager.java:303)
        at
org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.computeL
abels(LaunchingResourceManager.java:207)
        at
org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager$2.run(La
unchingResourceManager.java:125)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.core.expressions 4 201 2007-07-16 11:10:17.987
!MESSAGE No property tester contributes a property isTest to type class
org.eclipse.core.internal.resources.File

I just switched to TestNG 5.3 (from 5.1) running on Mac OS X 10.4

I have some tests in 
com.xyzz.abcdef.ejb.sb.product.insertionpoint.SimpleTest

The popup menu does not recognize the tests (greyed out 'Run as Test')
moving it to 

com.xyzz.abcdef.ejb.sb.insertionpoint.SimpleTest

enables the test. When I use an xml-file to point to that test and try to run 
it from within eclipse,
it skips all my test


Parser] Running:
  /Users/qwer/Documents/Projects/abcdef/build-1.0/dev/src/server/abcdef_facade/ngtests/
com/xyzz/abcdef/ejb/sb/product/insertionpoint/insertionPointSuite.xml

[RunInfo] Adding method selector: org.testng.internal.XmlMethodSelector@ec115b 
priority: 10
[TestNGClassFinder] SKIPPING CLASS class 
com.axzz.abcdef.ejb.sb.product.insertionpoint.SimpleTest
[RunInfo] Adding method selector: org.testng.internal.XmlMethodSelector@609c13 
priority: 10
[TestNGClassFinder] SKIPPING CLASS class 
com.xyzz.abcdef.ejb.sb.product.NGTestDeleteProduct
[[SuiteRunner]] Created 2 TestRunners
[TestRunner] Running test Insertion Point Tests on 0  classes,  included 
groups:[] excluded 
groups:[]
[TestRunner] WILL BE RUN IN RANDOM ORDER:
[TestRunner] WILL BE RUN SEQUENTIALLY:
[TestRunner] ===
[TestRunner] Found 0 applicable methods

The test ran fine under TestNG 5.1 and still runs fine when invoked from ant.