How to get Selenium/WebDriver tests running on Jen

Question

I am very new to Selenium and Automation. Using Selenium IDE and my general knowledge of Java I was able to make a series of test cases in Eclipse that run on JUnit. Now my test currently run when I am in eclipse and press [run]. I would like to import these test cases to Jenkins/Hudson. There are two ways I would prefer doing the CI.

1. Schedule a time (once per week) to run through the tests and send email of result.

2. Upload my test cases to a repository on GitHub and when there is a change done to the repository, run the tests and/or on a schedule (once per week).

Ive honestly tried to look up tutorials (videos/documents) but they all seem very unclear. Just to give an example, I do not know what a build.xml or POM is.

Is it better to do this with a Jenkins Plugin or using ANT or Maven? If so what are the things I need to add/change in my code to allow this to happen, and configure in Jenkins.

My Example Code is Below:

package Profile;

import java.util.concurrent.TimeUnit;
import java.util.regex.Pattern;
import java.util.concurrent.TimeUnit;
import org.junit.*;
import static org.junit.Assert.*;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.interactions.Actions;
import org.openqa.selenium.support.ui.Select;
import com.opera.core.systems.scope.protos.ExecProtos.ActionList.Action;

public class P_ProfileChangeTestCase {
  private WebDriver driver;
  private String baseUrl;
  private StringBuffer verificationErrors = new StringBuffer();

//Before the test begins, creates a new webdriver and sets the base url
  @Before
  public void setUp() throws Exception {
    driver = new FirefoxDriver();
    baseUrl = "http://www.test.com/";
    driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

  }

  @Test
  public void testOpen() throws Exception {
    System.out.println("**Starting Profile**");
    driver.get(baseUrl);
//Click LogIn
System.out.println("Clicking Log In");
driver.findElement(By.cssSelector("div.button.login > a.link")).click();
//Enter User name
System.out.println("Entering Username");
driver.findElement(By.xpath("//input[@id='login']")).sendKeys("TEST");
//Enter Password
System.out.println("Entering Password");
driver.findElement(By.xpath("//input[@id='login_password']")).sendKeys("PW");
//Click LogIn Button
System.out.println("Submit Log In");
driver.findElement(By.className("login-button")).click();
//Verify user name login by echo name to console
System.out.println("Verify User Log In");
String text = driver.findElement(By.cssSelector("span.username")).getText();
System.out.println("Username is :" + text);
////////////////////////
//Click on Edit Profile
System.out.println("Clicking on Edit Profile Button");
driver.findElement(By.cssSelector("div.button.login")).click();
driver.findElement(By.xpath("//div[@id='mlg-header']/div/div[3]/div/div[7]/div/div[2]/a")).click();
//Change description in profile
System.out.println("Editing the Interests section of profile");
driver.findElement(By.name("interests")).clear();
driver.findElement(By.name("interests")).sendKeys("Edit Profile in Selenium Eclipse");
//Update Profile
System.out.println("Click on submit to change profile");
driver.findElement(By.cssSelector("input[type=\"submit\"]")).click();
//Verify that update has been applied to profile
System.out.println("Verifing that change has been made");
assertEquals("Profile has been updated.", driver.findElement(By.cssSelector("b > b")).getText());
//Console Output of Assert Statement Above
System.out.println("Profile has been updated!");
System.out.println("**Profile Complete!**");

  }

  @After
  public void tearDown() throws Exception {
driver.quit();
String verificationErrorString = verificationErrors.toString();
if (!"".equals(verificationErrorString)) {
  fail(verificationErrorString);
    }
  }
  private boolean isAlertPresent() {
    try {
      driver.switchTo().alert();
      return true;
    } catch (NoAlertPresentException e) {
      return false;
    }
      }
}

Answer 1

Based on your information, you create your selenium automation using maven project base. In this case, if you want to use Jenkins as your CI, here is the steps :

1. Make sure you have already installed maven and set up the maven home in your system.
2. Create new item with Build a free-style software project.
3. Go to the .jenkins folder in your system. If you are using mac, it'll be placed inside home. Copy and paste your selenium project inside the Automation job folder (.jenkins/jobs/Automation/workspace). The workspace folder should be created manually.
4. After creating the job/project, go to the Source Code Management and set it as none (I assume currently you are using your selenium code from your local system). If you want to grab the code from git repository, you need to add the git plugin first : Jenkins -> Manage Jenkins -> Manage Plugins -> click on Available tab -> search for Github Plugin.
5. Check the Build Periodically under Build Triggers part and set it to (0 7 * * *). It means your automation will automatically be run at 7 everyday.
6. Add build to run your automation through maven command mvn clean test. Please choose Execute Shell if you use mac/linux, or choose Execute Windows Batch Command if you use Windows system.
7. If you want to send the email of the automation result, you need to install the Email Ext Plugin in Jenkins-Manage Plugin and set up the Editable Email Notification. If you have the attachment, the maven project result usually placed under the target folder. Below I give you example of zip file that I have in target folder.
8. Save your jenkins/project.
9. Set up the email sender : Go to Jenkins -> Manage Jenkins -> Configure System and follow the steps attached below.
10. Finally, build your jenkins project/job :
11. Let me know if you still have any issue ;)

Answer 2

Based on the posted code and the fact that you are using Maven, I'd say "mvn clean test" will run all the unit tests. So create a meven project in Jenkins (for that you'll need maven plugin in Jenkins) and in the configuration provide "clean test" as your maven goals to be executed by the jenkins' project.

Looking at the bigger picture here, although your tests are annotated as unit tests, but they don't possess the characteristics of unit tests. For one, unit tests should Mock external dependencies.