> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/regression-testing/browserstack.md).

# BrowserStack

<div align="left"><img src="/files/ykKF4vawCZvx6T1x5HbO" alt=""></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect BrowserStack**

* Find the **BrowserStack** integration module under the **Regression testing** section
* Click the **Connect** button
* Enter a BrowserStack API Access Key and the associated username
  * You can generate a username and associated API access key in BrowserStack by going to **Settings > Product > Service Accounts**
* Click **Save**; you’ll be presented with a dialog in which to select your BrowserStack project and add any test run naming keywords

{% hint style="warning" %}
For the release linkage, Runway will parse your test run names for the presence of a version string (e.g. “**2.3.0**”)
{% endhint %}

{% hint style="info" %}
You can optionally add test run naming keywords (case insensitive) to associate test runs with a particular app, e.g. "iOS" or "Android"
{% endhint %}

For more information on how Runway will leverage BrowserStack, visit the [Regression testing step](/using-runway/release-steps/regression-testing.md) article.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.runway.team/integrations/regression-testing/browserstack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.