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 133 of 221; 24 results per page.
Three CF time coordinates over the same six records: hours from the Unix epoch, days from 2026-01-01, and the same days under a 365_day calendar. A decoder that assumes one epoch, or ignores the calendar attribute, dates the records wrongly without raising anything.
A NetCDF-3 file with a genuine unlimited record dimension, so the record variable is stored interleaved rather than contiguously while the fixed-size station variable is not. It exercises the striding path that a reader written only against fixed dimensions gets wrong.
A six-taxon Newick tree with branch lengths on every edge and bootstrap-style support values written as internal node labels. That support notation is ambiguous by design in Newick (the same position can hold a node name), which is precisely what a parser has to decide about.
The identical tree topology with every branch length and support value stripped, which is what a Newick writer produces when the source tree has no lengths. Comparing the two proves a parser distinguishes 'length zero' from 'no length recorded'.
A preference centre with six topic checkboxes, a frequency radio group and a master unsubscribe control that must override every other choice. The override interaction is the behaviour worth testing here.
A downloadable newsletter-subscription form: email, interests, frequency, and a consent checkbox.
A company newsletter as an editable Word document with a masthead and three short articles, twinned with an HTML email version of the same content.
The newsletter as a responsive, table-based HTML email with inline styles: a masthead, three articles, and a call-to-action button. Opens in the in-browser editor; twin of the DOCX version.
An nginx combined-format access log with several requests, including a 403 and a 404, for testing log parsers.
Minimal nginx reverse-proxy config SAMPLE for syntax highlighter and linter tests.
Minimal Nim hello for nimlsp / highlighter tests.
Nim object type plus proc, for Nim AST tooling.
Nim recursive fib proc: realistic snippet.
Nim Template SAMPLE for Wave G language-tooling coverage.
Intentionally invalid Nim for nim check error paths.
A log with one sentence whose checksum has been altered and a final sentence truncated mid-transmission with no checksum at all: the two ways a serial GPS feed actually degrades. A correct parser drops both and keeps everything else.
The same twelve fixes reduced to GGA alone. GGA carries time-of-day but no date and no speed, so a parser that only reads GGA cannot place the track on a calendar: a real limitation that this file makes obvious rather than leaving to be discovered later.
The same sentences terminated with a bare LF rather than the CR LF the standard mandates: what you get after a log passes through a text editor or a Unix pipeline. Parsers that strip only "\r\n" leave a stray character on every line and then fail the checksum.
A twelve-fix receiver log with the five sentence types a GPS unit normally interleaves, including three-part GSV satellite-in-view sets. Every checksum is correct, so a parser that verifies them should accept the whole file.
Six cycles of a receiver that has power but no satellite lock: GGA fix quality 0, RMC status V, and empty coordinate fields throughout. Parsers that split on commas and index positionally read these empty fields as zeros and plot the track at Null Island.
NMEA never writes a negative coordinate: sign lives entirely in the N/S and E/W letters, and the numeric field is always positive. This log sits in the southern and eastern hemispheres, so a parser that ignores the hemisphere letter puts every fix in the wrong quadrant of the world.
A realistic Node.js/Express stack trace, a TypeError with V8-style 'at function (file:line:col)' frames including an async frame and internal node: frames. A fixture for testing JS stack-trace parsers.
Era and era-year for one instant across five calendar systems. The three whose months and days align with the Gregorian calendar, Japanese (Reiwa 8), ROC (Minguo 115) and Thai Buddhist (2569), carry a full rendered date; the Hijri and Hebrew entries carry the year only, because their day and month depend on the calculation variant and, for Hijri, on observation. Saying so is the point of the fixture.
The default output of bare `diff`: ed-style commands such as `3a4` with `<` and `>` bodies and no file headers at all. Tooling that identifies diffs by looking for `---`, `+++` or `@@` cannot even tell this is a diff, which is exactly what makes it a useful negative fixture.
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.
