BLOG
BlogGuides

Share a live test run in a pull request, no account needed

Every run started from CI, the API or an agent comes with a watch link. Paste it in the pull request and reviewers watch the browser live, then read the result.

Reviewers should not need a login#

A pull request says "tested". The reviewer has to take it on trust, or check out the branch and click through. Neither scales, and neither works for the product manager or designer who wants to see the change without a dev setup.

Every run started from CI, the API, the command-line tool or an AI agent answers with two addresses: the run page (sign-in required) and a watch link that anyone with it can open. From the watch link docs:

  • While the run goes: the live screen, the checks as they are verified, and each step with the picture right after it.
  • When it ends: the read-only result, with the checks and values, the replay, the video and the console and network logs.
  • Nothing else of your workspace: no other runs, tests or settings.

The command-line tool prints it under each started run. The GitHub Action exposes them as the watch-urls output, so a workflow step can post them as a pull request comment.

How long it works#

A watch link works while the run is queued or running and for 24 hours after it finishes, unless the workspace chose otherwise (from 1 hour to 7 days). Whatever happens, it stops 8 days after it was made. For a result you want to keep sharing, make a share link, which lasts 7, 30 or 90 days and can be turned off at any time.

Share on a run: choose how long the link works. Links that work now are listed, each with Turn off.
Share on a run: choose how long the link works. Links that work now are listed, each with Turn off.

Public repositories#

Runs from a public repository get a link only workspace members can open, so a test of your staging site is not broadcast to everyone who reads the repo.

Who decides#

Workspace admins choose whether watch links are on and how long they last. Turn them off if your app's screens show data that should stay inside the team; share links still work for results you choose to share one by one.

A habit that helps#

Ask for a watch link in the pull request template: "Testsy run:" followed by the link. Reviewers get evidence, the author gets a second pair of eyes on the replay, and the link expires on its own.

This post is part of Release testing for product teams.

Filed underWebSharing and alertsCI, schedules and agents