Fixtures for the fjord-android manual QA checklist. Not a real project.
  • Shell 86.8%
  • Kotlin 5.7%
  • TypeScript 4%
  • Python 3.5%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Stephen Way dcf84fbafc
All checks were successful
QA fixture run / quick (push) Successful in 2s
QA fixture run / chatty (push) Successful in 3s
QA fixture run / outcome (push) Successful in 3s
qa- remove m76 issue template probes
2026-10-03 01:54:25 +00:00
.forgejo/workflows qa- remove m76 issue template probes 2026-10-03 01:54:25 +00:00
assets Add the fixture content 2026-09-18 20:25:28 -07:00
data Remove the QA file with ? and # in its name 2026-10-02 15:44:35 +00:00
src Extend the sample on the base branch (#7) 2026-09-19 15:20:51 +00:00
README.md Add the fixture content 2026-09-18 20:25:28 -07:00
setup.sh Survive a merged fixture pull request 2026-09-19 07:19:20 -07:00

Fjord QA fixtures

Nothing here is a real project. This repository exists so that a person walking docs/manual-qa.md in fjord-android can reach every screen the checklist names, including the ones that are unreachable on an ordinary repository: the wiki, the stack lane, the binary and oversized file guards, and a commit with no diff.

setup.sh builds the rest of it (labels, milestone, issues, the stacked pull requests, a release, and a wiki page) against the Forgejo API. It is idempotent, so running it twice is safe and the second run should report everything as present.

./setup.sh                       # rasterstate/fjord-qa-fixtures
OWNER=you REPO=scratch ./setup.sh

What each file is here to trip

Path Screen it exercises
src/Sample.kt, src/sample.py, src/sample.ts File view, native syntax highlighting, three lexers
data/blob.bin The "binary file not shown" guard. A NUL byte in the first 8000 is the heuristic.
data/big.txt The "too large to display" guard, which trips over 512 KiB.
assets/logo.png An image that renders, as the control for the two guards above.
.forgejo/workflows/qa.yml Actions: a run list, a run detail, a job, logs, and workflow_dispatch.

The empty commit on main is deliberate. It is the only way to see the "no diff available" guard on the commit detail screen read as a sentence rather than as a blank.