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
For example, this can be produced by the @testing-library/react when it decides the summary of the DOM is too long and truncates it (as it may happen to truncate the text in the middle of an ANSI escape code, meaning strip-ansi won't remove it).
The output is:
<?xml version="1.0" encoding="UTF-8"?>
<testsuitesname="jest tests"tests="1"failures="1"errors="0"time="2">
<testsuitename="undefined"errors="0"failures="1"skipped="0"timestamp="2022-01-25T12:11:51"time="1.561"tests="1">
<testcaseclassname=" breaks jest-junit"name=" breaks jest-junit"time="0.001">
<failure>Error: �
at Object.<anonymous> (/home/lee/project/src/junit.spec.ts:2:11)
at Object.asyncJestTest (/home/lee/project/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:106:37)
at /home/lee/project/node_modules/jest-jasmine2/build/queueRunner.js:45:12
at new Promise (<anonymous>)
at mapper (/home/lee/project/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
at /home/lee/project/node_modules/jest-jasmine2/build/queueRunner.js:75:41
at processTicksAndRejections (node:internal/process/task_queues:96:5)</failure>
</testcase>
</testsuite>
</testsuites>
This is invalid XML and makes it harder to see why the test failed since Azure DevOps rejects the junit.xml file.
The text was updated successfully, but these errors were encountered:
To reproduce the issue:
For example, this can be produced by the
@testing-library/react
when it decides the summary of the DOM is too long and truncates it (as it may happen to truncate the text in the middle of an ANSI escape code, meaningstrip-ansi
won't remove it).The output is:
This is invalid XML and makes it harder to see why the test failed since Azure DevOps rejects the junit.xml file.
The text was updated successfully, but these errors were encountered: