Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 197 of 221; 24 results per page.
Clean 1024×1024 reference for super-resolution base A. Upscale the smaller inputs in this group toward this ground truth.
Clean 1024×1024 reference for super-resolution base B. Upscale the smaller inputs in this group toward this ground truth.
A complete urlencoded request dump with repeated keys, bracket notation, an encoded newline and a non-ASCII key, annotated with what each one tests. The host is example.invalid and nothing was ever sent.
The signpost as USDZ with `upAxis = "Y"` and `metersPerUnit = 1` in the stage metadata. USD is the only format in this group that declares BOTH the axis and the scale, which is exactly why it is the one AR pipelines standardised on.
The signpost as USDZ with `upAxis = "Z"` and `metersPerUnit = 1` in the stage metadata. USD is the only format in this group that declares BOTH the axis and the scale, which is exactly why it is the one AR pipelines standardised on.
A 10 mm cube as USDZ: Pixar's Universal Scene Description packaged as a stored zip, the format Apple uses for AR Quick Look. For testing USD/USDZ readers and conversion.
User JSON deliberately violating the schema five ways: negative case for validator error reporting.
JSON instance conforming to the Wave F user JSON Schema: positive validator test case.
Draft 2020-12 JSON Schema for a user object with email format and role enum, paired with valid/invalid instances.
A UTF-16 big-endian text file with a BOM (FE FF) and CRLF line endings, for testing wide-character decoding and byte-order detection.
A UTF-16 little-endian text file with a BOM (FF FE) and CRLF line endings, for testing wide-character decoding and encoding detection.
A UTF-32 little-endian text file with a BOM (FF FE 00 00): four bytes per code point, for testing full-width Unicode decoders and byte-order handling.
A UTF-8 text file with Unix (LF) line endings and no byte-order mark, containing accented and symbol characters, for testing charset detection.
A UTF-8 text file that starts with a byte-order mark (EF BB BF) and uses Windows (CRLF) line endings, for testing BOM handling and line-ending detection.
A uv lockfile in TOML, recording an sdist and a wheel per fictional package with inline tables carrying url, hash and byte size: a newer layout than poetry.lock and a useful contrast for parser tests. Every package, version, hash and licence is fictional: the tree describes nothing real.
A VAST 3.0 response pairing a linear spot with two companion banners in the standard IAB sizes, at the older schema version many ad servers still emit. Companions render alongside the video rather than in it, so they exercise a separate slot-matching path: the player has to find a matching container or correctly ignore them when required is none. All URLs point at example.invalid.
A valid VAST document containing no Ad element: the correct response when an ad server has nothing to serve. It arrives as HTTP 200 with a well-formed body, so it is not an error condition, and a player must resume content immediately rather than waiting for a timeout. Frequently mishandled: players stall on the break or log a spurious failure. The smallest meaningful VAST document there is.
A complete VAST 4.2 inline response for a linear pre-roll: two progressive MP4 media files at different bitrates, quartile tracking, an impression beacon and a click-through. Every URL points at the reserved example.invalid domain, so nothing can ever be fetched and no real ad server is contacted. For testing VAST parsing and player integration without a live ad stack.
A VAST wrapper: a response that carries no media of its own, only a VASTAdTagURI pointing at another VAST document plus its own tracking beacons that must be fired in addition to the resolved ad's. Wrapper chains are where real ad integrations break: unbounded redirect depth, timeouts, and tracking dropped part-way down the chain. Pairs with the inline response it nominally redirects to.
A vCard 3.0 contact with name, email, phone, and address, for testing contact importers.
A log-processing topology in TOML where components declare their inputs rather than an explicit graph, including a dropped-event route consumed as parse_json.dropped. The transform bodies are triple-quoted multi-line strings holding a different language, which is what breaks TOML tooling here.
A weighted comparison of fictional vendors with evidence notes, decisions, and review ownership. This UTF-8 CSV twin contains the model's single canonical table for parser, import, and round-trip tests.
A weighted comparison of fictional vendors with evidence notes, decisions, and review ownership. This print-ready PDF twin is designed for page-rendering, extraction, and cross-format comparison tests.
A weighted comparison of fictional vendors with evidence notes, decisions, and review ownership. This Excel workbook adds filters, frozen headers, print settings, typed cells, and live formulas where the model defines them.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
