Robot Framework — output.xml
Robot Framework's output.xml, in which every keyword call carries its own status element and a trailing statistics section restates the totals by tag and by suite. Robot 7 reports elapsed seconds rather than the endtime attribute older versions used, so schemaversion is what a reader must branch on. Reports the same canonical run as the JUnit dialect files: 12 tests, 9 passed, 1 assertion failure, 1 error and 1 skip.
<?xml version="1.0" encoding="UTF-8"?>
<robot generator="Robot 7.0.1 (Python 3.12.4 on linux)" generated="2026-08-07T09:14:22.031" rpa="false" schemaversion="5">
<suite id="s1" name="Checkout" source="/builds/novus/tests/checkout.robot">
<test id="s1-t1" name="Applies Unit Price" line="12">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Applies Unit Price" library="CartLibrary"><arg>cart.PricingTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="0.643"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.643"/>
</test>
<test id="s1-t2" name="Applies Quantity Multiplier" line="18">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Applies Quantity Multiplier" library="CartLibrary"><arg>cart.PricingTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="0.659"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.659"/>
</test>
<test id="s1-t3" name="Rounds Half Up At Two Decimals" line="24">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Rounds Half Up At Two Decimals" library="CartLibrary"><arg>cart.PricingTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="1.042"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="1.042"/>
</test>
<test id="s1-t4" name="Rejects Negative Quantity" line="30">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Rejects Negative Quantity" library="CartLibrary"><arg>cart.PricingTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="1.048"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="1.048"/>
</test>
<test id="s1-t5" name="Applies Tax To Subtotal" line="36">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Applies Tax To Subtotal" library="CartLibrary"><arg>cart.PricingTest</arg><status status="FAIL" start="2026-08-07T09:14:22.041" elapsed="0.352"/></kw>
<tag>cart</tag>
<status status="FAIL" start="2026-08-07T09:14:22.031" elapsed="0.352">expected:<12.60> but was:<12.59></status>
</test>
<test id="s1-t6" name="Applies Percentage Discount" line="42">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Applies Percentage Discount" library="CartLibrary"><arg>cart.DiscountTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="0.147"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.147"/>
</test>
<test id="s1-t7" name="Stacks Discounts In Declared Order" line="48">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Stacks Discounts In Declared Order" library="CartLibrary"><arg>cart.DiscountTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="0.327"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.327"/>
</test>
<test id="s1-t8" name="Ignores Expired Coupon" line="54">
<kw name="Given The Cart Is Ready" library="CartLibrary"><status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.010"/></kw>
<kw name="Then Ignores Expired Coupon" library="CartLibrary"><arg>cart.DiscountTest</arg><status status="PASS" start="2026-08-07T09:14:22.041" elapsed="0.893"/></kw>
<tag>cart</tag>
<status status="PASS" start="2026-08-07T09:14:22.031" elapsed="0.893"/>Specifications
- Seed
- 61200
- Encoding
- UTF-8
- Line Endings
- LF
- Format
- Robot Framework output.xml
- Schema Version
- 5
- Tests
- 12
- Pass
- 9
- Fail
- 2
- Skip
- 1
- Has Statistics Section
- true
- Elapsed Unit
- seconds
Testing contract
Expected to pass- Scenario
- Read Robot Framework totals from output.xml and cross-check the statistics section.
- Expected result
- The statistics total stat reads pass=9 fail=2 skip=1 and equals the per-test statuses counted from the suite tree.
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
“Robot Framework — output.xml” 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("robot-output.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- xmlTestNG — testng-results.xmlTestNG's own result document, with suite/test/class/test-method nesting, signature attributes and full stack traces in CDATA. TestNG has no error status, so the errored case is reported as FAIL and the header attributes read failed=2. Reports the same canonical run as the JUnit dialect files: 12 tests, 9 passed, 1 assertion failure, 1 error and 1 skip.
- xmlxUnit.net — v2 Assembly ResultsThe xUnit.net v2 shape: an <assemblies> root holding one assembly, whose tests are grouped into collections rather than classes. Result values are Pass, Fail and Skip with capital initials, which trips converters doing a case-sensitive comparison against the lowercase values every other format uses. Reports the same canonical run as the JUnit dialect files: 12 tests, 9 passed, 1 assertion failure, 1 error and 1 skip.
- xmlCucumber JUnit XML — Checkout RunThe 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.
- 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.
Generated by generation/testing.py. Free for any use, no attribution required — license.