A/B image twins with controlled pixel changes, anti-alias variants, and UI chrome crops for screenshot diff and visual regression tools.
Each card starts with one representative test file. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
68 test families · 115 available files · Page 1 of 4
History
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 t
Repo Config
An intentionally invalid ownership file carrying five defects that all parse as plausible lines: an owner that is neither a handle nor an email, a team with no organisation, a character class, a negation, and a path with
Repo Config
Deliberately overlapping rules so every interesting path matches two or three of them, which is the only way to test that a resolver applies last-match-wins rather than most-specific-wins. One rule has no owners at all,
Merges
What `git show` prints for a merge commit: a `diff --cc` header, an index line naming three blobs, `@@@` hunk markers, and two prefix columns instead of one. The `++` line is the giveaway a reviewer is looking for: conte
History
A breaking change announced twice, which the specification allows: a `!` after the scope and a `BREAKING CHANGE:` footer whose value continues onto a second line. Generators that stop a footer at the first newline lose h
Diffs
The same change as the unified twin, emitted in the pre-unified context format: `*** before` and `--- after` blocks separated by a row of asterisks, with `!`, `+` and `-` change markers. Parsers that assume every diff st
Profiles
The same workload after a change: JSON decoding costs four times as much and gains a new reflect frame, while cache lookups get cheaper. Paired with the baseline so a differential flamegraph can be scored against a known
Diff Regression
Baseline twin A for visual-diff regression (pixel change suite: 1px-crop). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (pixel change suite: 1px-shift). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (button change suite: button-add). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (button change suite: button-label). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (colour change suite: colour-tint). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (button change suite: corner-badge). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (pixel change suite: dot-noise). Compare against twin B.
Diff Regression
Baseline twin A for visual-diff regression (colour change suite: hue-shift). Compare against twin B.
History
The stable machine format of git blame: a full header block the first time a commit appears and a bare `<sha> <old> <new>` line every time after, with each source line following on a tab-prefixed line. A parser that expe
Patches
The `--cover-letter` message git writes ahead of a series: a `[PATCH 0/3]` subject, a shortlog of the authors and their subjects, and the combined diffstat, but no diff of its own. Series tooling has to recognise it as m
History
Per-commit file lists with single-letter status codes, tab-separated. Rename rows are the trap: `R100` is followed by TWO paths instead of one, so a splitter that takes field 2 as the filename reports the old path for re
