Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ardesco/selenium-maven-template
A maven template for Selenium that will let you check out and go.
https://github.com/ardesco/selenium-maven-template
java maven selenium selenium-webdriver template webdriver
Last synced: about 3 hours ago
JSON representation
A maven template for Selenium that will let you check out and go.
- Host: GitHub
- URL: https://github.com/ardesco/selenium-maven-template
- Owner: Ardesco
- Created: 2012-04-19T20:58:54.000Z (over 12 years ago)
- Default Branch: master
- Last Pushed: 2023-05-09T18:57:21.000Z (over 1 year ago)
- Last Synced: 2024-09-24T01:06:27.383Z (about 17 hours ago)
- Topics: java, maven, selenium, selenium-webdriver, template, webdriver
- Language: Java
- Size: 165 KB
- Stars: 461
- Watchers: 83
- Forks: 566
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
Awesome Lists containing this project
README
Selenium-Maven-Template
=======================
[](https://gitter.im/Ardesco/Selenium-Maven-Template?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
A maven template for Selenium 4 that has the latest dependencies so that you can just check out and start writing tests in four easy steps. If you like what you see have a look at
my Selenium book [Mastering Selenium Webdriver](https://www.amazon.co.uk/Mastering-Selenium-WebDriver-Mark-Collin/dp/1784394351).
1. Open a terminal window/command prompt
2. Clone this project.
3. `cd Selenium-Maven-Template` (Or whatever folder you cloned it into)
4. `mvn clean verify`
All dependencies should now be downloaded and the example google cheese test will have run successfully in headless mode (Assuming you have Firefox installed in the default
location)
### What should I know?
- To run any unit tests that test your Selenium framework you just need to ensure that all unit test file names end, or start with "test" and they will be run as part of the build.
- The maven failsafe plugin has been used to create a profile with the id "selenium-tests". This is active by default, but if you want to perform a build without running your
selenium tests you can disable it using:
```shell
mvn clean verify -P-selenium-tests
```
- The maven-failsafe-plugin will pick up any files that end in IT by default. You can customise this is you would prefer to use a custom identifier for your Selenium tests.
### Known problems...
- It looks like SafariDriver is no longer playing nicely and we are waiting on Apple to fix it... Running safari driver locally in server mode and connecting to it like a grid
seems to be the workaround.
### Anything else?
Yes you can specify which browser to use by using one of the following on the command line:
- `-Dbrowser=firefox`
- `-Dbrowser=chrome`
- `-Dbrowser=ie`
- `-Dbrowser=edge`
- `-Dbrowser=opera`
- `-Dbrowser=brave`
If you want to toggle the use of chrome or firefox in headless mode set the headless flag (by default the headless flag is set to true)
- `-Dheadless=true`
- `-Dheadless=false`
You don't need to worry about downloading the IEDriverServer, EdgeDriver, ChromeDriver , OperaChromiumDriver, or GeckoDriver binaries, this project will do that for you
automatically.
You can specify a grid to connect to where you can choose your browser, browser version and platform:
- `-Dremote=true`
- `-DseleniumGridURL=http://{username}:{accessKey}@ondemand.saucelabs.com:80/wd/hub`
- `-Dplatform=xp`
- `-Dbrowser=firefox`
- `-DbrowserVersion=44`
You can even specify multiple threads (you can do it on a grid as well!):
- `-Dthreads=2`
You can also specify a proxy to use
- `-DproxyEnabled=true`
- `-DproxyHost=localhost`
- `-DproxyPort=8080`
- `-DproxyUsername=fred`
- `-DproxyPassword=Password123`
If the tests fail screenshots will be saved in `${project.basedir}/target/screenshots`
If you need to force a binary overwrite you can do:
- `-Doverwrite.binaries=true`
### It's not working!!!
You have probably got outdated driver binaries, by default they are not overwritten if they already exist to speed things up. You have two options:
- `mvn clean verify -Doverwrite.binaries=true`
- Delete the `selenium_standalone_binaries` folder in your resources directory
### Brave fails when in headless mode
Currently, Brave seems to be a bit flaky when running in headless mode, I would suggest running with `-Dheadless=false`
### It's looking for the Brave binary in the wrong location
You probably don't have the brave binary installed in one of the default locations that this codebase is expecting. That's OK though, you can specify it by seeting the following system property:
- `-DbraveBinaryLocation=/path/to/brave-browser`