Sample OPML Subscriptions
Sample OPML Subscriptions — small deterministic fixture for parsers and the in-browser editor.
<?xml version="1.0"?><opml version="2.0"><head><title>SAMPLE</title></head><body><outline text="Example" xmlUrl="https://example.com/feed.xml"/></body></opml>
Specifications
- Role
- sample fixture
Testing contract
Expected to pass- Scenario
- Exercise Sample OPML Subscriptions in its feeds workflow. Sample OPML Subscriptions — small deterministic fixture for parsers and the in-browser editor.
- Expected result
- 1 text lines, decoded as UTF-8; first nonempty line is '<?xml version="1.0"?><opml version="2.0"><head><title>SAMPLE</title></head><body><outline text="Example" xmlUrl="https://example.com/feed.x…'. Declared feature checks: role=sample fixture.
What is a .opml file?
OPML (Outline Processor Markup Language, .opml) is an XML format for nested outlines. Its most common use is exchanging feed subscription lists between RSS readers, where each outline element carries a feed title and xmlUrl, but it also serves for mind maps and document outlines.
How to use this file
Use an example .opml file to test feed-reader import and export, OPML parsers, and outline tooling, or to move a subscription list between podcast and RSS apps.
How to use this file for testing
“Sample OPML Subscriptions” is a deterministic Novus Examples fixture for Editor testing. Text-based files you can open, edit, and download directly in the browser editor.
Documented properties for this file: sample fixture. 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.
Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.
Code examples
import xml.etree.ElementTree as ET
root = ET.parse("sample.opml").getroot()
for o in root.iter("outline"):
print(o.get("text"), o.get("xmlUrl"))Related files
- txtads.txtAn IAB ads.txt listing authorised digital sellers with account IDs and relationships (sample data) — for testing ads.txt parsers and ad-fraud tooling.
- txtdnt-policy.txt (Do Not Track compliance statement)A sample machine-discoverable Do Not Track policy of the kind served at /.well-known/dnt-policy.txt, stating retention windows, exceptions and a contact for a fictional site. For testing crawlers and privacy scanners that look for the document and read its version header.
- xmlhost-meta (XRD, XML form)Host metadata in its original XRD form: a subject, an alias, an expiry, one property, and three Link elements including an lrdd template with a {uri} placeholder. Paired with the JRD twin that carries exactly the same data.
- txthumans.txtA humans.txt crediting the people and stack behind a site, in the conventional TEAM/SITE block format — for testing plain-text metadata parsers.
- txtmta-sts.txt (RFC 8461 SMTP MTA-STS policy)An SMTP MTA-STS policy in enforce mode listing three MX patterns, one of them a wildcard, with a seven-day max_age. RFC 8461 specifies CRLF line endings, so this fixture is written with them deliberately - for testing policy parsers that split on bare LF.
- txtPlain-text sitemap (one URL per line)The plain-text sitemap format the sitemaps.org protocol also accepts: one absolute URL per line, no markup, UTF-8 encoded. For testing that a crawler supports the text form as well as XML.
Generated by generation/breadth_extra_wave_c.py. Free for any use, no attribution required, license.