Runs exported Selenium IDE tests in command line
Node.js is required to use selenium-side-runner
.
The project guarantees support for the active LTS major version (e.g. 10 & 12).
NOTE: The minimum supported version of Node is now 10.15.0 LTS
yarn global add selenium-side-runner
or
npm install -g selenium-side-runner
selenium-side-runner project.side project2.side *.side
selenium-side-runner -c "browserName=chrome platform=MAC"
selenium-side-runner -c "chromeOptions.binary='/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'"
selenium-side-runner -c "chromeOptions.args=[disable-infobars, headless]"
selenium-side-runner --server http://localhost:4444/wd/hub
Will only run tests matching the filter
selenium-side-runner --filter mytest
Change the base URL that the tests were recorded with, note that it will not affect tests that used absolute URLs.
selenium-side-runner --base-url https://www.seleniumhq.org
All of the configuration can be written in the .side.yml
file, the runner will load it from the current working directory automatically.
capabilities:
browserName: "firefox"
baseUrl: "https://www.seleniumhq.org"
server: "http://localhost:4444/wd/hub"
Running tests faster through the use of multiple workers
selenium-side-runner -w 4
The runner will automatically set the number of workers to the amount of cores available, for most cases this is the best result.
Note: unless you specified that a suite is parallel, it will still run the contained tests sequentially, though the runner will run suites in parallel by default.
To mark a suite's tests as parallel, set that in the suite's settings in the IDE.
selenium-side-runner
can pass proxy capabilities to the browser using the following schemes.
Configures WebDriver to bypass all browser proxies.
selenium-side-runner --proxy-type=direct
proxyType: direct
Manually configures the browser proxy.
selenium-side-runner --proxy-type=manual --proxy-options="http=localhost:434 bypass=[http://localhost:434, http://localhost:8080]"
proxyType: manual
proxyOptions:
http: http://localhost:434
https: http://localhost:434
ftp: http://localhost:434
bypass:
- http://localhost:8080
- http://host:434
- http://somethingelse:32
Configures WebDriver to configure the browser proxy using the PAC file at the given URL.
selenium-side-runner --proxy-type=pac --proxy-options="http://localhost/pac"
proxyType: pac
proxyOptions: http://localhost/pac
Creates a proxy configuration for a socks proxy.
selenium-side-runner --proxy-type=socks --proxy-options="socksProxy=localhost:434 socksVersion=5"
proxyType: socks
proxyOptions:
socksProxy: localhost:434
socksVersion: 5
Configures WebDriver to use the current system's proxy.
selenium-side-runner --proxy-type=system
proxyType: system
When running your projects make sure that the command is aware of the locator strategy before variables are evaluated.
For example click | id=${myButton}
vs click | ${idOfMyButton}
.
Always use the first one, since the strategy is hardcoded in the command, the second would yield an error.
But it works in the IDE.
That is because the IDE calculates locator strategies differently than the runner, it is a known current issue.