Skip to content

issue-tracker: synthetic user-testing scenario for the GitHub mock - #195

Merged
michielbdejong merged 2 commits into
mainfrom
claude/user-testing-fixtures
Sep 29, 2026
Merged

michielbdejong merged 2 commits into
mainfrom
claude/user-testing-fixtures

Conversation

@michielbdejong

@michielbdejong michielbdejong commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

An opt-in scenario for the mock proxy's github-issues fixture, for trying the GitHub issues drive app by hand without a GitHub account. Everything is under integrations/issue-tracker/; localthought/ and tooling/ are untouched.

Scenario. MOCK_SCENARIO=user-testing on integrations/localthought/mock-proxy.mjs (read by the fixture's create, so fixtures/index.mjs needs no change) swaps the seeded repositories for synthetic ones in fixtures/github-issues/user-testing.mjs:

  • acme-studio/website: 16 issues (9 Todo, 3 Doing, 4 Done) and 7 comments by four invented people. Labels bug, enhancement, design, docs, maintenance, good first issue and planning, as GitHub's { name, color } objects. It includes one title of about 160 characters, Markdown bodies with a task list, code blocks and links, and one issue with a null body.
  • acme-studio/brand-guide (2 issues) and acme-studio/old-site (issues turned off) in the picker.

All data is invented and the file says so. The default scenario is unchanged: atomic-fixture/tracker with 2 issues and 1 comment, which the e2e asserts.

Label routes now match a stored label by name, because the scenario stores label objects. atomic:doing is still added as a plain name. The behaviour for the default scenario's plain names is the same.

New drivers (POST /fixture/github-issues/<driver>): createIssue, createComment, commentAs ([repo, number, login, body], a comment by someone else) and failNext ([status, count]: the next count proxied requests answer 503, 429/403 with GitHub's rate-limit message, or 401).

Live GitHub. fixtures/github-issues/seed-live-repo.mjs --repo <owner>/<name> [--yes] puts the same acme-studio/website issues, labels (including atomic:doing) and comments into an empty, disposable repository. It runs through gh api as whichever account the GitHub CLI is signed in as, and never reads a token. Without --yes it only prints what it would do. It refuses a repository that already has issues. It's meant for an issue-tracker session on the usertest droplet with a dedicated test account. Checked only for its refusals (bad arguments, a repository with issues); no repository has been seeded with it yet.

Tests. fixtures/github-issues/scenario.test.ts has 7 tests covering the scenario, the label routes, the drivers, and that the default scenario lists only atomic-fixture/*. The lane's vitest.config.ts now includes fixtures/**/*.test.ts.

Checked at pin 2567fc30b:

  • node integrations/tooling/run-lane.mjs issue-tracker --tier typecheck: passed
  • node integrations/tooling/run-lane.mjs issue-tracker --tier unit: 194 passed, 8 skipped
  • node integrations/tooling/run-lane.mjs issue-tracker --tier e2e: 1 passed
  • node --test integrations/localthought/mock-proxy.test.mjs: 15/15
  • oxlint and oxfmt as CI runs them: clean

By hand, once, on 2026-09-25, against atomic-server bc39dac4b in a Vite dev build (atomic-server scripts/demo-session/demo-session.sh --plugin issue-tracker, on its local branch claude/demo-session-tooling): connect, the picker and importing acme-studio/website worked. The import took about 33 s. That run needed a local host patch for a dev-only StrictMode bug in ProxyConnectReturn, filed separately in atomic-server.

Not verified: any of this against live GitHub. User testing moved to the usertest droplet with real accounts. This scenario is for local mock sessions and future e2e cases.

🤖 Generated with Claude Code

Michiel de Jong and others added 2 commits September 29, 2026 13:08
MOCK_SCENARIO=user-testing on the mock proxy swaps the seeded repositories
for invented ones (fixtures/github-issues/user-testing.mjs): acme-studio/
website with 16 issues and 7 comments, a small second repository and one with
issues turned off. Labels use GitHub's { name, color } shape, so the label
routes now match by name. The default scenario the e2e asserts is unchanged.

New drivers for changing the GitHub side during a session: createIssue,
createComment, commentAs (a comment by another login) and failNext (the next
requests answer 503, 429/403 or 401). scenario.test.ts covers both, and the
lane's vitest config now includes fixtures/**/*.test.ts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… issues

seed-live-repo.mjs puts the user-testing scenario's acme-studio/website
issues, labels (with atomic:doing) and comments into an empty repository
through `gh api`, as whichever account the GitHub CLI is signed in as. It
never reads a token, prints its plan unless given --yes, and refuses a
repository that already has issues. For user testing on the usertest
droplet against live GitHub.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michielbdejong
michielbdejong merged commit 12f5fbb into main Sep 29, 2026
18 checks passed
michielbdejong pushed a commit that referenced this pull request Sep 29, 2026
Resolve integrations/issue-tracker/README.md: keep both the user-testing
scenario (#195) and the synthetic 206-item import test (#206) in the
verification note.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant