Skip to main content
Ask AI

BrowserStack Integration

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​

LevelWhereWhat you set
OrganizationSettings → IntegrationsUsername and access key
RepositoryRepository detail → Integrations → Cloud FarmsProduct, 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)​

  1. Open Settings → Integrations.
  2. Find the BrowserStack card and open Configure (or Connect if not yet connected).
  3. Enter:
    • Username — Your BrowserStack username (often your account email).
    • Access Key — From the BrowserStack dashboard: Account Settings → Access Keys.
  4. 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:

  1. Open the Repository you want to scope.
  2. Go to the Integrations tab.
  3. Open the Cloud Farms segment (it appears when TestMu AI or BrowserStack is connected at org level).

BrowserStack Build Filter panel​

FieldPurpose
ProductAutomate (web) or App Automate (mobile).
ProjectOptional. Restricts builds to a BrowserStack project name when set.
Build filterOptional 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 storageWhen 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.