What is @wdio/browserstack-service?
@wdio/browserstack-service is a WebdriverIO service that provides integration with BrowserStack, a cloud-based cross-browser testing platform. This service allows you to run your WebdriverIO tests on BrowserStack's infrastructure, enabling you to test your web applications across a wide range of browsers and devices.
What are @wdio/browserstack-service's main functionalities?
BrowserStack Local Testing
This feature allows you to test your local applications on BrowserStack by establishing a secure connection between your local machine and BrowserStack's infrastructure.
const { remote } = require('webdriverio');
const browserstack = require('@wdio/browserstack-service');
const options = {
user: 'YOUR_BROWSERSTACK_USERNAME',
key: 'YOUR_BROWSERSTACK_ACCESS_KEY',
services: ['browserstack'],
capabilities: {
'bstack:options': {
os: 'Windows',
osVersion: '10',
local: true,
seleniumVersion: '3.141.59'
},
browserName: 'chrome',
browserVersion: 'latest'
}
};
(async () => {
const browser = await remote(options);
await browser.url('http://localhost:3000');
console.log(await browser.getTitle());
await browser.deleteSession();
})();
Parallel Testing
This feature allows you to run tests in parallel across multiple browsers and operating systems, significantly reducing the time required for test execution.
const { remote } = require('webdriverio');
const browserstack = require('@wdio/browserstack-service');
const options = {
user: 'YOUR_BROWSERSTACK_USERNAME',
key: 'YOUR_BROWSERSTACK_ACCESS_KEY',
services: ['browserstack'],
capabilities: [
{
'bstack:options': {
os: 'Windows',
osVersion: '10',
seleniumVersion: '3.141.59'
},
browserName: 'chrome',
browserVersion: 'latest'
},
{
'bstack:options': {
os: 'OS X',
osVersion: 'Big Sur',
seleniumVersion: '3.141.59'
},
browserName: 'safari',
browserVersion: 'latest'
}
]
};
(async () => {
const browser1 = await remote(options.capabilities[0]);
const browser2 = await remote(options.capabilities[1]);
await browser1.url('https://www.example.com');
await browser2.url('https://www.example.com');
console.log(await browser1.getTitle());
console.log(await browser2.getTitle());
await browser1.deleteSession();
await browser2.deleteSession();
})();
Automated Screenshots
This feature allows you to take automated screenshots of your web application during test execution, which can be useful for visual regression testing and debugging.
const { remote } = require('webdriverio');
const browserstack = require('@wdio/browserstack-service');
const options = {
user: 'YOUR_BROWSERSTACK_USERNAME',
key: 'YOUR_BROWSERSTACK_ACCESS_KEY',
services: ['browserstack'],
capabilities: {
'bstack:options': {
os: 'Windows',
osVersion: '10',
seleniumVersion: '3.141.59'
},
browserName: 'chrome',
browserVersion: 'latest'
}
};
(async () => {
const browser = await remote(options);
await browser.url('https://www.example.com');
await browser.saveScreenshot('./screenshot.png');
await browser.deleteSession();
})();
Other packages similar to @wdio/browserstack-service
@wdio/sauce-service
@wdio/sauce-service is a WebdriverIO service that provides integration with Sauce Labs, another cloud-based cross-browser testing platform. Similar to @wdio/browserstack-service, it allows you to run your WebdriverIO tests on Sauce Labs' infrastructure, offering features like parallel testing and automated screenshots.
webdriverio
WebdriverIO is a popular testing framework for Node.js that allows you to run tests on various browsers and devices. While it does not provide direct integration with BrowserStack or Sauce Labs, it can be extended with services like @wdio/browserstack-service and @wdio/sauce-service to achieve similar functionalities.
nightwatch
Nightwatch is an end-to-end testing framework that supports running tests on various browsers and devices. It offers built-in support for BrowserStack and Sauce Labs, making it a viable alternative to using WebdriverIO with @wdio/browserstack-service.
WebdriverIO Browserstack Service
A WebdriverIO service that manages local tunnel and job metadata for Browserstack users.
Installation
The easiest way is to keep @wdio/browserstack-service
as a devDependency in your package.json
.
{
"devDependencies": {
"@wdio/browserstack-service": "^7.16.3"
}
}
You can simple do it by:
npm install @wdio/browserstack-service --save-dev
Instructions on how to install WebdriverIO
can be found here.
Configuration
WebdriverIO has Browserstack support out of the box. You should simply set user
and key
in your wdio.conf.js
file. This service plugin provides supports for Browserstack Tunnel. Set browserstackLocal: true
also to activate this feature.
Reporting of session status on BrowserStack will respect strict
setting of Cucumber options.
exports.config
user: process.env.BROWSERSTACK_USERNAME,
key: process.env.BROWSERSTACK_ACCESS_KEY,
services: [
['browserstack', {
browserstackLocal: true
}]
],
};
Options
In order to authorize to the BrowserStack service your config needs to contain a user
and key
option.
browserstackLocal
Set this to true to enable routing connections from Browserstack cloud through your computer.
Type: Boolean
Default: false
preferScenarioName
Cucumber only. Set this to true to enable updating the session name to the Scenario name if only a single Scenario was ran. Useful when running in parallel with wdio-cucumber-parallel-execution.
Type: Boolean
Default: false
forcedStop
Set this to true to kill the browserstack process on complete, without waiting for the browserstack stop callback to be called. This is experimental and should not be used by all. Mostly necessary as a workaraound for this issue.
Type: Boolean
Default: false
opts
Specified optional will be passed down to BrowserstackLocal.
Type: Object
Default: {}
List of available local testing modifiers to be passed as opts:
Local Identifier
If doing simultaneous multiple local testing connections, set this uniquely for different processes -
opts = { localIdentifier: "randomstring" };
Verbose Logging
To enable verbose logging -
opts = { verbose: "true" };
Note - Possible values for 'verbose' modifier are '1', '2', '3' and 'true'
Force Local
To route all traffic via local(your) machine -
opts = { forceLocal: "true" };
Folder Testing
To test local folder rather internal server, provide path to folder as value of this option -
opts = { f: "/my/awesome/folder" };
Force Start
To kill other running Browserstack Local instances -
opts = { force: "true" };
Only Automate
To disable local testing for Live and Screenshots, and enable only Automate -
opts = { onlyAutomate: "true" };
Proxy
To use a proxy for local testing -
- proxyHost: Hostname/IP of proxy, remaining proxy options are ignored if this option is absent
- proxyPort: Port for the proxy, defaults to 3128 when -proxyHost is used
- proxyUser: Username for connecting to proxy (Basic Auth Only)
- proxyPass: Password for USERNAME, will be ignored if USERNAME is empty or not specified
opts = {
proxyHost: "127.0.0.1",
proxyPort: "8000",
proxyUser: "user",
proxyPass: "password",
};
Local Proxy
To use local proxy in local testing -
- localProxyHost: Hostname/IP of proxy, remaining proxy options are ignored if this option is absent
- localProxyPort: Port for the proxy, defaults to 8081 when -localProxyHost is used
- localProxyUser: Username for connecting to proxy (Basic Auth Only)
- localProxyPass: Password for USERNAME, will be ignored if USERNAME is empty or not specified
opts = {
localProxyHost: "127.0.0.1",
localProxyPort: "8000",
localProxyUser: "user",
localProxyPass: "password",
};
PAC (Proxy Auto-Configuration)
To use PAC (Proxy Auto-Configuration) in local testing -
- pac-file: PAC (Proxy Auto-Configuration) file’s absolute path
opts = { "pac-file": "<pac_file_abs_path>" };
Binary Path
By default, BrowserStack local wrappers try downloading and executing the latest version of BrowserStack binary in ~/.browserstack or the present working directory or the tmp folder by order. But you can override these by passing the -binarypath argument.
Path to specify local Binary path -
opts = { binarypath: "/path/to/binary" };
Logfile
To save the logs to the file while running with the '-v' argument, you can specify the path of the file. By default the logs are saved in the local.log file in the present woring directory.
To specify the path to file where the logs will be saved -
opts = { verbose: "true", logFile: "./local.log" };
For more information on WebdriverIO see the homepage.