Bird
Raised Fist0
Selenium Pythontesting~15 mins

Cloud testing platforms (BrowserStack, Sauce Labs) in Selenium Python - Build an Automation Script

Choose your learning style10 modes available
Verify login functionality on BrowserStack cloud platform
Preconditions (3)
Step 1: Open remote browser session on BrowserStack with Windows 10 and Chrome latest
Step 2: Navigate to 'https://example.testapp.com/login'
Step 3: Enter 'testuser@example.com' in the email input field with id 'email'
Step 4: Enter 'TestPass123' in the password input field with id 'password'
Step 5: Click the login button with id 'loginBtn'
Step 6: Wait until the dashboard page loads and URL contains '/dashboard'
✅ Expected Result: User is successfully logged in and redirected to the dashboard page with URL containing '/dashboard'
Automation Requirements - Selenium WebDriver with Python
Assertions Needed:
Verify current URL contains '/dashboard' after login
Verify login button is clickable before clicking
Verify email and password fields are present before input
Best Practices:
Use explicit waits to wait for elements and page load
Use remote WebDriver with desired capabilities for BrowserStack
Use try-except blocks to handle exceptions gracefully
Close the remote browser session after test
Automated Solution
Selenium Python
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

# BrowserStack credentials and URL
BROWSERSTACK_USERNAME = 'your_username'
BROWSERSTACK_ACCESS_KEY = 'your_access_key'
remote_url = f'https://{BROWSERSTACK_USERNAME}:{BROWSERSTACK_ACCESS_KEY}@hub-cloud.browserstack.com/wd/hub'

# Desired capabilities for Windows 10 and Chrome latest
desired_cap = {
    'os': 'Windows',
    'os_version': '10',
    'browserName': 'Chrome',
    'browser_version': 'latest',
    'name': 'Login Test on BrowserStack'
}

try:
    driver = webdriver.Remote(
        command_executor=remote_url,
        desired_capabilities=desired_cap
    )

    wait = WebDriverWait(driver, 15)

    # Navigate to login page
    driver.get('https://example.testapp.com/login')

    # Wait for email field and enter email
    email_field = wait.until(EC.presence_of_element_located((By.ID, 'email')))
    email_field.send_keys('testuser@example.com')

    # Wait for password field and enter password
    password_field = wait.until(EC.presence_of_element_located((By.ID, 'password')))
    password_field.send_keys('TestPass123')

    # Wait for login button to be clickable and click
    login_button = wait.until(EC.element_to_be_clickable((By.ID, 'loginBtn')))
    login_button.click()

    # Wait until URL contains '/dashboard'
    wait.until(EC.url_contains('/dashboard'))

    # Assertion: Verify URL contains '/dashboard'
    assert '/dashboard' in driver.current_url, 'Login failed or dashboard not loaded'

finally:
    driver.quit()

This script uses Selenium WebDriver with Python to run a test on BrowserStack cloud platform.

First, it sets up the remote WebDriver with BrowserStack credentials and desired capabilities for Windows 10 and Chrome latest.

It opens the login page URL, waits explicitly for the email and password fields to be present, then inputs the test credentials.

It waits for the login button to be clickable before clicking it.

After clicking, it waits until the URL contains '/dashboard' to confirm successful login.

Finally, it asserts that the URL contains '/dashboard' to verify the test passed.

The driver is quit in a finally block to ensure the browser session closes even if errors occur.

Common Mistakes - 4 Pitfalls
Using time.sleep() instead of explicit waits
{'mistake': 'Hardcoding local WebDriver instead of using remote WebDriver for BrowserStack', 'why_bad': "Tests won't run on BrowserStack cloud without remote WebDriver setup.", 'correct_approach': 'Use webdriver.Remote with BrowserStack hub URL and desired capabilities.'}
Not verifying elements are present or clickable before interacting
Not closing the browser session after test
Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials to verify login success or failure.

Show Hint

Practice

(1/5)
1. What is the main advantage of using cloud testing platforms like BrowserStack or Sauce Labs for Selenium tests?
easy
A. You do not need to write any Selenium code
B. They automatically fix bugs in your code
C. Tests run only on your local machine
D. You can test on many browsers and devices without owning them

Solution

  1. Step 1: Understand cloud testing platform purpose

    Cloud platforms provide access to many browsers and devices remotely.
  2. Step 2: Compare options

    Only the option stating 'You can test on many browsers and devices without owning them' correctly states the main advantage; others are incorrect or unrelated.
  3. Final Answer:

    You can test on many browsers and devices without owning them -> Option D
  4. Quick Check:

    Cloud testing = remote multi-browser/device access [OK]
Hint: Cloud platforms = test many devices remotely [OK]
Common Mistakes:
  • Thinking tests run locally only
  • Believing cloud platforms fix code bugs
  • Assuming no Selenium code is needed
2. Which of the following is the correct way to specify the remote WebDriver URL for BrowserStack in Python Selenium?
easy
A. driver = webdriver.Remote(command_executor='https://hub-cloud.browserstack.com/wd/hub', desired_capabilities=capabilities)
B. driver = webdriver.Chrome('https://hub-cloud.browserstack.com/wd/hub')
C. driver = webdriver.Firefox('browserstack.com')
D. driver = webdriver.Remote('http://localhost:4444/wd/hub')

