missing output

[Jeff F]

I just switched from junit to TestNG and am having some trouble with its reporting. When it hits an uncaught runtime exception, the stack trace isn't printed anywhere that I can find. I looked in the console, in the eclipse plugin's failure report, and in test-output/index.html.

For some reason, after each test, TestNG displays following error:
Error
DOMSource cannot be processed: check that saxon8-dom.jar is on the classpath
net.sf.saxon.trans.DynamicError: DOMSource cannot be processed: check that saxon8-dom.jar is on the classpath
at net.sf.saxon.event.Sender.send(Sender.java:184)
at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:28)
at org.testng.reporters.JUnitXMLReporter.generateReport(JUnitXMLReporter.java:152)
at org.testng.reporters.JUnitXMLReporter.onFinish(JUnitXMLReporter.java:111)
at org.testng.TestRunner.fireEvent(TestRunner.java:871)
at org.testng.TestRunner.afterRun(TestRunner.java:699)
at org.testng.TestRunner.run(TestRunner.java:484)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
at org.testng.SuiteRunner.run(SuiteRunner.java:168)
at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
at org.testng.TestNG.run(TestNG.java:719)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:122)
Error while writing out JUnitXML because of net.sf.saxon.trans.DynamicError: DOMSource cannot be processed: check that saxon8-dom.jar is on the classpath

I have saxon8.jar in my classpath. I tried to find saxon8-dom.jar to see what happens when it's included, but I couldn't find on ibiblio, the saxon website, TestNG's src distribution, or anywhere. (Is it actually a dependency?)

Any recommendations? I could live with this error if there was some other way to view uncaught exceptions & the stack trace.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=84047&messageID=150179#150179

[Cédric Beust ♔]

I think it's the opposite problem:  you should remove saxon from your classpath or put it at the very end.

--
Cédric

On 5/16/07, Jeff F <testng...@opensymphony.com> wrote:

I just switched from junit to TestNG and am having some trouble with its reporting.  When it hits an uncaught runtime exception, the stack trace isn't printed anywhere that I can find.  I looked in the console, in the eclipse plugin's failure report, and in test-output/index.html.

For some reason, after each test, TestNG displays following error:
Error
  DOMSource cannot be processed: check that saxon8-dom.jar is on the classpath
net.sf.saxon.trans.DynamicError: DOMSource cannot be processed: check that saxon8-dom.jar is on the classpath
        at net.sf.saxon.event.Sender.send(Sender.java:184)
        at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:28)

        at org.testng.reporters.JUnitXMLReporter.generateReport (JUnitXMLReporter.java:152)

        at org.testng.reporters.JUnitXMLReporter.onFinish(JUnitXMLReporter.java:111)
        at org.testng.TestRunner.fireEvent(TestRunner.java:871)

        at org.testng.TestRunner.afterRun (TestRunner.java:699)

        at org.testng.TestRunner.run(TestRunner.java:484)
        at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
        at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
        at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
        at org.testng.SuiteRunner.run(SuiteRunner.java:168)
        at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
        at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
        at org.testng.TestNG.run(TestNG.java:719)
        at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)

        at org.testng.remote.RemoteTestNG.main (RemoteTestNG.java:122)

[Alexandru Popescu ☀]

Can you please tell us what version are you using? (I remember I have
changed the JUnitXML report generator implementation to not use any
specific XML dependencies).

./alex
--
.w( the_mindstorm )p.
TestNG co-founder
EclipseTestNG Creator

[Jeff F]

It's v5.5. I just got started with TestNG this week for my web app. I downloaded the latest and copied the jars from the '3rdparty' dir to WEB-INF/lib. I'm not sure if it's relevant, but I also followed the instructions regarding the maven surefire craziness, to get things working outside of eclipse.

Thanks for your help with this! -Jeff

---------------------------------------------------------------------
Posted via Jive Forums

http://forums.opensymphony.com/thread.jspa?threadID=84047&messageID=150360#150360

[Alexandru Popescu ☀]

On 5/17/07, Jeff F <testng...@opensymphony.com> wrote:
>

> It's v5.5. I just got started with TestNG this week for my web app. I downloaded the latest and copied the jars from the '3rdparty' dir to WEB-INF/lib. I'm not sure if it's relevant, but I also followed the instructions regarding the maven surefire craziness, to get things working outside of eclipse.
>

I think that the changed I have mentioned in available only in SVN
trunk (and hoepfully in the beta download available from:
http://testng.org/testng-5.6beta-jdk15.jar).

./alex
--
.w( the_mindstorm )p.
TestNG co-founder
EclipseTestNG Creator

> Thanks for your help with this! -Jeff

[Jeff F]

No change with the download or with the svn trunk (r463)

Anything else I could try?

---------------------------------------------------------------------
Posted via Jive Forums

http://forums.opensymphony.com/thread.jspa?threadID=84047&messageID=150404#150404