Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

146 results

Page 4 of 7; 24 results per page.

Show the canonical directory

PWA: app-shell.css SAMPLE

PWA shell fixture SAMPLE (app-shell.css) for offline app-shell testing.

File: CSS · Pwa
Use case: Web assets· Conversion set

PWA: index-shell.html SAMPLE

PWA shell fixture SAMPLE (index-shell.html) for offline app-shell testing.

File: HTML · Pwa
Use case: Web assets· Conversion set

PWA: offline.html SAMPLE

PWA shell fixture SAMPLE (offline.html) for offline app-shell testing.

File: HTML · Pwa
Use case: Web assets· Conversion set

PWA: sw-register.js SAMPLE

PWA shell fixture SAMPLE (sw-register.js) for offline app-shell testing.

File: JS · Pwa
Use case: Web assets· Conversion set

robots.txt

A robots.txt with wildcard and per-agent rules, a crawl-delay, and a sitemap reference, for testing robots parsers and crawler policy handling.

File: TXT · Crawlers · UTF-8
Use case: Web assetsEditor testing

robots.txt - block everything except one path

A robots.txt that disallows the entire site for every crawler while allowing one media path for a single image agent. For testing full-block handling and the common misconception that a Disallow removes a URL from a search index.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - Crawl-delay, Request-rate and Visit-time

A robots.txt carrying three different crawl-rate hints - an integer Crawl-delay, a fractional one alongside Request-rate and Visit-time, and a very large one - none of which are part of RFC 9309. For testing that a crawler reads or ignores rate hints without dropping the Disallow rules that share the group.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - field case, tabs and indentation

A robots.txt using upper-case, mixed-case and indented field names, a tab-indented rule, a value with no space after the colon, and both trailing and full-line comments. For testing that field names are treated case-insensitively while path values stay case-sensitive.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - five Sitemap directives

A robots.txt declaring five sitemaps - before the first group, inside two different groups, in lower case, gzipped, and on another host. For testing that a discovery crawler collects Sitemap as a file-global field instead of scoping it to the group it sits in.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - merged groups and Allow/Disallow precedence

A robots.txt where Googlebot is named by two separate groups and every Disallow has an equal-length Allow competing with it. For testing group merging, case-insensitive product tokens, and the rule that the most specific match wins with Allow breaking ties.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - unknown and vendor-specific fields

A robots.txt in which real Disallow rules are surrounded by Noindex, Host, Clean-param, Nofollow and two invented fields, several with inline comments. For testing that a parser skips fields it does not implement instead of aborting or mis-binding the rules that follow.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - UTF-8 BOM with CRLF line endings

A robots.txt that begins with a UTF-8 byte-order mark, uses CRLF line endings, and leaves trailing spaces after two rule values. For testing the byte-level tolerances RFC 9309 requires - a leading BOM must be discarded rather than glued onto the first field name.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt - wildcard and $ anchor matching

A robots.txt built entirely from pattern rules: `*` inside a path, `$` anchoring the end of a URL, a query-string pattern, and an Allow that carves one file out of a disallowed subtree. For testing that a robots parser implements RFC 9309 path matching rather than prefix comparison.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt that is actually an HTML 404 page

The single most common broken robots.txt in the wild: a server that answers /robots.txt with its HTML 404 page instead of a 404 status. For testing that a crawler treats unparseable markup as 'no robots.txt' and allows the site rather than inventing rules from tag names.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt with deliberately invalid syntax

A deliberately invalid robots.txt: a rule before any group, an empty product token, an absolute URL where a path belongs, whitespace before the colon, a non-numeric Crawl-delay, and a line with no colon at all. For testing that a parser degrades line-by-line instead of failing the whole file.

File: TXT · Crawlers
Use case: Web assetsWeb scraping+1· Conversion set

robots.txt: Wave G SAMPLE

robots.txt: Wave G SAMPLE for crawler and .well-known tooling.

File: TXT · Well Known
Use case: Web assets

Sample App .env

Sample App .env: small deterministic fixture for parsers and the in-browser editor.

File: ENV · Config
Use case: Editor testingConfig parsing

Sample Dockerfile

Sample Dockerfile: small deterministic fixture for parsers and the in-browser editor.

File: DOCKERFILE · Config
Use case: Editor testingConfig parsing

Sample OPML Subscriptions

Sample OPML Subscriptions: small deterministic fixture for parsers and the in-browser editor.

File: OPML · Feeds
Use case: Editor testing

Security Contact JSON: 01

Well-known security contact JSON SAMPLE #1.

File: JSON · Well Known
Use case: Web assets

Security Contact JSON: 02

Well-known security contact JSON SAMPLE #2.

File: JSON · Well Known
Use case: Web assets

Security Contact JSON: 03

Well-known security contact JSON SAMPLE #3.

File: JSON · Well Known
Use case: Web assets

Security Contact JSON: 04

Well-known security contact JSON SAMPLE #4.

File: JSON · Well Known
Use case: Web assets

Security Contact JSON: 05

Well-known security contact JSON SAMPLE #5.

File: JSON · Well Known
Use case: Web assets