xml2.3 KB

JUnit XML — Aggregate <testsuites> Root

Three suites under a <testsuites> root whose own attributes already hold the aggregate totals. A parser that sums the children and also trusts the root double-counts every case, which is the classic cause of a dashboard reporting 24 tests for a 12-test run.

Error handling Conversion testing Code parsing

Preview — first 34 linesxml

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Checkout Aggregate" tests="12" failures="1" errors="1" skipped="1" time="7.450">
  <testsuite name="cart.PricingTest" tests="5" failures="1" errors="0" skipped="0" time="3.744">
    <testcase classname="cart.PricingTest" name="appliesUnitPrice" time="0.643"/>
    <testcase classname="cart.PricingTest" name="appliesQuantityMultiplier" time="0.659"/>
    <testcase classname="cart.PricingTest" name="roundsHalfUpAtTwoDecimals" time="1.042"/>
    <testcase classname="cart.PricingTest" name="rejectsNegativeQuantity" time="1.048"/>
    <testcase classname="cart.PricingTest" name="appliesTaxToSubtotal" time="0.352">
      <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>
  </testsuite>
  <testsuite name="cart.DiscountTest" tests="4" failures="0" errors="0" skipped="1" time="2.067">
    <testcase classname="cart.DiscountTest" name="appliesPercentageDiscount" time="0.147"/>
    <testcase classname="cart.DiscountTest" name="stacksDiscountsInDeclaredOrder" time="0.327"/>
    <testcase classname="cart.DiscountTest" name="ignoresExpiredCoupon" time="0.893"/>
    <testcase classname="cart.DiscountTest" name="appliesLoyaltyTier" time="0.700">
      <skipped message="loyalty tiers are disabled in the CI profile"/>
    </testcase>
  </testsuite>
  <testsuite name="checkout.SessionTest" tests="3" failures="0" errors="1" skipped="0" time="1.639">
    <testcase classname="checkout.SessionTest" name="createsSessionForNewCart" time="0.783"/>
    <testcase classname="checkout.SessionTest" name="expiresSessionAfterTimeout" time="0.695">
      <error message="Connection refused: sessions.example.com:5432" type="java.net.ConnectException"><![CDATA[java.net.ConnectException: Connection refused: sessions.example.com:5432
	at checkout.SessionStore.open(SessionStore.java:41)
	at checkout.SessionTest.expiresSessionAfterTimeout(SessionTest.java:57)
]]></error>
    </testcase>
    <testcase classname="checkout.SessionTest" name="restoresCartOnResume" time="0.161"/>
  </testsuite>
</testsuites>

Specifications

Seed: 61200
Encoding: UTF-8
Line Endings: LF
Root Element: testsuites
Suites: 3
Tests: 12
Aggregate Attributes: true

Testing contract

Expected to pass

Scenario: Aggregate a multi-suite JUnit file whose root element repeats the totals.
Expected result: The run reports 12 tests once — the root aggregate and the sum of the three child suites agree and must not be added together.

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 — Aggregate <testsuites> Root” 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-testsuites-wrapper.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])