BlueDragon.NET and JUnit XML report doesn't work (+fix)
2 views
Skip to first unread message
Tero Pikala
Sep 23, 2009, 9:52:30 AM9/23/09
to mxunit
When creating report using BD.NET / MXUnit / Ant generated xml report
contains empty WDDX packet after XML report.
I fixed that by adding CFABORT right after XML has been generated,
patch is below.
Tero
Index: runner/HttpAntRunner.cfc
===================================================================
--- runner/HttpAntRunner.cfc (revision 1223)
+++ runner/HttpAntRunner.cfc (working copy)
@@ -52,6 +52,7 @@
</cfcase>
<cfdefaultcase>#trim(arguments.results.getJUnitXMLResults())#</
cfdefaultcase>
</cfswitch>
+ <cfabort>
</cfoutput>
</cffunction>
contains empty WDDX packet after XML report.
I fixed that by adding CFABORT right after XML has been generated,
patch is below.
Tero
Index: runner/HttpAntRunner.cfc
===================================================================
--- runner/HttpAntRunner.cfc (revision 1223)
+++ runner/HttpAntRunner.cfc (working copy)
@@ -52,6 +52,7 @@
</cfcase>
<cfdefaultcase>#trim(arguments.results.getJUnitXMLResults())#</
cfdefaultcase>
</cfswitch>
+ <cfabort>
</cfoutput>
</cffunction>
bill shelton
Sep 23, 2009, 10:24:39 AM9/23/09
to mxunit
Thanks for the patch, Tero! We welcome any help with Open BlueDragon
No reflection on your research, but executing a CFABORT in this
context to prevent wddx output smells of something else altogether. I
wonder if calling CFABORT simply killing some output stream?
bill
No reflection on your research, but executing a CFABORT in this
context to prevent wddx output smells of something else altogether. I
wonder if calling CFABORT simply killing some output stream?
bill
Tero Pikala
Sep 23, 2009, 10:30:25 AM9/23/09
to mxunit
Bill,
To be honest I didn't really investigate much why it's writing that
WDDX packet there. I suspect it has something to do with that WDDX is
usual output format when CFCs are called directly from URL?
Tero
To be honest I didn't really investigate much why it's writing that
WDDX packet there. I suspect it has something to do with that WDDX is
usual output format when CFCs are called directly from URL?
Tero
Peter J. Farrell
Sep 23, 2009, 6:14:41 PM9/23/09
to mxu...@googlegroups.com
Bill,
Have you rolled in my Open BD fixes I posted with my tickets? One of them was that the JUnit report returned a WDDX packet and not XML. I wonder if Tero uses my patch if it fixes the problem.
.Peter
Tero Pikala said the following on 09/23/2009 09:30 AM:
Have you rolled in my Open BD fixes I posted with my tickets? One of them was that the JUnit report returned a WDDX packet and not XML. I wonder if Tero uses my patch if it fixes the problem.
.Peter
Tero Pikala said the following on 09/23/2009 09:30 AM:
Reply all
Reply to author
Forward
0 new messages