forked from SeleniumHQ/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
install.html
79 lines (64 loc) · 2.54 KB
/
install.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
<!doctype html>
<meta charset=utf-8>
<title>Installation</title>
<link rel=stylesheet href=se.css>
<link rel=prev href=intro.html title=Introduction>
<link rel=next href=start.html title="Getting Started">
<script src=docs.js></script>
<h1>Selenium Installation</h1>
<p>Selenium set up is quite different than other commercial tools.
You don’t install a tool using Selenium binaries
but set up your test automation project to use Selenium binary
in the language of your choice.
The Selenium binary you would need
depends on browsers you want to run your tests upon.
<h2>Using browser specific JAR</h2>
<p>If you want to run tests in only a specific browser
then you can add browser specific dependency in your <i>pom.xml</i> file.
You should add following dependency in your <i>pom.xml</i> file to run
tests only in Firefox:
<pre>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-firefox-driver</artifactId>
<version>2.53.1</version>
</dependency>
</pre>
<p>That's all and you are ready to driver your tests in Firefox.
In the similar manner, if you want to run tests only in Chrome
then you can use following dependency:
<pre>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-chrome-driver</artifactId>
<version>2.53.1</version>
</dependency>
</pre>
<h2>Using non browser specific JAR</h2>
<p>More often than not you would need to run test
on more than one browser.
Hence you would use <i>selenium-java</i>
Maven dependency in your project.
The <i>selenium-java</i> JAR
contains the language bindings and the drivers
and not the server side piece.
<pre>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>2.53.1</version>
</dependency>
</pre>
<h2>Using standalone JAR</h2>
<p>If you plan to use <a href=grid.html>Selenium Grid</a>
then you should download
<a href=https://www.seleniumhq.org/download/>selenium-server-standalone JAR</a> file.
<i>selenium-server-standalone</i> jar is never uploaded,
but all the components are available via
<a href=http://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-server/>selenium-server</a>
The standalone JAR contains everything,
including the remote Selenium server
and the client-side bindings.
Which means if you use selenium-server-standalone jar
in your project then you don't have to add selenium-java
or browser specific jar.