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
I am using utPLSQL-sql-cli to let the UT_XUNIT_REPORTER create a file with the results of the utplsql3 unit tests. My Jenkins pipeline project should pick up the generated xml, but is giving an arror after I have added a test with a description that contains an "<" character, e.g. -- %test(Test a case where A <> B)
Jenkins reports the following error: Failed to read test report file C:\Jenkins\workspace\A\utPLSQL-sql-cli\unit_test_output.xml org.dom4j.DocumentException: Error on line 1246 of document : The value of attribute "name" associated with an element type "testcase" must not contain the '<' character.
I would expect that I can use special XML characters in the name of a test, and that the reporter will escape them.
The text was updated successfully, but these errors were encountered:
Resolves#499
Unified reporting of failures across reporters.
With that change, expectation results are only kept in `ut_test` for failed expectations.
XUnit reporter now reports also the line of the test where an expectation has failed.
Resolves#487
I am using utPLSQL-sql-cli to let the UT_XUNIT_REPORTER create a file with the results of the utplsql3 unit tests. My Jenkins pipeline project should pick up the generated xml, but is giving an arror after I have added a test with a description that contains an "<" character, e.g.
-- %test(Test a case where A <> B)Jenkins reports the following error:
Failed to read test report file C:\Jenkins\workspace\A\utPLSQL-sql-cli\unit_test_output.xml org.dom4j.DocumentException: Error on line 1246 of document : The value of attribute "name" associated with an element type "testcase" must not contain the '<' character.I would expect that I can use special XML characters in the name of a test, and that the reporter will escape them.
The text was updated successfully, but these errors were encountered: