dart
141 BDart Counter
Tiny Dart class with a counter: fixture for Dart analysis servers.
- File
- DART · Dart
- Use case
- Syntax highlightingCode parsing+1
Explore the test library
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.
5297 results
Page 52 of 221; 24 results per page.
dart
102 BDart Future
Dart async Future SAMPLE for analysis-server tests.
- File
- DART · Dart
- Use case
- Syntax highlightingCode parsing+1
dart
42 BDart Hello
Minimal Dart hello-world for Flutter/Dart IDE and highlight tests.
- File
- DART · Dart
- Use case
- Syntax highlightingCode parsing+1
m4s
818 BDASH VOD: Init Segment (init-stream0.m4s)
A DASH initialisation segment carrying codec configuration for one representation. Named by the manifest's $RepresentationID$ template, so this file also exercises whether a client resolves template variables correctly rather than pattern-matching filenames.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
818 BDASH VOD: Init Segment (init-stream1.m4s)
A DASH initialisation segment carrying codec configuration for one representation. Named by the manifest's $RepresentationID$ template, so this file also exercises whether a client resolves template variables correctly rather than pattern-matching filenames.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
818 BDASH VOD: Init Segment (init-stream2.m4s)
A DASH initialisation segment carrying codec configuration for one representation. Named by the manifest's $RepresentationID$ template, so this file also exercises whether a client resolves template variables correctly rather than pattern-matching filenames.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
mpd
2.2 KBDASH VOD: Manifest (Playable Package)
A complete, playable MPEG-DASH manifest for the same 320x180 at 300 kbps, 480x270 at 700 kbps, 640x360 at 1400 kbps ladder as the HLS package, produced from the same encoder run, so the two can be compared directly as packaging rather than as content. Every segment it references exists in this group. Served inline as application/dash+xml with permissive CORS, so dash.js can load it cross-origin.
- File
- MPD · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
16 KBDASH VOD: Media Segment (chunk-stream0-00001.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
19.2 KBDASH VOD: Media Segment (chunk-stream0-00002.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
39.9 KBDASH VOD: Media Segment (chunk-stream1-00001.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
61 KBDASH VOD: Media Segment (chunk-stream1-00002.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
32.2 KBDASH VOD: Media Segment (chunk-stream2-00001.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
m4s
61.7 KBDASH VOD: Media Segment (chunk-stream2-00002.m4s)
A one-second DASH media segment, addressed by the manifest's $Number$ template. The same underlying CMAF structure as the HLS segments in the sibling package, which is the whole point of CMAF, and something a fixture set should let you verify rather than take on trust.
- File
- M4S · Vod Dash
- Use case
- Streaming manifestsVideo codecs+1· Conversion set
mpd
514 BDASH, Intentionally Corrupt: Malformed ISO 8601 Duration
An intentionally corrupt DASH manifest whose mediaPresentationDuration is the bare number 14.0 instead of the ISO 8601 form PT14.0S. The XML is well-formed, so it parses cleanly and only fails at schema validation, which most players skip. The usual result is a duration of zero or NaN and a seek bar that never populates, with no error anywhere.
- File
- MPD · Stream Corrupt
- Use case
- Streaming manifestsVideo QA· Conversion set
mpd
805 BDASH: Dynamic (Live) Manifest With a Time-Shift Buffer
A live DASH manifest: type is dynamic, there is no total duration, and the client must compute which segment is currently available from availabilityStartTime, the wall clock, and the segment duration. Declares a one-minute time-shift buffer and an eight-second presentation delay. The timestamps are fixed so the fixture stays deterministic: a real client will compute a segment number far in the future, which is itself a useful edge case to handle gracefully.
- File
- MPD · Stream · unbounded: no mediaPresentationDuration
- Use case
- Streaming manifestsConversion testing+1· Conversion set
mpd
750 BDASH: Explicit SegmentList Addressing
The same content addressed with an explicit SegmentList: every segment URL enumerated rather than derived from a template. Verbose, but it is what older packagers emit and it permits non-uniform segment naming. A DASH client must support both this and SegmentTemplate; the paired template manifest in this group is the direct contrast.
- File
- MPD · Stream
- Use case
- Streaming manifestsConversion testing+1· Conversion set
mpd
1.5 KBDASH: Multi-Period Manifest With a Mid-Roll Break
Three DASH periods (content, an ad break, then content again), each with its own initialisation segment. Period boundaries are where players most often break: the decoder must be reset, the buffer cannot span the discontinuity, and rendition selection restarts. Pairs with the VMAP and SCTE-35 fixtures, which describe the same break from the ad-signalling side.
- File
- MPD · Stream
- Use case
- Streaming manifestsConversion testing+1· Conversion set
mpd
1.5 KBDASH: Static MPD With a Segment Template
A DASH manifest with separate video and audio adaptation sets, three video representations, and $RepresentationID$/$Number$ segment-template addressing: the standard VOD packaging shape. Served inline as application/dash+xml with permissive CORS, so dash.js can load it cross-origin. A manifest-parsing fixture: it describes segment URLs rather than shipping the segments.
- File
- MPD · Stream · PT14.0S
- Use case
- Streaming manifestsConversion testing+1· Conversion set
json
3 KBDashboard JSON: Chained Template Variables (json)
A dashboard driven by four template variables, one of which queries using the value of another: the chained dependency that must be resolved in order. Multi-select variables interpolate as regex alternations, which is why every query here uses =~ rather than =.
- File
- JSON · Alerts
- Use case
- ObservabilityJSON parsing+1· Conversion set
json
4.1 KBDashboard JSON: Five-Panel Service Overview (json)
A dashboard document in the Grafana JSON model: five panels on the 24-column grid, each with a datasource reference by UID, a PromQL target and a unit. Three panels query the recording rules in this category, so the dashboard and the rule file can be validated against each other.
- File
- JSON · Alerts
- Use case
- ObservabilityJSON parsing+1· Conversion set
png
4.7 KB
Dashboard Mock 01 (288px)
Synthetic dashboard mock (KPI cards + bar chart): SAMPLE UI for layout / chart vision models. Not a real product.
- File
- PNG · Chart Vision · 288 × 288 px
- Use case
- Computer visionOCR testing· Conversion set
png
4.9 KB
Dashboard Mock 02 (288px)
Synthetic dashboard mock (KPI cards + bar chart): SAMPLE UI for layout / chart vision models. Not a real product.
- File
- PNG · Chart Vision · 288 × 288 px
- Use case
- Computer visionOCR testing· Conversion set
png
4.9 KB
Dashboard Mock 03 (288px)
Synthetic dashboard mock (KPI cards + bar chart): SAMPLE UI for layout / chart vision models. Not a real product.
- File
- PNG · Chart Vision · 288 × 288 px
- Use case
- Computer visionOCR testing· Conversion set
png
4.7 KB
Dashboard Mock 04 (288px)
Synthetic dashboard mock (KPI cards + bar chart): SAMPLE UI for layout / chart vision models. Not a real product.
- File
- PNG · Chart Vision · 288 × 288 px
- Use case
- Computer visionOCR testing· Conversion set