# A fresh look for capability generator

We are excited to unveil a fresh look for capabilities, along with SDK configuration and improved navigation. Hope you love it as much as we do.

## Capabilities

Capabilities are a series of key-value pairs that allow you to configure your tests on the BrowserStack cloud grid.

Use our Capabilities Generator to configure your test suite in the language of your choice. The capabilities generator lets you select from a comprehensive set of options you can use to customize your tests on the BrowserStack Cloud grid. You can also find out more about each capability by scrolling to our [Capabilities Reference](/content/docs/automate/capabilities#reference-main-section/index.html) section.

### Capability generator

#### Other frameworks

- [WebdriverIO](/content/docs/automate/selenium/wdio-browserstack-capabilities/index.html)
- [Cypress](/content/docs/automate/cypress/cypress-capabilities/index.html)
- [Puppeteer](/content/docs/automate/puppeteer/puppeteer-capabilities/index.html)

Selenium - BrowserStack SDK

## Tabs

### Selenium
  
### SeleniumPlaywright

### Integration method

- Browserstack SDK
- Non-SDK Integration
- Non-YAML Schema

### BrowserStack SDK

BrowserStack SDK is a plug-and-play solution that enables you to run your entire test suite with no code changes. Using the SDK reduces the integration time from hours to a few minutes.

### Core Capabilities

- **Select browser or device combination**
- **You can run multiple threads in parallel**
  - Parallel Thread #1: Windows 10, Chrome 120
  - Parallel Thread #2: OS X Monterey, Safari 15.6
  - Parallel Thread #3: iOS, iPhone 13

#### Parallels per platform

The number of parallel threads to be used for each platform set.

- **Resolution**
- **Selenium Version**
- **Appium Version**

### Browser Specific Capabilities

- **Enable Popups**: True / False (default)
- **Allow Cookies**: True / False (default)

## Project details

- **Project Name**: Specify a name for a logical group of builds.
- **Build Name**: Specify a name for a logical group of tests.
- **Build Identifier**: Select a dynamic build identifier that appends to the build name and generates a unique name on the BrowserStack dashboard.
- **Local Connectivity**: Enable BrowserStack Local.
  - Test localhost / internal servers in your network: True / False (default)
- **Debugging**: Debug:
  - Generate screenshots at various steps in your test: True / False (default)
- **Network Logs**: Capture network logs for your test: True / False (default)
- **Record Videos**: Enable video recording during your test: True (Default) / False
- **Console Logs**: Capture network logs for your test: Selenium Logs: Enable seleniumLogs for your test: True (Default) / False
- **Interactive Debugging**: Enable interactive debugging during your test: True (Default) / False
- **Appium Logs**: Enable appium logs for your test: True (Default) / False
- **Timezone**: Configure tests to run on a custom timezone.

### Note: [View the complete list of timezones on Wikipedia](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)

### Simulate Network

Simulate different network conditions when testing on real mobile devices.

---

```yaml
userName: YOUR_USERNAME
accessKey: YOUR_ACCESS_KEY
platforms:
  - browserName: Chrome
    os: Windows
    osVersion: 10
    browserVersion: 120.0
  - browserName: Safari
    os: OS X
    osVersion: Monterey
    browserVersion: 15.6
  - browserName: chromium
    osVersion: 15
    deviceName: iPhone 13
buildIdentifier: ${BUILD_NUMBER}
consoleLogs: info
```

### Capabilities Reference

| BrowserStack specific capabilities |  |
| --- | --- |
| **userName** | For running your Selenium and Appium tests on BrowserStack it, requires a username and an access key for authenticating the user. This capability can be used to set the username. You can find your username and access key on the [Settings page](/content/accounts/profile/details/index.html) under the Automate section. **Example:** `userName: <BROWSERSTACK_USERNAME>` |
| **accessKey** | For running your Selenium and Appium tests on BrowserStack it, requires a username and an access key for authenticating the user. This capability can be used to set the access key. You can find your username and access key on the [Settings page](/content/accounts/profile/details/index.html) under the Automate section. **Example:** `accessKey: <BROWSERSTACK_ACCESSKEY>` |
| **os** | OS you want to test (Windows, OS X).
| **osVersion** | OS version you want to test. (Windows: XP, 7, 8, 8.1, 10 and 11; OS X: Snow Leopard, Lion, etc.)

---