xml814 B

JUnit XML — Same Test Reported Twice

The same classname and name appear twice with different outcomes — what a parameterised runner or a merged report can produce. Any store keyed on classname+name overwrites the first result and reports the suite as green or red depending purely on document order.

Error handling Conversion testing Code parsing

Preview — first 14 linesxml

<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
  <testsuite name="cart.PricingTest" tests="3" failures="1" errors="0" skipped="0" time="0.342" timestamp="2026-08-07T09:14:22" hostname="ci-runner-04">
    <testcase classname="cart.PricingTest" name="appliesUnitPrice" time="0.121"/>
    <testcase classname="cart.PricingTest" name="appliesUnitPrice" time="0.144">
      <failure message="expected:&lt;12.60&gt; but was:&lt;12.59&gt;" type="java.lang.AssertionError"><![CDATA[java.lang.AssertionError: expected:<12.60> but was:<12.59>
	at cart.PricingTest.appliesTaxToSubtotal(PricingTest.java:88)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
]]></failure>
    </testcase>
    <testcase classname="cart.PricingTest" name="roundsHalfUpAtTwoDecimals" time="0.077"/>
  </testsuite>
</testsuites>

Specifications

Seed: 61200
Encoding: UTF-8
Line Endings: LF
Tests: 3
Failures: 1
Distinct Test Identities: 2
Duplicated Identity: cart.PricingTest.appliesUnitPrice

Testing contract

Expected to recover

Scenario: Store results from a report in which one test identity appears twice.
Expected result: Three <testcase> elements are read but only two distinct identities exist; the duplicate must be reported rather than silently overwritten.

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 — Same Test Reported Twice” is a deterministic Novus Examples fixture for Error handling, Conversion testing, Code parsing. Deliberately corrupt and invalid files, clearly labelled, for testing how your tool fails.

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-duplicate-testcase.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])