To run your tests on a Grid (e.g., your own Grid or on a hosted provider like Sauce Labs) you can specify that along with different capabilities.
#CAL CODERUNNER DRIVER#
See Installing a browser driver for details. NOTE: When running tests locally, some setup is required for each browser. Selenium-side-runner -c "browserName=safari" Selenium-side-runner -c "browserName=firefox" Selenium-side-runner -c "browserName=edge" Selenium-side-runner -c "browserName='internet explorer'" The most common use of capabilities is to specify a different browser for local test execution. With the runner you have the ability to pass in different configuration arguments at run time.
See Test Parallelization In A Suite for details. If you want the tests within a suite to be executed in parallel, there is a setting you'll need to change. NOTE: Parallel execution happens automatically at the suite level. The number of processes is configurable (amongst other things) at run time through various arguments you can provide. When you run this command it will launch your tests in parallel, in multiple browser windows, spread across n processes (where n is the number of available CPU cores on your machine).
side files you can use a wildcard (e.g., /path/to/*.side). > selenium-side-runner /path/to/your-project.side Once everything's installed, running your tests is a simple matter of calling selenium-side-runner from the command-line followed by the path to the project file saved earlier (see Getting Started). See this section of the SafariDriver documentation for details. There are just a few steps you'll need to take to enable it on your machine. It ships with the latest version of Safari. There's some additional setup required for IEDriver to work.
#CAL CODERUNNER INSTALL#
> npm install -g geckodriverįor Internet Explorer, you'll need to be running on Windows, and you'll also need IEDriver. > npm install -g edgedriverįor Firefox, you'll need geckodriver. > npm install -g chromedriverįor Microsoft Edge, you'll need to be running on Windows, and you'll also need EdgeDriver. Chromeįor Chrome, you'll need ChromeDriver. You'll also need to have the browser installed on your machine. Each browser has its own which you can either download and add to your system path manually, or, you can use a package manager to install the latest version of the browser driver (recommended). Selenium communicates with each browser through a small binary application called a browser driver. If you want to run your tests locally there is some additional setup required for each browser. If so, see the Node installation documentation for package managers or download a Node installer for your operating system directly from the Node downloads page. NOTE: Your system configuration may differ from what's used in the sample above (e.g., Homebrew on MacOS).
#CAL CODERUNNER DRIVERS#
There's just the small matter of installing the Selenium IDE command line runner, getting the necessary browser drivers (if running your tests locally), and launching the runner from a command prompt with the options you want. You can now run all of your Selenium IDE tests on any browser, in parallel, and on a Grid without needing to write any code.