Repository navigation
issue-tracker: synthetic user-testing scenario for the GitHub mock - #195
Merged
Merged
Conversation
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>
This was referenced Sep 29, 2026
This was referenced Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/andtooling/are untouched.Scenario.
MOCK_SCENARIO=user-testingonintegrations/localthought/mock-proxy.mjs(read by the fixture'screate, sofixtures/index.mjsneeds no change) swaps the seeded repositories for synthetic ones infixtures/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 anullbody.acme-studio/brand-guide(2 issues) andacme-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/trackerwith 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:doingis 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) andfailNext([status, count]: the nextcountproxied 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 sameacme-studio/websiteissues, labels (includingatomic:doing) and comments into an empty, disposable repository. It runs throughgh apias whichever account the GitHub CLI is signed in as, and never reads a token. Without--yesit 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.tshas 7 tests covering the scenario, the label routes, the drivers, and that the default scenario lists onlyatomic-fixture/*. The lane'svitest.config.tsnow includesfixtures/**/*.test.ts.Checked at pin
2567fc30b:node integrations/tooling/run-lane.mjs issue-tracker --tier typecheck: passednode integrations/tooling/run-lane.mjs issue-tracker --tier unit: 194 passed, 8 skippednode integrations/tooling/run-lane.mjs issue-tracker --tier e2e: 1 passednode --test integrations/localthought/mock-proxy.test.mjs: 15/15By hand, once, on 2026-09-25, against atomic-server
bc39dac4bin a Vite dev build (atomic-serverscripts/demo-session/demo-session.sh --plugin issue-tracker, on its local branchclaude/demo-session-tooling): connect, the picker and importingacme-studio/websiteworked. The import took about 33 s. That run needed a local host patch for a dev-only StrictMode bug inProxyConnectReturn, 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