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
If an XML file contains methods with less-than, greater-than, and ampersand symbols in the name, then the HTML report generated is displaying < , > , & for the method name instead of the actual symbol. This seems to be due to the xmlTransform function being executed on the method name which converts the & at the start of the entity into & which makes the rest of the entity invalid. If you click down to the "Method Coverage summary" then it ends up displaying correctly because that doesn't run the xmlTransform function.
It seems like the XMLHandler should normalize the element's attribute to convert the entities into the regular characters and then have an htmlTransform to convert the characters back into HTML entities later.
You can see this by loading the the test coverage.xml file in the test resources directory and seeing the <init> method.
The text was updated successfully, but these errors were encountered:
If an XML file contains methods with less-than, greater-than, and ampersand symbols in the name, then the HTML report generated is displaying
<
,>
,&
for the method name instead of the actual symbol. This seems to be due to the xmlTransform function being executed on the method name which converts the & at the start of the entity into&
which makes the rest of the entity invalid. If you click down to the "Method Coverage summary" then it ends up displaying correctly because that doesn't run the xmlTransform function.It seems like the XMLHandler should normalize the element's attribute to convert the entities into the regular characters and then have an htmlTransform to convert the characters back into HTML entities later.
You can see this by loading the the test coverage.xml file in the test resources directory and seeing the
<init>
method.The text was updated successfully, but these errors were encountered: