Cucumber JUnit XML — Checkout Run
The same six pickles reported as JUnit XML, which is what a BDD suite hands to a generic CI dashboard. One <testcase> per pickle means the three expanded outline rows appear as three tests with identical names — enough to break any store keyed on name alone.
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
<testsuite name="Checkout totals" tests="6" failures="0" errors="0" skipped="0" time="1.280" timestamp="2026-08-07T09:14:22" hostname="ci-runner-04">
<testcase classname="Checkout totals" name="A single-item cart shows tax separately" time="0.280"/>
<testcase classname="Checkout totals" name="Quantity multiplies the subtotal" time="0.200"/>
<testcase classname="Checkout totals" name="Quantity multiplies the subtotal" time="0.200"/>
<testcase classname="Checkout totals" name="Quantity multiplies the subtotal" time="0.200"/>
<testcase classname="Checkout totals" name="Quantity multiplies the subtotal" time="0.200"/>
<testcase classname="Checkout totals" name="The receipt renders as plain text" time="0.200"/>
</testsuite>
</testsuites>
Specifications
- Seed
- 61200
- Encoding
- UTF-8
- Line Endings
- LF
- Dialect
- cucumber-junit
- Tests
- 6
- Failures
- 0
- Errors
- 0
- Skipped
- 0
- One Testcase Per Pickle
- true
Testing contract
Expected to pass- Scenario
- Feed a BDD run to a CI dashboard that only understands JUnit XML.
- Expected result
- 6 test cases are reported, of which three share the name "Quantity multiplies the subtotal" because they are expansions of one outline.
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
“Cucumber JUnit XML — Checkout Run” is a deterministic Novus Examples fixture for Conversion testing, Log parsing, Error handling. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
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("cucumber-junit-results.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- xmlFlaky Run — Network Dependency, Build #301 (errored)Build #301 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is errored while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.
- xmlFlaky Run — Network Dependency, Build #302 (passing)Build #302 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.
- xmlFlaky Run — Network Dependency, Build #303 (passing)Build #303 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.
- xmlFlaky Run — Network Dependency, Build #304 (passing)Build #304 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.
- xmlFlaky Run — Network Dependency, Build #305 (errored)Build #305 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is errored while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.
- xmlFlaky Run — Order Dependent, Build #201 (passing)Build #201 of five consecutive runs of cart.DiscountTest, in which stacksDiscountsInDeclaredOrder is passing while the other five cases pass every time. The underlying cause is a shared coupon cache left populated by a sibling test under random ordering. Read the whole family in build order to reproduce what a flake detector sees.
Generated by generation/testing.py. Free for any use, no attribution required — license.