Solution

  1. Step 1: Identify correct Remote WebDriver syntax

    Using webdriver.Remote with command_executor URL and capabilities is correct for BrowserStack.
  2. Step 2: Check other options

    Options using Firefox or Chrome constructors with URLs are incorrect; the option with localhost URL is also wrong.
  3. Final Answer:

    driver = webdriver.Remote(command_executor='https://hub-cloud.browserstack.com/wd/hub', desired_capabilities=capabilities) -> Option A
  4. Quick Check:

    Remote WebDriver + BrowserStack URL = driver = webdriver.Remote(command_executor='https://hub-cloud.browserstack.com/wd/hub', desired_capabilities=capabilities) [OK]
Hint: Use webdriver.Remote with BrowserStack URL [OK]
Common Mistakes:
  • Using local URLs instead of BrowserStack URL
  • Calling Chrome or Firefox constructors with URLs
  • Omitting desired capabilities
3. Given this Python Selenium code snippet for Sauce Labs, what will be printed if the test runs successfully?
from selenium import webdriver
caps = {
  'browserName': 'chrome',
  'platformName': 'Windows 10',
  'browserVersion': 'latest'
}
driver = webdriver.Remote(
  command_executor='https://username:accesskey@ondemand.saucelabs.com:443/wd/hub',
  desired_capabilities=caps
)
driver.get('https://example.com')
print(driver.title)
driver.quit()
medium
A. An error about missing local Chrome driver
B. The title of https://example.com page
C. Empty string
D. Sauce Labs login page title

Solution

  1. Step 1: Understand remote driver usage

    The code uses Sauce Labs remote URL with correct capabilities, so it runs on Sauce Labs cloud.
  2. Step 2: Analyze driver.get and print

    driver.get loads example.com, and driver.title prints its page title.
  3. Final Answer:

    The title of https://example.com page -> Option B
  4. Quick Check:

    Remote driver loads page title = The title of https://example.com page [OK]
Hint: Remote driver prints page title, not errors [OK]
Common Mistakes:
  • Expecting local driver errors
  • Thinking remote driver prints login page
  • Assuming empty title without loading
4. You wrote this code to run tests on BrowserStack but get a connection error:
driver = webdriver.Remote(
  command_executor='https://hub-cloud.browserstack.com/wd/hub',
  desired_capabilities=capabilities
)
What is the most likely cause and fix?
medium
A. Missing username and access key in URL; add them as https://username:accesskey@hub-cloud.browserstack.com/wd/hub
B. Wrong browser name in capabilities; change to 'firefox'
C. Local WebDriver server not running; start Selenium server locally
D. Use HTTP instead of HTTPS in URL

Solution

  1. Step 1: Identify connection error cause

    BrowserStack requires authentication via username and access key in the URL.
  2. Step 2: Fix URL with credentials

    Add username and access key before the host in the URL to authenticate properly.
  3. Final Answer:

    Missing username and access key in URL; add them as https://username:accesskey@hub-cloud.browserstack.com/wd/hub -> Option A
  4. Quick Check:

    Authentication URL format fixes connection [OK]
Hint: Add username:accesskey@ in URL for BrowserStack [OK]
Common Mistakes:
  • Ignoring authentication in remote URL
  • Changing browser name without cause
  • Assuming local server needed for cloud
5. You want to run a Selenium test on BrowserStack for a mobile device with these requirements: Android 13, Chrome browser, and device name 'Samsung Galaxy S22'. Which desired capabilities dictionary is correct?
hard
A. { 'platformName': 'Android', 'platformVersion': '12', 'browserName': 'Chrome', 'deviceName': 'Samsung Galaxy S22' }
B. { 'platformName': 'Windows', 'platformVersion': '13', 'browserName': 'Chrome', 'deviceName': 'Samsung Galaxy S22' }
C. { 'platformName': 'Android', 'platformVersion': '13', 'browserName': 'Chrome', 'deviceName': 'Samsung Galaxy S22' }
D. { 'platformName': 'Android', 'browserName': 'Firefox', 'deviceName': 'Samsung Galaxy S22' }

Solution

  1. Step 1: Match platform and version

    Android 13 is required, so platformName must be 'Android' and platformVersion '13'.
  2. Step 2: Check browser and device name

    Browser must be 'Chrome' and deviceName 'Samsung Galaxy S22' exactly.
  3. Step 3: Eliminate incorrect options

    The option with platformVersion '12' has wrong version; the one with 'Windows' has wrong platform; the one with 'Firefox' and no version has wrong browser and missing version.
  4. Final Answer:

    { 'platformName': 'Android', 'platformVersion': '13', 'browserName': 'Chrome', 'deviceName': 'Samsung Galaxy S22' } -> Option C
  5. Quick Check:

    Correct platform, version, browser, device = { 'platformName': 'Android', 'platformVersion': '13', 'browserName': 'Chrome', 'deviceName': 'Samsung Galaxy S22' } [OK]
Hint: Match all capability keys exactly for device testing [OK]
Common Mistakes:
  • Using wrong platform or version
  • Choosing wrong browser name
  • Missing platformVersion key
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard