You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caused by: org.testng.TestNGException: java.nio.channels.ClosedChannelException
at org.testng.xml.SuiteXmlParser.parse(SuiteXmlParser.java:20)
at org.testng.xml.SuiteXmlParser.parse(SuiteXmlParser.java:9)
at org.testng.xml.Parser.parse(Parser.java:170)
at org.testng.TestNG.initializeSuitesAndJarFile(TestNG.java:279)
at org.testng.TestNG.run(TestNG.java:1081)
Notes
Both files exist and readable. Running just tests.xml is successful. Running with individually enumerated suite xml eg. tests1.xml, tests2.xml executes successfully.
Encountered while using TestNG in a maven project and assigning the suite xml programmatically with testNg.setXmlSuites(List<XmlSuite>);
Also, built 6.9.13 (Ubuntu 16.04 x64). Successful build. Jar in testng/build/libs/testng-6.9.13.jar. However there is 'no main manifest attribute'; so couldn't just do java -jar testng-6.9.13.jar suite-files.xml.
Went back to create a simple example. In doing so, found that during some pre-processing I set the xmlSuite.setFileName() which in turn made it self-referential I think. At any rate, removed this step and all is good in reading a suite xml file with suite-files declarations. Thank you for time and consideration.
TestNG Version
6.9.13
Expected behavior
Successful read of a suite-file.
Actual behavior
Notes
Both files exist and readable. Running just tests.xml is successful. Running with individually enumerated suite xml eg. tests1.xml, tests2.xml executes successfully.
Encountered while using TestNG in a maven project and assigning the suite xml programmatically with
testNg.setXmlSuites(List<XmlSuite>);
Also, built 6.9.13 (Ubuntu 16.04 x64). Successful build. Jar in testng/build/libs/testng-6.9.13.jar. However there is 'no main manifest attribute'; so couldn't just do java -jar testng-6.9.13.jar suite-files.xml.
Is the issue reproductible on runner?
Test case sample
suite-files.xml
tests.xml
The text was updated successfully, but these errors were encountered: