https://github.com/tsundberg/selenium-test-automation-ci

A sample project that shows how Selenium tests can be executed on a ci server and Saucelabs
https://github.com/tsundberg/selenium-test-automation-ci

Last synced: 7 days ago
JSON representation

A sample project that shows how Selenium tests can be executed on a ci server and Saucelabs

• Host: GitHub
• URL: https://github.com/tsundberg/selenium-test-automation-ci
• Owner: tsundberg
• Created: 2015-07-20T10:07:43.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2016-01-27T18:37:37.000Z (almost 9 years ago)
• Last Synced: 2024-04-24T12:01:22.884Z (7 months ago)
• Language: Java
• Homepage:
• Size: 54.7 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# selenium-test-automation-ci

## Running from a command line

Executing a build on a CI server is the same as running the build from a

command line prompt.

The most important difference is that the execution is triggered on a change

in the version control system and executed on another machine.

This means that an execution will always be done. Any mistakes that prevents

the build to succeeds will be caught. Any tweaks done on the developers host

will not be available and the comment it works on my machine is invalid.

This project is executed fro a prompt using the command

```

./gradlew clean build

```

## Running from a CI server

Setting up a CI server is done using these steps:

* Download Jenkins from [http://jenkins-ci.org/](http://jenkins-ci.org/)

* Move the downloaded war a directory where it can live and be executed

* Start Jenkins with `java -jar jenkins.war`

* Access Jenkins on [http://localhost:8080/](http://localhost:8080/)

* Install the Git plugin

  * Manage Jenkins

  * Manage plugins

   Select Updates

    * Update the JUnit plugin

  * Select Available

    * Select and install: GIT plugin

    * Select and install: Gradle plugin

  * Restart Jenkins

* Create a new job

  * Call it Cross browse`

  * Use the type - Freestyle project

  * Ok

  * Set Source Code Management to Git

  * Add the url `[email protected]:tsundberg/selenium-test-automation-ci.git`

  * Build Triggers - Poll SCM

  * Set the schedule to '* * * * *' - i.e. poll every minute

  * Add a build step - Invoke Gradle script

    * Use Gradle Wrapper

    * Tasks: clean build

  * Post-build Actions

    * Publish JUnit test result report

    * Test report XMLs - `**/TEST*.xml`

    * Save

* Execute the build immediately - Build Now

Any changes done to the project will now be picked up and executed.