TestRelicBrowserStack Integration
Connect BrowserStack at the organization level with username and access key, then scope builds per repository using Cloud Farms settings.
Connect BrowserStack so TestRelic can use your BrowserStack Automate and App Automate account data for this organization. Credentials are org-wide; optional build filters and product choice are configured per repository.
What you configure in TestRelic
| Level | Where | What you set |
|---|---|---|
| Organization | Settings → Integrations | Username and access key |
| Repository | Repository detail → Integrations → Cloud Farms | Product, optional project, build filter, artifact caching |
Build filters are described in the sections below; they limit which BrowserStack builds are associated with each repo.
Connect BrowserStack (organization)
- Open Settings → Integrations.
- Find the BrowserStack card and open Configure (or Connect if not yet connected).
- Enter:
- Username — Your BrowserStack username (often your account email).
- Access Key — From the BrowserStack dashboard: Account Settings → Access Keys.
- Save to verify the connection.
Vendor reference
BrowserStack's own API documentation is published at BrowserStack Automate API reference. Use it alongside TestRelic only when you need vendor API details; TestRelic connection is entirely through the fields above.
Per-repository: Cloud Farms
After BrowserStack is connected for the organization:
- Open the Repository you want to scope.
- Go to the Integrations tab.
- Open the Cloud Farms segment (it appears when TestMu AI or BrowserStack is connected at org level).
BrowserStack Build Filter panel
| Field | Purpose |
|---|---|
| Product | Automate (web) or App Automate (mobile). |
| Project | Optional. Restricts builds to a BrowserStack project name when set. |
| Build filter | Optional substring. Only builds whose name contains this string are pulled for this repo. Leave blank to include all builds. Example placeholder in the app: a label like regression for substring matching. |
| Cache videos / logs / screenshots to TestRelic storage | When enabled, artifacts are cached in TestRelic so the Session Workspace and Ask AI can still use them if BrowserStack is temporarily unreachable. |
Click Save to persist repository settings.
Org connection required
If BrowserStack is not connected under Settings → Integrations, the Cloud Farms area prompts you to connect there first; per-repo filters apply only after org-level credentials are valid.
TestMu AI Integration
Connect TestMu AI at the organization level with username and access key, then scope builds per repository using Cloud Farms settings.
Amplitude Integration
Connect Amplitude to capture analytics events during test sessions and align test navigation patterns with real user journeys.