Quantcast
Channel: Adobe Community : Popular Discussions - FlexUnit
Viewing all articles
Browse latest Browse all 25673

FlexUnit XML reports lacking details

$
0
0

I have been working on integrating FlexUnit support into a CI framework at my company, and FlexUnit4's CI Ant tasks have been invaluable to me. So, kudos to the good folks here who have been working on FlexUnit4!

 

Now, my question: Is it just me, or does anyone else think that the XML reports generated by FlexUnit lack detail?

 

For instance, if I run a JUnit test in Java-land, any failures in the JUnit XML report contain not only the failure message, but also the stack traceback.e.g.:

 

  <testcase classname="com.solutions.di.tools.junit.AllTests" name="testRegProdGeoLvl" time="0.0">

    <error message="Timeout occurred. Please note the time in the report does not reflect the time until the timeout." type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout.

                at com.sas.djte.junit.JUnitCaller.callJUnit(JUnitCaller.java:364)

                at com.sas.djte.junit.JUnitCaller.execute(JUnitCaller.java:195)

                at groovy.util.AntBuilder.nodeCompleted(AntBuilder.java:212)

                at groovy.util.BuilderSupport.doInvokeMethod(BuilderSupport.java:147)

                at groovy.util.AntBuilder.doInvokeMethod(AntBuilder.java:162)

                at groovy.util.BuilderSupport.invokeMethod(BuilderSupport.java:64)

                at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)

                at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)

                at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)

                at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:129)

                at embedded_script_in_C__Program_Files_DJTE_import_dot_macrodef.run(embedded_script_in_C__Pr ogram_Files_DJTE_import_dot_macrodef:18)

                at org.codehaus.groovy.ant.Groovy.parseAndRunScript(Groovy.java:425)

                at org.codehaus.groovy.ant.Groovy.execGroovy(Groovy.java:404)

                at org.codehaus.groovy.ant.Groovy.execute(Groovy.java:279)

                at net.sf.antcontrib.logic.TryCatchTask.execute(TryCatchTask.java:207)

                at net.sf.antcontrib.logic.TryCatchTask.execute(TryCatchTask.java:207)

</error>

 

But with FlexUnit4, failures only seem to contain a brief message, no tracebacks:

 

  <testcase classname="com.commons.resources::ResourceLoaderTest" name="testLocalizedContentFRFR" time="0.000" status="failure">

    <failure message="ResourceLoader.LOCALE_CHANGED event did not fire as expected!!" type="com.commons.resources::ResourceLoaderTest.testLocalizedContentFRFR"><![CDATA[]]></f ailure>

  </testcase>

 

I am using the "verbose=true" setting with the <flexunit> Ant task.  Is there any plan to beef up the output in the reported XML results?

 

Thanks,

Trevor

 


Viewing all articles
Browse latest Browse all 25673

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>