Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.0-beta-7
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Hi,
I have a test case that fails and thus the error is:
"Expected <xxxx> but was <yyyy>"
This is stored in the junit XML report as:
<error message="expected:<SELECT...> but was:<null>" [...]
But when it goes throught the first DVSL transformation to transform it into a valid xdoc, it is translated to:
<code>
junit.framework.ComparisonFailure: expected:<SELECT...> but was:<null>
[...]
And then xdoc:transform transforms it into HTML :
<code>
junit.framework.ComparisonFailure: expected:<SELECT...> but was:<null>
[...]
And the browser just simply ignore these unknown tags and displays:
"junit.framework.ComparisonFailure: expected: but was: at " [...]
How to correct?
Thanks
-Vincent
Issue Links
- is depended upon by
-
MAVEN-401
Release maven-b10
-
This issue will soon be resolved as we are going to use JSL instead of DVSL.