Flaky Run — Order Dependent, Build #204 (passing)
Build #204 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.
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
<testsuite name="cart.DiscountTest" tests="6" failures="0" errors="0" skipped="0" time="3.559" timestamp="2026-08-07T09:14:22" hostname="ci-runner-04" id="204">
<testcase classname="cart.DiscountTest" name="appliesPercentageDiscount" time="0.863"/>
<testcase classname="cart.DiscountTest" name="stacksDiscountsInDeclaredOrder" time="0.048"/>
<testcase classname="cart.DiscountTest" name="ignoresExpiredCoupon" time="0.735"/>
<testcase classname="cart.DiscountTest" name="appliesLoyaltyTier" time="0.434"/>
<testcase classname="cart.DiscountTest" name="rejectsUnknownCoupon" time="1.053"/>
<testcase classname="cart.DiscountTest" name="appliesFreeShippingThreshold" time="0.426"/>
</testsuite>
</testsuites>
Specifications
- Seed
- 61200
- Build Number
- 204
- Build Index
- 4
- Builds In Family
- 5
- Suite
- cart.DiscountTest
- Tests
- 6
- Flaky Test
- cart.DiscountTest.stacksDiscountsInDeclaredOrder
- Flaky Test Outcome
- pass
- Other Tests Outcome
- pass
- Root Cause
- a shared coupon cache left populated by a sibling test under random ordering
- Dialect
- surefire
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Ingest build #204 as one sample in a five-build flake-detection window.
- Expected result
- stacksDiscountsInDeclaredOrder is recorded as passing in this build while the other five cases pass, so no single build on its own identifies the flake.
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
“Flaky Run — Order Dependent, Build #204 (passing)” is a deterministic Novus Examples fixture for Error handling, Log parsing, Conversion testing. Deliberately corrupt and invalid files, clearly labelled, for testing how your tool fails.
Documented properties for this file: seed 61200 · 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("order-dependent-build-204.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 — Quarantined After Two Failures, Build #401 (failing)Build #401 of five consecutive runs of cart.PricingTest, in which appliesTaxToSubtotal is failing while the other five cases pass every time. The underlying cause is a rounding boundary that only trips when the tax rate table is reloaded. 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.