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 94 of 221; 24 results per page.
A Go module manifest with separate direct and // indirect require blocks for the fictional tree. Served with a .txt extension because go.mod has no registered media type; the content is verbatim go.mod syntax. Every package, version, hash and licence is fictional: the tree describes nothing real.
go.sum content: two h1: lines per fictional module (one for the module zip and one for its go.mod), which is the pairing a verifier must require. Served as .txt because go.sum has no registered media type. Every package, version, hash and licence is fictional: the tree describes nothing real.
GPC: Global Privacy Control SAMPLE for crawler and .well-known tooling.
The same eight trackpoints written to the GPX 1.0 schema. The two versions differ in namespace and in where document metadata lives (1.1 wraps it in a `metadata` element, 1.0 puts name, desc and time directly under `gpx`), which is exactly what a namespace-hardcoding reader gets wrong.
The same eight trackpoints written to the GPX 1.1 schema. The two versions differ in namespace and in where document metadata lives (1.1 wraps it in a `metadata` element, 1.0 puts name, desc and time directly under `gpx`), which is exactly what a namespace-hardcoding reader gets wrong.
A GPX track with timestamped trackpoints and elevation, for testing route parsers and mapping tools.
Eight trackpoints each carrying a Garmin TrackPointExtension with heart rate, cadence and air temperature. The GPX schema deliberately leaves `extensions` open, so this is the fixture for checking that a reader surfaces vendor data instead of discarding it on export.
Seven trackpoints whose timestamps go forwards, backwards, and then repeat: the pattern a receiver produces after a clock correction or a buffered replay. Naive speed calculations divide by a negative or zero time delta and emit impossible values.
A `rte` element: an ordered list of waypoints describing a planned route, with no timestamps because it has not been travelled yet. Many importers only look for `trk` and report this perfectly valid file as empty.
The baseline GPS trace for this category: 24 timestamped, elevated trackpoints in a single segment, walking the Coast Road of the invented territory. Every other GPX fixture here is this file with one thing changed.
Five `wpt` elements for the towns of the territory, with names, symbols and descriptions but no track or route. It is the GPX equivalent of a point layer, and the third of the three top-level GPX content types.
The same eight points timestamped with a +01:00 offset rather than the usual Z. The digits are identical to the reference track, so a parser that strips the offset and assumes UTC produces times that are wrong by exactly one hour: a silent error that only shows up when two traces are merged.
The same 24 points split into two `trkseg` elements with a ten-minute gap between them: what a receiver writes after a stop or a signal loss. Tools that concatenate segments without noticing the boundary report a moving average dragged down by a pause that never happened on the move.
A track containing exactly one point, which is what a receiver writes when a recording is stopped immediately. Distance, speed and bearing all need a pair of points, so this is the fixture that finds off-by-one loops and empty-slice crashes.
Eight trackpoints with timestamps but no `ele` element, the shape a receiver writes on a 2D fix. Elevation-profile code that assumes the element is present either crashes or charts a flat line at zero, which looks like real data.
The same eight points with elevation but no `time` element: what you get when a track is drawn in a planning tool rather than recorded. Speed and pace calculations must refuse to produce a number here instead of dividing by a zero duration.
A gradebook that computes a weighted average from homework, midterm, and final scores, assigns a letter grade with nested IF, and averages the class: good for formula testing.
A smooth three-channel gradient composition, paired with its greyscale conversion to test luminance handling.
True 8-bit greyscale conversion of the gradient composition, the paired reference for testing colour-to-grey conversion.
A Gradle Groovy DSL build script with a plugins block, a Java toolchain, five dependency configurations, task configuration via named() and a registered task. Every coordinate and repository is fictional, so nothing resolves.
Gradle's dependency report, which marks repeat subtrees with `(*)` and explains the marker in a footer, so a parser has to resolve those references back to their first occurrence. Every package, version, hash and licence is fictional: the tree describes nothing real.
A Gradle dependency lockfile: one `group:artifact:version=configurations` line per fictional module plus the `empty=` line that records configurations resolving to nothing. Every package, version, hash and licence is fictional: the tree describes nothing real.
A Gradle settings script (the file that actually defines a multi-project build) with pluginManagement, a repositories mode, a version catalog declaring libraries, a bundle and a plugin, and one project remapped to a custom directory.
A gradle.properties exercising the .properties grammar rather than Gradle: a \uXXXX escape, a backslash line continuation, all three key/value separator forms, and a key containing escaped separator characters.
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.
