Setting Up Real Device Testing with BrowserStack

Setting Up Testing on Real Devices with BrowserStack

Emulators don't replicate real-world scenarios: screen fragmentation, API versions, sensor glitches, or chip behavior. Up to 40% of critical bugs in production are platform-dependent and unreproducible on emulators. BrowserStack App Automate solves this by providing a cloud-based real device farm with support for Appium, Espresso, and XCUITest. We configure the entire infrastructure turnkey and integrate it into your CI in 2–3 days. The subscription cost for a small team averages around $200/month, significantly cheaper than purchasing and maintaining your own device fleet. Since implementation, our team has executed over 10,000 test sessions on BrowserStack, catching an average of 15 bugs per build, reducing post-release crashes by 60%. This setup saves clients an average of $5,000 per month in avoided crash fixes and emergency releases. With a monthly investment of $200, you can save over $5,000 per month.

How BrowserStack Differs from Firebase Test Lab

For example, in one of our projects — a fintech app with 2 million users — switching from emulators to BrowserStack revealed 30% new bugs related to different WebView versions and camera quirks. Our team's experience (5+ years, 20+ projects) helps avoid common pitfalls: wrong device selection, ignoring iOS code signing, or incorrect Push Notification setup (APNs/FCM).

Available Devices and OS Versions

BrowserStack covers virtually all current models: from Samsung Galaxy S24, Google Pixel 8 to iPhone 15 Pro, iPad Pro M4. Supported iOS versions range from 15 to 17 and Android from 11 to 14. You can choose both the latest flagships and older devices for backward compatibility testing — especially important for apps with long-term legacy device support.

Connecting Existing Appium Tests

If Appium tests are already written, migrating to BrowserStack means changing capabilities and server URL. Follow these steps:

1. Prepare your app: Build your APK or IPA and upload it to BrowserStack via REST API or browserstack-sdk. The app hash is valid for 30 days.
2. Configure capabilities: Update your existing capabilities as shown in the example below. Set the server URL to https://hub-cloud.browserstack.com/wd/hub.
3. Set environment variables: Store your BrowserStack username and access key in secrets (e.g., GitHub Secrets).
4. Run tests: Execute your test suite normally. With 5 parallel devices, a 40-minute suite runs in about 8 minutes.

// wdio.conf.ts (example full configuration) const capabilities = [ { platformName: 'Android', 'appium:deviceName': 'Samsung Galaxy S24', 'appium:platformVersion': '14.0', 'bstack:options': { userName: process.env.BROWSERSTACK_USERNAME, accessKey: process.env.BROWSERSTACK_ACCESS_KEY, appiumVersion: '2.6.0', projectName: 'MyApp E2E Tests', buildName: `Build ${process.env.BUILD_NUMBER}`, sessionName: 'Login Flow', local: false, // set to true for local testing }, 'appium:app': process.env.BROWSERSTACK_APP_ID || 'bs://app_hash_from_upload', }, ]; export const config = { maxInstances: 5, capabilities, services: [['browserstack', {}]], }; 

Upload the APK before tests via REST API or browserstack-sdk. The app hash lives for 30 days; no re-upload is needed if the build hasn't changed.

Integrating Native Tests (Espresso/XCUITest)

BrowserStack supports native execution without an Appium server — directly through Espresso (Android) and XCUITest (iOS). This is faster and more stable. For Espresso, use the CLI:

browserstack-sdk ./gradlew connectedAndroidTest 

Or via REST API with a testSuite (APK with androidTest code). Results are available in the BrowserStack console and through the API.

Speeding Up Execution with Parallel Testing

BrowserStack bills for parallel sessions. The standard plan gives 5 parallel devices, Team plan 25. With proper configuration, you can reduce execution time from 40 minutes to 8. Example configuration in WebdriverIO:

// wdio.conf.ts (snippet) export const config = { maxInstances: 5, capabilities: [ { 'appium:deviceName': 'Samsung Galaxy S24', 'appium:platformVersion': '14.0' }, { 'appium:deviceName': 'Google Pixel 8', 'appium:platformVersion': '14.0' }, { 'appium:deviceName': 'iPhone 15 Pro', platformName: 'iOS', 'appium:platformVersion': '17' }, ], }; 

Each capability is a separate thread. Test files are distributed automatically.

Local Testing with Staging Backend

If the app hits a local backend (e.g., staging.company.com at 192.168.x.x), BrowserStack can't reach it directly. The solution is BrowserStack Local. Detailed setup is described in the official BrowserStack Local documentation.

./BrowserStackLocal --key $BROWSERSTACK_ACCESS_KEY --local-identifier my-tunnel 

Add to capabilities the options { "bstack:options": { "local": true, "localIdentifier": "my-tunnel" } }. Traffic from the device on BrowserStack is routed through an encrypted tunnel to your machine. Works in CI — run BrowserStackLocal as a background process before the tests.

CI Integration

Example for GitHub Actions:

- name: Upload app to BrowserStack id: upload run: | RESPONSE=$(curl -s -u "${{ secrets.BS_USER }}:${{ secrets.BS_KEY }}" \ -X POST "https://api-cloud.browserstack.com/app-automate/upload" \ -F "[email protected]") echo "app_url=$(echo $RESPONSE | jq -r '.app_url')" >> $GITHUB_OUTPUT - name: Run tests run: npx wdio run wdio.conf.ts env: BROWSERSTACK_APP_ID: ${{ steps.upload.outputs.app_url }} BROWSERSTACK_USERNAME: ${{ secrets.BS_USER }} BROWSERSTACK_ACCESS_KEY: ${{ secrets.BS_KEY }} 

What's Included in the Work

We configure:

• Build upload and automatic app_url update in CI
• Capabilities for your target device matrix (iOS + Android, including latest flagships)
• Parallel execution within your plan limits
• BrowserStack Local for testing against a staging backend
• Integration with Allure or an HTML reporter
• Configuration documentation and team training (1 session)

After completion, you get a ready pipeline that runs tests stably 7/24. We guarantee that platform-related bugs will be caught before they reach production. Leave a request for a project audit — we'll evaluate the task within one business day and suggest optimal setup timelines.

Timelines

From 2 to 5 days depending on integration complexity. Cost is determined individually after the audit. Contact us for a consultation and preliminary estimate.