JUnit XML — Phpunit Dialect (phpunit)
The same 12-case Novus Checkout run written the way PHPUnit 11.2 --log-junit writes it. PHPUnit nests per-class suites inside a named parent suite and adds an assertions count that no other dialect reports. 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.
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
<testsuite name="Checkout Test Suite" tests="12" assertions="34" errors="1" failures="1" skipped="1" time="7.450">
<testsuite name="Cart\PricingTest" file="tests/Cart/PricingTest.php" tests="5" assertions="13" errors="0" failures="1" skipped="0" time="3.744">
<testcase classname="Cart\PricingTest" name="appliesUnitPrice" time="0.643" file="tests/Cart/PricingTest.php" line="24" assertions="3"/>
<testcase classname="Cart\PricingTest" name="appliesQuantityMultiplier" time="0.659" file="tests/Cart/PricingTest.php" line="30" assertions="3"/>
<testcase classname="Cart\PricingTest" name="roundsHalfUpAtTwoDecimals" time="1.042" file="tests/Cart/PricingTest.php" line="36" assertions="3"/>
<testcase classname="Cart\PricingTest" name="rejectsNegativeQuantity" time="1.048" file="tests/Cart/PricingTest.php" line="42" assertions="3"/>
<testcase classname="Cart\PricingTest" name="appliesTaxToSubtotal" time="0.352" file="tests/Cart/PricingTest.php" line="48" assertions="3">
<failure message="expected:<12.60> but was:<12.59>" 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" file="tests/Cart/DiscountTest.php" tests="4" assertions="10" errors="0" failures="0" skipped="1" time="2.067">
<testcase classname="Cart\DiscountTest" name="appliesPercentageDiscount" time="0.147" file="tests/Cart/DiscountTest.php" line="54" assertions="3"/>
<testcase classname="Cart\DiscountTest" name="stacksDiscountsInDeclaredOrder" time="0.327" file="tests/Cart/DiscountTest.php" line="60" assertions="3"/>
<testcase classname="Cart\DiscountTest" name="ignoresExpiredCoupon" time="0.893" file="tests/Cart/DiscountTest.php" line="66" assertions="3"/>
<testcase classname="Cart\DiscountTest" name="appliesLoyaltyTier" time="0.700" file="tests/Cart/DiscountTest.php" line="72" assertions="3">
<skipped message="loyalty tiers are disabled in the CI profile"/>
</testcase>
</testsuite>
<testsuite name="Checkout\SessionTest" file="tests/Checkout/SessionTest.php" tests="3" assertions="7" errors="1" failures="0" skipped="0" time="1.639">
<testcase classname="Checkout\SessionTest" name="createsSessionForNewCart" time="0.783" file="tests/Checkout/SessionTest.php" line="78" assertions="3"/>
<testcase classname="Checkout\SessionTest" name="expiresSessionAfterTimeout" time="0.695" file="tests/Checkout/SessionTest.php" line="84" assertions="3">
<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" file="tests/Checkout/SessionTest.php" line="90" assertions="3"/>
</testsuite>
</testsuite>
</testsuites>
Specifications
- Seed
- 61200
- Dialect
- phpunit
- Producer
- PHPUnit 11.2 --log-junit
- Tests
- 12
- Failures
- 1
- Errors
- 1
- Skipped
- 1
- Passed
- 9
- Suite Time Seconds
- 7.45
- Root Element
- testsuites
- Encoding
- UTF-8
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Parse a JUnit XML report produced in the phpunit dialect and extract the run totals.
- Expected result
- 12 tests, 9 passed, 1 failure, 1 error and 1 skipped — identical to the other seven dialect files in this group.
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 — Phpunit Dialect (phpunit)” is a deterministic Novus Examples fixture for Conversion testing, Error handling, Log parsing. 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("phpunit-junit-results.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- 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 — Console Output in CDATACaptured 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.
- 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 — Mixed Pass, Fail, Error and SkipThe full canonical run flattened into a single suite: nine passes, one failure, one error and one skip. This is the same twelve cases the eight dialect files carry, so totals can be compared straight across.
Generated by generation/testing.py. Free for any use, no attribution required — license.