Installing Selenium for an enterprise environment is not trivial, involving:
Careful preparation will cut down the risk of expending a lot of time setting the environment up.
You'll need IT:AD:Java installed first:
You can check that it's correctly installed as follows: * IT:AD:Java:HowTo:Check that Java is correctly installed
You'll need a service account on each Hub Server of your Grid, eg: Svc_Selenium, or Svc_UXTests, as well as the Node servers.
Selenium can be installed either: * as a single instance, or * as a grid of Selenium installs (where you have a front Selenium instance you communicate with who in turn managers n instances of Selenium on other servers of various operating systems).
Bar the most trivial POC scenarios, in an enterprise environment where you'll need to test against various versions of a browsers that can't be installed side by side on the same browser (eg: IE), you'll need a Selenium Grid.
As it's the more complex scenario of the two, the following will concentrate on how to install a Grid.
To install a Grid, you'll need a Server box, and Hub boxes (one for Chrome, one for each version of IE (as it can't be installed side by side on the same machine).
A Node Selenium server can be installed on the same machine as the Hub Selenium Server – but not recommended (the machine on which the Selenium Hub Server is usually a Server OS, whereas, the Nodes are usually workstation OS's).
But it's also fine in most cases, as browsers are (in 99.99% of cases…) browsers – no matter what OS they are running on.
One Node Selenium server can manage more than one WebDriver.
You'll therefore need VMs built up that are suitable for the topology you've decided on. Ask your SysAdmin.
At the very least – to get started – you'll need a VM on which to install the Hub (and optionally webdrivers, as mentioned above).
Configuring Windows Service is difficult and opaque enough already, and even more so when trying to run Java based applications (Selenium's servers are Java based application).
Hence why we recommend you install IT:AD:NSSM (Non Sucking (Windows) Service Manager) on all the VMs, as per the instructions: Install
Normally, I would suggest referencing one copy of NSSM on your machine (eg: c:\Apps) but in this case I'll suggest you place a copy of NSSM in the Selenium directory.
The primary source packages can be downloaded from: * http://docs.seleniumhq.org/download/
http://selenium-release.storage.googleapis.com/index.htmlThere you'll see a tree of files to download:
As a “Microsoft Shop” you'll be most probably be wanting a combination of:
* FF and chrome, which you download separately In that case, you'll definitely need the Internet Explorer Server as part of your Grid:
The IE Server is tiny and is going to be one of the 'node's in your Grid. By default – like all nodes – starts on port 5555, but can be changed by starting it with -port=5556
As for testing Chrome. You'll need: *
You'll also need the WebDrivers for each browser.
* Firefox Driver
On the server:
On the Hub you'll be using to test Chrome, you'll need to:
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\Application\chrome.exeOn the Hub you'll be using to test a version of IE, you'll need: