> Call the `diagnose` tool first. Full index: /llms.txt. Errors: /reference/problems.

# Test a deployed URL

A page that anyone can open over HTTPS, such as a staging site or a preview, needs no tunnel and no install.

## Set it up

1. Create a project and add a web app with the page's start URL.
2. Run `diagnose` (your agent does this first) to see whether a run can start.
3. If the app has a login, add a test account for it. Never share a real customer's login.
4. Find or write [scenarios](/concepts/scenarios-and-test-plans).

## Start a run

From the web app, start a run from a scenario or a test plan. From your agent:

```text
start_run(project_id, app_id, target={"kind": "web", "start_url": "https://staging.example.com/"}, selection, request_id)
```

`selection` is exactly one of `{"kind": "scenarios", "scenario_ids": [...]}` or a test plan. `request_id` is a new unique id for each deliberate run. Send the same one to repeat the same call and no second run starts. See [Runs](/reference/mcp/runs).

## From CI

```bash
talotrace check --project <project id> --app <app id> --scenario <scenario id> --start-url https://staging.example.com/ --timeout 10m --evidence-dir ./evidence
```

With an HTTPS page, leave out `--ports`. Set `TALOTRACE_API_KEY` from your pipeline's secret store. See [API keys](/api-keys).

## Sign-in flows

If the app signs in through another provider, register that provider's callback for the address you test. Use a test account that the provider accepts, and keep its password in test data, never in a scenario's text.