Step-1

Record your test case using the selenium IDE. I assume we all know how to record a test scenario using selenium IDE. Once recorded, export the test case as Java(JUnit)-Selenium RC and save it as a java file. You can do this by naming the file with a .java extension. I have saved my exported script as WarehouseLogin.java

Step-2

Open Eclipse and create a new java project and then add selenium client driver to the project. You can do this by right click on the project,

Properties>java build path>libraries>Add external jars

Search and find the selenium-java-client-driver.jar (which is at C:\selenium-remote-control-1.0.3\selenium-java-client-driver-1.0.1) and add the jar file.

Similarly add the junit libraries as well. To do this, Right click on the project, Properties>java build path>libraries>Add Library. Select junit and add it.

Step-3

create a package under the project. To do this right click on the project, new>package. Type the package name as com.examples.tests.

Now create a new class under this package with the name WarehouseLogin. To do this, right click on the package New>class; give the class name as WarehouseLogin and finish. Overwrite your newly created java class with the recorded selenium script.

Step-4

I modified the java class as given below to run it as java application. I will discuss how to run as a Junit test in my future post.

package com.example.tests;

//import the necessary packages and classes
import com.thoughtworks.selenium.*;
import java.util.regex.Pattern;
import com.example.tests.Server;

public class WarehouseLogin {

private Selenium selenium;
private final static String URL = “http://www.warehouse.co.uk”;

public void setup()throws Exception{
//I am using my startSeleniumServer()method which I wrote in Server class to start the selenium server. if you manually start the server, then you can comment the line
Server.startSeleniumServer();
selenium=new DefaultSelenium(“localhost”,4444,”*firefox”,URL);
selenium.start();
selenium.open(URL);
}

/**

*This method test whether a login is successfully with valid data

*/

public void testLogin() throws Exception{
selenium.open(“/”);
selenium.click(“headerMyAccount”);
selenium.waitForPageToLoad(“30000″);
selenium.type(“loginEmail”, “nadarajah.chenththuran@bt.com”);
selenium.type(“loginPassword”, “09101978″);
selenium.click(“//form[@id='loginForm']/fieldset/div[3]/input”);
selenium.waitForPageToLoad(“30000″);
System.out.println(“Login successfuly”);

}

/**

*This method test whether a logout is successful

*/
public void testLogout()throws Exception{
selenium.click(“//img[@alt='Log Out']“);
selenium.waitForPageToLoad(“30000″);
System.out.println(“Logout successful”);
}

public void stopServer(){
// I am using my stopSeleniumServer()method which I wrote in Server class to stop the server.
Server.stopSeleniumServer(selenium);
}

public static void main(String[] args){
try{
WarehouseLogin whl=new WarehouseLogin();

//new object is created and methods are called.
whl.setup();
whl.testLogin();
whl.testLogout();
whl.stopServer();
}catch(Exception e){
System.err.println(e);
}
}
}

I believe this will help those who wish to know how to export and use selenium with their language of choice.

We can use JUnit with Selenium which I will discuss in my future posts.

Muhammad Usman has already raised this question in linked in. “What will be the appropriate answer of the question from management why this bug was not captured before?” As I am also quite familiar with this question, I thought to write what I think can be the reasons.

When I was working in Pandora Inc, I was asked  a similar question by Linda, my project manager for a particular functionality, I was so sure that I tested that functionality during the system testing and then in regression testing as well. The defect was found after a data migration from live database which was after the UAT. As we do not run the regression test cases after the UAT, we did not test this functionality after the data migration. PM asked “why was this not captured before”. I told that it was not captured before because it was not an issue before the data migration. Then she asked “are you sure you tested this before and do you have the template” Unfortunately I missed that test result template for that functionality. Even though I explained to the PM that there was no defect during the regression testing and the UAT, she was understandably upset.

Linda threw the same query again in another project where I did not even know that there was such a requirement. The defect was identified by the client. Once Linda saw the defect report, she came straight towards me and asked the same so called question “Why was this not captured before”. I told her that it was not captured before because I did not know it was an issue because I did not know it did not meet the requirement because I did not know such a requirement because it was documented nowhere.

There was another situation where I captured an issue while doing a system testing. That issue was fixed and retested and then closed by me. The issue did not happen during the regression testing cycle. But regressed during the UAT. Samuel  did not know this issue was already logged and retested. She asked “why was this not found before”. I proved her that it was tested before by showing the issue number. When I did a root cause analysis, I found that the developers did some code change in between the regression test cycle and the UAT which caused the issue.

I agree that we testers miss some defects due to many reasons such as pressures due to crazy dead lines, poor requirements, lack of domain knowledge and so forth. At the same time PMs should understand that there are high chances for an issue to be regressed at any stage due to last minute code fixes, configurations, migrations and so forth.  They have to find out the root cause without simply blaming the testers.

First of all PMs should appreciate the testers as the defect was found before live. Only testers can not be responsible when a defect is found at last minute. It’s a team problem and we as a team should diagnose and resolve it. As Shrini commented “What would a police say if he is asked why a certain robbery was not prevented?” Police can only help to reduce the level of robbery, but can’t stop all. We testers also are same as Police officers.



Note: I have taken the opportunity to use one of  my My dream company name and project manager to discuss the subject line.