Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Groups & ExcludedGroups are ignored after first Ant-based test is run #82

Open
gszura opened this issue Aug 24, 2011 · 0 comments
Open

Comments

@gszura
Copy link

gszura commented Aug 24, 2011

ant config file (only important parts):

[...]
<target name="testNG-smoke">
    <testng groups="smoke"
            excludedgroups="broken, not-implemented"
            outputdir="${testNG.reports.dir}"
            classpathref="testNG.run.classpath">
        <xmlfileset dir="${testNG.config.dir}" includes="testng.xml" />
    </testng>
</target>
[...]

TestNG config file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
<test name="test set 1" preserve-order="false" verbose="5">
    <packages>
        <package name="xxx.xxx.xxx.set1.*" />
    </packages>
</test>
<test name="test set 2" preserve-order="false" verbose="5">
    <packages>
        <package name="xxx.xxx.xxx.set2.*" />
    </packages>
</test>
</suite>

Now when calling "testNG-smoke" ant target, information about included and excluded groups is used by TestNG while running tests from "test set 1", but they are ignored while running tests from "test set 2", so instead of tests from particular group only, all available tests are executed - from logs:

[...]
[testng] [TestRunner] Running test test set 1 on 62 classes, included groups:[smoke ] excluded groups:[broken not-implemented ]
[...]
[testng] [TestRunner] Running test test set 2 on 28 classes, included groups:[] excluded groups:[ ]
[...]

Last time it was working fine on TestNG 6.0.1.

I've found similar issue here, reported 4 years ago: http://jira.opensymphony.com/browse/TESTNG-194
This one most probably describe the same issue: #69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants