Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update issue with xml special chars in failure.#669

Merged
jgebal merged 1 commit intoutPLSQL:developfrom
lwasylow:develop
May 12, 2018
Merged

Update issue with xml special chars in failure.#669
jgebal merged 1 commit intoutPLSQL:developfrom
lwasylow:develop

Conversation

@lwasylow
Copy link
Copy Markdown
Member

Remove CDDATA and replace with xml convert
Text inside a CDDATA was not treated as xml so converting all characters was causing a poor display e.g.

Actual: 'test' (varchar2) was expected to equal: '<![CDATA[some stuff]]>' (varchar2)
"at "UT3.CHECK_FAIL_ESCAPE.FAIL_MISERABLY", line 4 ut3.ut.expect('test').to_equal('<![CDATA[some stuff]]>');

Converted all text using XML CONVERT and removing CDDATA allowed to generate proper result and escape CDDATA tags that caused failure of xml message.

Actual: 'test' (varchar2) was expected to equal: '<![CDATA[some stuff]]>' (varchar2)
"at "UT3.CHECK_FAIL_ESCAPE.FAIL_MISERABLY", line 4 ut3.ut.expect('test').to_equal('some stuff');"

XML content attached along with the screen from jenkins for that xml.
junit.txt

test_evidence

Remove CDDATA and replace with xml convert
@jgebal jgebal added this to the 3.1.2 milestone May 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants