JUnit XML — Console Output in CDATA
Captured stdout and stderr wrapped in CDATA, where the stdout text itself looks like XML markup. A parser must treat the CDATA content as opaque characters; one that re-parses it finds a <report> element that does not exist.
<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="cart.PricingTest" tests="2" failures="0" errors="0" skipped="0" time="0.198">
<testcase classname="cart.PricingTest" name="appliesUnitPrice" time="0.121"/>
<testcase classname="cart.PricingTest" name="roundsHalfUpAtTwoDecimals" time="0.077"/>
<system-out><![CDATA[<report status="partial">not real markup, just log text</report>
[INFO] wrote target/surefire-reports/cart.PricingTest.txt
]]></system-out>
<system-err><![CDATA[WARNING: discount table cache was cold
]]></system-err>
</testsuite>
Specifications
- Seed
- 61200
- Encoding
- UTF-8
- Line Endings
- LF
- Tests
- 2
- Has System Out
- true
- Has System Err
- true
- Cdata Contains Markup
- true
Testing contract
Expected to pass- Scenario
- Read captured console output that contains angle brackets inside CDATA.
- Expected result
- system-out is returned as literal text including the <report …> line, and no child element is created from it.
What is a .xml file?
XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.
How to use this file
Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.
How to use this file for testing
“JUnit XML — Console Output in CDATA” is a deterministic Novus Examples fixture for Log parsing, Error handling, Conversion testing. Access logs and JSON-lines application logs — for testing log parsers, tailers, and ingestion pipelines.
Documented properties for this file: seed 61200 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Test and coverage reports document their totals (suites, cases, passes, failures, skips, covered lines) in the spec table. Point your CI dashboard, coverage gate, or report converter at the file and assert those counts survive; format twins carry identical numbers so a conversion can be scored exactly.
Code examples
import xml.etree.ElementTree as ET
tree = ET.parse("structure-system-out-cdata.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- xmlJUnit XML — @Playwright/Test Dialect (playwright)The same 12-case Novus Checkout run written the way @playwright/test 1.47 junit reporter writes it. Playwright puts the run totals on the <testsuites> root, names each suite after its spec file, and uses the bare describe title as classname. All eight dialect files in this group report 12 tests, 1 failure, 1 error and 1 skip, so a JUnit parser can be held to identical totals across every producer.
- xmlJUnit XML — All Tests PassingA clean green run: six passing cases, zero failures, errors and skips. The baseline a CI gate should treat as success, and the control case for any dashboard that colours a build from the failure count.
- xmlJUnit XML — Empty Suite (Zero Tests)A structurally valid report containing a suite with no <testcase> children at all — what a runner writes when a filter matched nothing. Aggregators that divide by the test count to compute a pass rate hit a zero denominator here.
- xmlJUnit XML — Error and Failure DistinguishedOne <failure> (an assertion that did not hold) and one <error> (an exception the test never expected), side by side. Parsers that collapse the two lose the distinction between a broken assertion and a broken environment.
- xmlJUnit XML — Every Test SkippedA suite in which every case was skipped, so tests equals skipped and nothing actually ran. A gate that reads only the failure count calls this green; one that checks executed>0 catches it.
- xmlJUnit XML — Go-Junit-Report Dialect (go-junit-report)The same 12-case Novus Checkout run written the way go-junit-report 2.1 writes it. go-junit-report names each suite after a Go package and carries the toolchain version in a go.version property. All eight dialect files in this group report 12 tests, 1 failure, 1 error and 1 skip, so a JUnit parser can be held to identical totals across every producer.
Generated by generation/testing.py. Free for any use, no attribution required — license.