René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Crash of Realtime Report when server output contains \u003c![CDATA[...]]\u003e","articleBody":"When I run the realtime reporter via `ut3_tester_helper` for `ut3$user#` and the test `core.check_fail_escape.fail_miserably` exists the realtime reporter crashes while processing the following post-test event:\r\n\r\n```xml\r\n\u003cevent type=\"post-test\"\u003e\r\n  \u003ctest id=\"core.check_fail_escape.fail_miserably\"\u003e\r\n    \u003ctestNumber\u003e1\u003c/testNumber\u003e\r\n    \u003ctotalNumberOfTests\u003e673\u003c/totalNumberOfTests\u003e\r\n    \u003cstartTime\u003e2020-06-02T23:10:03.579607\u003c/startTime\u003e\r\n    \u003cendTime\u003e2020-06-02T23:10:03.591826\u003c/endTime\u003e\r\n    \u003cexecutionTime\u003e.012219\u003c/executionTime\u003e\r\n    \u003ccounter\u003e\r\n      \u003cdisabled\u003e0\u003c/disabled\u003e\r\n      \u003csuccess\u003e1\u003c/success\u003e\r\n      \u003cfailure\u003e0\u003c/failure\u003e\r\n      \u003cerror\u003e0\u003c/error\u003e\r\n      \u003cwarning\u003e0\u003c/warning\u003e\r\n    \u003c/counter\u003e\r\n    \u003cserverOutput\u003e\u003c![CDATA[FAILURE\r\n  Actual: 'test' (varchar2) was expected to equal: '\u003c![CDATA[some stuff]]\u003e' (varchar2)\r\n  at \"UT3$USER#.CHECK_FAIL_ESCAPE.FAIL_MISERABLY\", line 4 ut3_develop.ut.expect('test').to_equal('\u003c![CDATA[some stuff]]\u003e');\r\n]]\u003e\u003c/serverOutput\u003e\r\n  \u003c/test\u003e\r\n\u003c/event\u003e\r\n```\r\n\r\nThe realtime reporter gets stuck. It looks like this \"forever\" (I expect it to time out after 4h, but not checked ;-) ). Not possible to stop/abort the process:\r\n\r\n![image](https://user-images.githubusercontent.com/3883171/83650926-341bee80-a5b9-11ea-9f9c-fad60631dd93.png)\r\n\r\nThe reason is clear. Nested CDATA sections are not supported by XML. It is the reponsibility of the realtime reporter in the utPLSQL framework to produce a valid XML. However, the SQL Developer extension must still be capable to process data produced by utPLSQL 3.1.4 .. 3.1.10 (or so). Hence I suggest to implement some pre-processing to fix such wrong XML. \r\n\r\nThis link might be helpful: https://stackoverflow.com/questions/12860754/using-cdata-inside-another-cdata .","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2020-06-03T14:45:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/107/utPLSQL-SQLDeveloper/issues/107"}