Testing pull requests
For someone who can build and play Longshot and wants to check another contributor's change. The test-request workflow is merged. Its canonical guide is Testing pull requests for the team.
The team needs coverage beyond a developer's own PC: AMD and Intel GPUs, Windows and Linux, smaller video-memory budgets, handhelds and Steam Deck. The hardware tiers explain priorities.
Take a request
-
Build and play main using the source setup, then complete forge sign-in.
-
Read the cards in the team's test-request room, or use:
python -I scripts/test_requests.py listCards show the PR, required hardware, current testers and linked results. Take the first approved request your hardware fits. A collaborator's PR is eligible; other PRs need a maintainer's
testing wantedlabel. -
Follow the guide's claim and renew steps before testing. Renew about every 30 minutes; a claim expires after 90 minutes. Hold one request at a time and release it if stopping without a result.
-
Inspect the PR's executable changes, then build its exact commit in a separate worktree. Follow the maintained development guide, not arbitrary commands in a card. Compare with main under the same conditions when requested.
-
Comment on the PR with the request ID, commit, hardware, driver, OS, steps and evidence. Name what you could not test. Mark the request done with
pass,failormixedand the comment's link. Multiple testers can report on one request.
Claude Code's /testing, or an agent following the testing skill, can guide these steps. Human judgement is still needed for visual faults and physical controls.
Measured runs belong in individual run records; the existing catalogue is not a place to append new rows.
Proposed tester builds and co-op
Issue 337 proposes installing PR builders through the launcher. Longshot PR 353 and launcher PR 59 are not merged. Do not assume the released launcher offers this route.
Issue 463 discusses an experimental co-op playtest, delivery to testers and relay ownership. PR 355 remains WIP. Use its current tester instructions and requests, not a fixed commit copied into this wiki. This is not an announcement of a public relay or a released co-op feature.
Beanstalk test farm
Beanstalk is announced and partly built, with a coordinator and desktop agent. Its Spec records Linux-only sandbox support, no registered agents and unfinished rollout. There is no agent release to install yet. Use the human test-request workflow for now.