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 27 of 221; 24 results per page.
Intentionally invalid semantic test records for Cedar Street Tacos. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.
Linked operating model for Cedar Street Tacos. 375 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.
Numeric expected results for Cedar Street Tacos. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.
Operating chart PNG for Cedar Street Tacos. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.
Operating model JSON Schema for Cedar Street Tacos. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.
Operating report PDF for Cedar Street Tacos. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.
Purchase import CSV for Cedar Street Tacos. 96 data rows, 8 columns and 96 expected accepted rows.
Workflow and import guide for Cedar Street Tacos. Documents 18 source tables, exact expected totals and supported versus manual workflows.
Nine laboratory results where only four are plain numbers: two are below the detection limit, one is above range, two are missing in different spellings, and one is a legitimate small negative near the blank. Coercing the censored strings to numbers or to NaN both bias the summary, and the file distinguishes every case explicitly.
A landscape certificate of completion with a decorative double border, recipient name, course title, date, and signature lines: a print-ready PDF to award or adapt.
A PKCS#10 certificate signing request (PEM) with the subject and SAN, self-signed by the RSA key to prove key possession, for testing CSR parsers and certificate-authority intake flows.
SAMPLE change order DOCX linked to the SOW narrative.
change-password, Well-Known SAMPLE for crawler and .well-known tooling.
The machine-generated twin of the hand-written changelog: version headings that are themselves compare links, a leading warning glyph on the breaking-changes section, and every entry ending in a short-hash link back to the commit. The hashes are the same fictional ids used by the log fixtures in this category.
A hand-maintained changelog in the Keep a Changelog layout: an Unreleased section, dated version headings in square brackets, the standard change-type subheadings, and reference-style compare links at the bottom. It describes the same releases as the generated twin in this group, so a converter between the two can be scored.
Four named chapters (Cold Open, Titles, Main Segment, Credits) on two-second boundaries. The clip burns the chapter name and a running timecode into the picture, so the chapter marks can be verified by eye against what the player's chapter menu claims. Matroska stores chapters as a proper EditionEntry structure with nanosecond timestamps and per-language names, and every desktop player exposes them. This is the reference case.
Four named chapters (Cold Open, Titles, Main Segment, Credits) on two-second boundaries. The clip burns the chapter name and a running timecode into the picture, so the chapter marks can be verified by eye against what the player's chapter menu claims. MP4 has no chapter box. FFmpeg writes them as a QuickTime chapter track (a hidden text track referenced by the video track), which QuickTime, VLC and most desktop players read and which browsers ignore completely. Remux this to MKV and back and the chapters usually survive; convert it with a tool that maps streams individually and they usually do not.
FFmpeg's own metadata format, and the one used to build the two embedded-chapter files in this group. START and END are integers in the declared TIMEBASE, which is the detail that trips people up: change TIMEBASE and every timestamp silently means something else. This is the exact file the MKV and MP4 chapter fixtures here were built from.
The XML dialect `mkvmerge` and `mkvpropedit` read to write chapters into a Matroska file without re-muxing it. Timestamps are nanosecond-precision `HH:MM:SS.nnnnnnnnn`, and each ChapterAtom carries a UID that must be stable across edits: the field most hand-written generators omit, which is why re-running them renumbers every chapter.
The same clip with the chapter marks explicitly removed. The control for this group, and the file that tells you whether a chapter reader returns an empty list or reports the whole-file duration as a single unnamed chapter: both are common, and they are not the same answer.
The plain-text convention used in video descriptions: `M:SS Title`, one per line, first entry at zero. There is no specification, so every parser guesses, at leading zeros, at `HH:MM:SS` versus `M:SS`, at whether a dash or a dot separates the timestamp from the title. Useful for testing a scraper against the format people actually paste.
A WebVTT file intended for `<track kind="chapters">` rather than `kind="subtitles"`. Structurally it is an ordinary WebVTT file, which is the point, nothing inside it says 'chapters', so the same bytes behave as captions if the kind attribute is wrong, and the chapter titles are rendered over the video as subtitles. A common and very visible mistake.
The same synthetic conversations in the Anthropic Messages JSONL shape: a top-level system prompt plus a messages array of user and assistant turns. The format twin of the OpenAI file, for testing chat-format conversion.
A chat fine-tuning dataset in the OpenAI JSONL format: one conversation per line as a messages array with system, user, and assistant turns. Synthetic Q&A content. Paired with an Anthropic-format twin for testing format converters.
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.
