Integrate Your Test Suite

Run test suite on a single browser

// Set this in your testng.conf.json file
"environments": [{
    "os":"Windows",
    "os_version":"10",
    "browser": "chrome",
    "browser_version":"latest",
}]

// Set this in your testng.conf.json file
"environments": [{
    "os":"Windows",
    "osVersion":"10",
    "browserName": "chrome",
    "browserVersion":"latest",
}]

We recommend running your build using a single browser like Chrome or Firefox, to begin with. This will isolate issues during the migration phase and help with faster debugging. Refer to the capabilities on the right to use Chrome.

Once you’ve migrated your test cases or have achieved stability with Chrome or Firefox, you can setup cross-browser testing.

Organize tests

Naming your tests and builds properly is crucial for effective debugging, test reporting and analyzing your build execution time on BrowserStack.

Mark test as passed or failed

To mark whether your test has passed or failed on BrowserStack, use the adjacent Javascript executor in your test script. You can mark a test as passed or failed based on your test assertions.

Set up Debugging capabilities

BrowserStack provides the following debugging capabilities for your tests:

1. Use visual logs capability to capture screenshots at every Selenium command automatically. Enable visual logs by using the browserstack.debug capability as shown on the right.
2. Console Logs with log level ‘errors’ are enabled by default. You can enable different log levels viz. warnings, info, verbose, errors and disable using the browserstack.console capability as shown on the right.
3. Network Logs capture the browser’s performance data such as network traffic, latency, HTTP requests, and responses in a HAR format. You can enable network logs using the browserstack.networkLogs capability as shown on the right.

Commonly used features and advanced-use cases

Here’s a list of features and capabilities you may find useful.