automationbydebasish: May 2014

Thursday 29 May 2014

How to extract text from PDF Using Apache Tika Library In Java

import java.io.FileInputStream;
import java.io.InputStream;

import org.apache.tika.parser.pdf.PDFParser;
import org.apache.tika.metadata.Metadata;
import org.apache.tika.parser.ParseContext;
import org.apache.tika.sax.BodyContentHandler;
import org.xml.sax.ContentHandler;

public class ParsePDFWithTika {
  public static void main(String args[]) throws Exception {

    InputStream is = null;
    try {
      is = new FileInputStream("C:/Temp/realhowto-vbs-20121221.pdf");
      ContentHandler contenthandler = new BodyContentHandler();
      Metadata metadata = new Metadata();
      PDFParser pdfparser = new PDFParser();
      pdfparser.parse(is, contenthandler, metadata, new ParseContext());
      System.out.println(contenthandler.toString());
    }
    catch (Exception e) {
      e.printStackTrace();
    }
    finally {
        if (is != null) is.close();
    }
  }
}

Tuesday 27 May 2014

Integration Of ReportNG With TestNG

ReportNG is third party reporting tool which can be plugged in with TestNG as listener.

ReportNG can be downloaded from http://reportng.uncommons.org/.

From this site, 2 jars are to be downloaded for use:
1. reportng-1.1.4.jar
2. velocity-dep-1.4

But, to run with testng-6.8.jar, those jar needs class "com.google.inject", which can be found in guice.jar.
This can be downloaded from https://code.google.com/p/google-guice/wiki/Guice40.

All 3 jars need to be in classpath. In below target "runTestNGTestCase, classpathref points to classpath which includes all classfiles and jars".

listeners attribute should be added with classnames separated by comma.
listeners="org.uncommons.reportng.HTMLReporter,org.uncommons.reportng.JUnitXMLReporter">
So, target for running testNG with reportNG should look like as below:

<target name="runTestNGTestCase">
<testng classpathref="classes.test.location" outputDir="test-output" useDefaultListeners="true" listeners="org.uncommons.reportng.HTMLReporter,org.uncommons.reportng.JUnitXMLReporter">
<classfileset dir="bin" includes="**/TestFlipKarHomePage.class" />
<sysproperty key="org.uncommons.reportng.title" value="My Test Report"/>
</testng>
</target>

Monday 26 May 2014

Working Example Of DragAndDrop Using WebDriver

WebDriver uses Actions class to drag and drop.
Actions class is found in package org.openqa.selenium.interactions

There are 2 methods related to drag and drop:
1. dragAndDropBy(WebElement elment,int x, int y)
//This will drag WebElement element to location is defined by x and y coordinate.
2. dragAndDrop(WebElement a, WebElement b)
//This will drag WebElement a and drop to WebElement b

Working Example:

// Initializing FirefoxDriver
WebDriver driver = new FirefoxDriver();
/* Loading the site on which we need to perform the
drag and drop action.*/
driver.get("http://jqueryui.com/droppable/");
driver.manage().window().maximize();
// Waiting for element to load
Thread.sleep(5000);
/* Drag and drop features are usually part of the iframes.
So we first need to switch to the iframe so that selenium
can locate the web element.*/
List<WebElement> frames=driver.findElements(By.tagName("iframe"));

driver.switchTo().frame(frames.get(0));
//WebElement box = driver.findElement(By.xpath("html/body/div[1]"));
WebElement box = driver.findElement(By.id("draggable"));

/* Creating the object of Actions class and passing the
driver to it. It should be noted that Actions(WebDriver driver)
is an argument constructor which take driver as argument.*/
Actions act = new Actions(driver);
act.dragAndDrop(box, driver.findElement(By.id("droppable"))).build().perform();
driver.switchTo().defaultContent();
driver.close();

How to call testNG using Ant

Saturday 17 May 2014

How To Search Text On XML, Ignoring Case

Lets take example:
XML:
<Names>
<Name>Debasish</Name>
<Name>Subhasish</Name>
</Names>

What would be xpath to search Node with text "Debasish".
The xpath=//Name[contains(text(),'Debasish')].
The outcome=Element='<Name>Debasish</Name>'

Lets see the outcome when xpath=//Name[contains(text(),'debasish')].
There is no match. (I have used online tool http://www.freeformatter.com/).

Now, what can i do to search text irrespective of its case.
One general solution, we normally use in programming is to either convert text to lower case or upper case and then compare.
Here, in case of xpath, we will do same.
The xpath would be: //Name[contains(lower-case(text()),'debasish')]
The outcome=Element='<Name>Debasish</Name>'

XML And XPath...Is XML Case Sensitive

Lets See What Is DOM.
DOM stands for document object model which is interpreted by browser and presents the DOM in better human understandable html format. DOM is hierarchy structure of webelements.

Lets see simple DOM presented in html format.

<html><head><body><tr><td><input type="text" value="Debasish" /></td><td><input type="text" value="Subhasish" /></td></tr></body></head></html>.

If you see above html, it will look like XML. Only difference between html and XML is html has fixed set of tags and tags are not case sensitive. Does not matter, if one writes "tr" or "Tr" or "TR". Its all same for html. But, XML tags are case sensitive. So, in general, XML does have user defined tags which is case sensitive(CASE SENSITIVE) where as html tags are not case sensitive(CASE INSENSITIVE).

Impact Of XPath On:

DOM: outcome of //input is same as //Input. The output is same as //INPUT. So, xpath in case of DOM is not case sensitive. But, attriubtes such as id,name are case sensitive.
XPath Operators Are Case Sensitive:
But, xpath operators are case sensitive.
Ex: In above case, what will be xpath to look for inputbox with value=Debasish. The xpath would be as shown below.
//Input[contains(@value,'Debasish')]
As shown above. "contains" is the operator which searches for Input box with value="Debasish".
If "contains" is written as "Contains"(capital C), it will search nothing. Rather, it will syntax error.
So, it confirms xpath operators are case sensitive.

XML: <Names><Name>Debasish</Name><Name>Subhasish</Name></Names>
<Name> is not same as <name>. <Name> is different node and <name> is different node.
outcome of xpath=//Name will return two nodes/Elements
<Name>Debasish</Name>
<Name>Subhasish</Name>

If XML is: <Names><Name>Debasish</Name><name>Subhasish</name></Names>
outcome of xpath=//Name will return one node/Element
<Name>Debasish</Name>
outcome of xpath=//name will return one node/Element
<name>Subhasish</name>

This confirms, XML is case sensitive. So, as xpath on those xmls.

Junit Vs TestNG

Here I did a feature comparison between JUnit 4 and TestNG.

1. Annotation Support

The annotation supports are implemented in both JUnit 4 and TestNG look similar.

Feature	JUnit 4	TestNG
test annotation	@Test	@Test
run before all tests in this suite have run	–	@BeforeSuite
run after all tests in this suite have run	–	@AfterSuite
run before the test	–	@BeforeTest
run after the test	–	@AfterTest
run before the first test method that belongs to any of these groups is invoked	–	@BeforeGroups
run after the last test method that belongs to any of these groups is invoked	–	@AfterGroups
run before the first test method in the current class is invoked	@BeforeClass	@BeforeClass
run after all the test methods in the current class have been run	@AfterClass	@AfterClass
run before each test method	@Before	@BeforeMethod
run after each test method	@After	@AfterMethod
ignore test	@ignore	@Test(enbale=false)
expected exception	@Test(expected = ArithmeticException.class)	@Test(expectedExceptions = ArithmeticException.class)
timeout	@Test(timeout = 1000)	@Test(timeout = 1000)

The main annotation differences between JUnit4 and TestNG are

1. In JUnit 4, we have to declare “@BeforeClass” and “@AfterClass” method as static method. TestNG is more flexible in method declaration, it does not have this constraints.

2. 3 additional setUp/tearDown level: suite and group (@Before/AfterSuite, @Before/AfterTest, @Before/AfterGroup). See more detail here.

JUnit 4

    @BeforeClass
    public static void oneTimeSetUp() {
        // one-time initialization code   
     System.out.println("@BeforeClass - oneTimeSetUp");
    }

TestNG

    @BeforeClass
    public void oneTimeSetUp() {
        // one-time initialization code   
     System.out.println("@BeforeClass - oneTimeSetUp");
}

In JUnit 4, the annotation naming convention is a bit confusing, e.g “Before”, “After” and “Expected”, we do not really understand what is “Before” and “After” do, and what we “Expected” from test method? TestiNG is easier to understand, it uses “BeforeMethod”, “AfterMethod” and “ExpectedException” instead.

2. Exception Test

The “exception testing” means what exception throws from the unit test, this feature is implemented in both JUnit 4 and TestNG.

JUnit 4

      @Test(expected = ArithmeticException.class)  
 public void divisionWithException() {  
   int i = 1/0;
 }

TestNG

      @Test(expectedExceptions = ArithmeticException.class)  
 public void divisionWithException() {  
   int i = 1/0;
 }

3. Ignore Test

The “Ignored” means whether it should ignore the unit test, this feature is implemented in both JUnit 4 and TestNG .

JUnit 4

        @Ignore("Not Ready to Run")  
 @Test
 public void divisionWithException() {  
   System.out.println("Method is not ready yet");
 }

TestNG

 @Test(enabled=false)
 public void divisionWithException() {  
   System.out.println("Method is not ready yet");
 }

4. Time Test

The “Time Test” means if an unit test takes longer than the specified number of milliseconds to run, the test will terminated and mark as fails, this feature is implemented in both JUnit 4 and TestNG .

JUnit 4

        @Test(timeout = 1000)  
 public void infinity() {  
  while (true);  
 }

TestNG

 @Test(timeOut = 1000)  
 public void infinity() {  
  while (true);  
 }

5. Suite Test

The “Suite Test” means bundle a few unit test and run it together. This feature is implemented in both JUnit 4 and TestNG. However both are using very different method to implement it.

JUnit 4

The “@RunWith” and “@Suite” are use to run the suite test. The below class means both unit test “JunitTest1” and “JunitTest2” run together after JunitTest5 executed. All the declaration is define inside the class.

@RunWith(Suite.class)
@Suite.SuiteClasses({
        JunitTest1.class,
        JunitTest2.class
})
public class JunitTest5 {
}

TestNG

XML file is use to run the suite test. The below XML file means both unit test “TestNGTest1” and “TestNGTest2” will run it together.

<!DOCTYPE suite SYSTEM "http://beust.com/testng/testng-1.0.dtd" >
<suite name="My test suite">
  <test name="testing">
    <classes>
       <class name="com.fsecure.demo.testng.TestNGTest1" />
       <class name="com.fsecure.demo.testng.TestNGTest2" />
    </classes>
  </test>
</suite>

TestNG can do more than bundle class testing, it can bundle method testing as well. With TestNG unique “Grouping” concept, every method is tie to a group, it can categorize tests according to features. For example,

Here is a class with four methods, three groups (method1, method2 and method3)

        @Test(groups="method1")
 public void testingMethod1() {  
   System.out.println("Method - testingMethod1()");
 }  
 
 @Test(groups="method2")
 public void testingMethod2() {  
  System.out.println("Method - testingMethod2()");
 }  
 
 @Test(groups="method1")
 public void testingMethod1_1() {  
  System.out.println("Method - testingMethod1_1()");
 }  
 
 @Test(groups="method4")
 public void testingMethod4() {  
  System.out.println("Method - testingMethod4()");
 }

With the following XML file, we can execute the unit test with group “method1” only.

<!DOCTYPE suite SYSTEM "http://beust.com/testng/testng-1.0.dtd" >
<suite name="My test suite">
  <test name="testing">
   <groups>
      <run>
        <include name="method1"/>
      </run>
    </groups>
    <classes>
       <class name="com.fsecure.demo.testng.TestNGTest5_2_0" />
    </classes>
  </test>
</suite>

With “Grouping” test concept, the integration test possibility is unlimited. For example, we can only test the “DatabaseFuntion” group from all of the unit test classes.

6. Parameterized Test

The “Parameterized Test” means vary parameter value for unit test. This feature is implemented in both JUnit 4 and TestNG. However both are using very different method to implement it.

JUnit 4

The “@RunWith” and “@Parameter” is use to provide parameter value for unit test, @Parameters have to return List[], and the parameter will pass into class constructor as argument.

@RunWith(value = Parameterized.class)
public class JunitTest6 {
 
  private int number;
 
  public JunitTest6(int number) {
     this.number = number;
  }
 
  @Parameters
  public static Collection<Object[]> data() {
    Object[][] data = new Object[][] { { 1 }, { 2 }, { 3 }, { 4 } };
    return Arrays.asList(data);
  }
 
  @Test
  public void pushTest() {
    System.out.println("Parameterized Number is : " + number);
  }
}

It has many limitations here; we have to follow the “JUnit” way to declare the parameter, and the parameter has to pass into constructor in order to initialize the class member as parameter value for testing. The return type of parameter class is “List []”, data has been limited to String or a primitive value for testing.

TestNG

XML file or “@DataProvider” is use to provide vary parameter for testing.

XML file for parameterized test.
Only “@Parameters” declares in method which needs parameter for testing, the parametric data will provide in TestNG’s XML configuration files. By doing this, we can reuse a single test case with different data sets and even get different results. In addition, even end user, QA or QE can provide their own data in XML file for testing.

Unit Test

      public class TestNGTest6_1_0 {
 
    @Test
    @Parameters(value="number")
    public void parameterIntTest(int number) {
       System.out.println("Parameterized Number is : " + number);
    }
 
      }

XML File

<!DOCTYPE suite SYSTEM "http://beust.com/testng/testng-1.0.dtd" >
<suite name="My test suite">
  <test name="testing">
 
    <parameter name="number" value="2"/>  
 
    <classes>
       <class name="com.fsecure.demo.testng.TestNGTest6_0" />
    </classes>
  </test>
</suite>

@DataProvider for parameterized test.

While pulling data values into an XML file can be quite handy, tests occasionally require complex types, which can’t be represented as a String or a primitive value. TestNG handles this scenario with its @DataProvider annotation, which facilitates the mapping of complex parameter types to a test method.

@DataProvider for Vector, String or Integer as parameter

        @Test(dataProvider = "Data-Provider-Function")
 public void parameterIntTest(Class clzz, String[] number) {
    System.out.println("Parameterized Number is : " + number[0]);
    System.out.println("Parameterized Number is : " + number[1]);
 }
 
 //This function will provide the patameter data
 @DataProvider(name = "Data-Provider-Function")
 public Object[][] parameterIntTestProvider() {
  return new Object[][]{
       {Vector.class, new String[] {"java.util.AbstractList", 
"java.util.AbstractCollection"}},
       {String.class, new String[] {"1", "2"}},
       {Integer.class, new String[] {"1", "2"}}
      };
 }

@DataProvider for object as parameter
P.S “TestNGTest6_3_0” is an simple object with just get set method for demo.

        @Test(dataProvider = "Data-Provider-Function")
 public void parameterIntTest(TestNGTest6_3_0 clzz) {
    System.out.println("Parameterized Number is : " + clzz.getMsg());
    System.out.println("Parameterized Number is : " + clzz.getNumber());
 }
 
 //This function will provide the patameter data
 @DataProvider(name = "Data-Provider-Function")
 public Object[][] parameterIntTestProvider() {
 
  TestNGTest6_3_0 obj = new TestNGTest6_3_0();
  obj.setMsg("Hello");
  obj.setNumber(123);
 
  return new Object[][]{
       {obj}
  };
 }

TestNG’s parameterized test is very user friendly and flexible (either in XML file or inside the class). It can support many complex data type as parameter value and the possibility is unlimited. As example above, we even can pass in our own object (TestNGTest6_3_0) for parameterized test

7. Dependency Test

The “Parameterized Test” means methods are test base on dependency, which will execute before a desired method. If the dependent method fails, then all subsequent tests will be skipped, not marked as failed.

JUnit 4

JUnit framework is focus on test isolation; it did not support this feature at the moment.

TestNG

It use “dependOnMethods “ to implement the dependency testing as following

        @Test
 public void method1() {
    System.out.println("This is method 1");
 }
 
 @Test(dependsOnMethods={"method1"})
 public void method2() {
  System.out.println("This is method 2");
 }

The “method2()” will execute only if “method1()” is run successfully, else “method2()” will skip the test.

Conclusion

After go thought all the features comparison, i suggest to use TestNG as core unit test framework for Java project, because TestNG is more advance in parameterize testing, dependency testing and suite testing (Grouping concept). TestNG is meant for high-level testing and complex integration test. Its flexibility is especially useful with large test suites. In addition, TestNG also cover the entire core JUnit4 functionality. It’s just no reason for me to use JUnit anymore.

1. @test annotation can take dependsOnMethods,dependsOnGroups. This causes dependent method is called first, then test method is called.
Example:
@test
public void test1()
{
}
public void test2(dependsOnMethods test1)
{
}
This will cause test2 to follow after test1. If test1 fails, then test2 will skip.
@test
public void test3(groups={sanity})
{
}
public void test4(dependsOnMethods test3)
{
}
if test 3 fails, then test4 will skip

2. DataProvider which is used for parameterization, is easy to configure. Junit implementation is bit complex.

Tuesday 13 May 2014

Limitation of Using @FindBy Annotation In PageFactory And How to overcome it

Example Of PageFactory:
import org.openqa.selenium.WebDriver
import org.openqa.selenium.WebElement
import org.openqa.selenium.support.PageFactory

////PageLogin.java
public class PageLogin
{
@FindBy(id="userName")
private WebElement PageLogin_txtUserName;
@FindBy(id="password")
private WebElement PageLogin_txtPassword;
@FindBy(id="btnSubmit")
private WebElement PageLogin_btnSubmit;

//instance initialization block
{
//pseudo singleton method to retrieve WebDriver Instance
WebDriver wd=WebDriverInstance.getWebDriverInstance();
wd.get("http://localhost:8080/Project/login.html);
PageFactory.initElements(wd,this);
}
//instance initialization block ends
public String doLogin(String userName,String password)
{
PageLogin_txtUserName.sendKeys(userName);
PageLogin_txtPassword.sendKeys(password);
PageLogin_btnSubmit.click();

return WebDriverInstance.getWebDriverInstance().getTitle();

}

}
//class definition PageLogin.java ends
////testLogin.java
PageLogin login=new PageLogin();
login.doLogin("A","B"); //#1
login.doLogin("C","D"); //#2
In step #1 and #2, driver will look for userName and password every time on page, when ever we call login.doLogin, which will degrade the performance.
The solution should be once userName/password is found/located, it should be stored in memory.
PageFactory provides this solution. @CacheLookup is solution.
So, above code can be enhanced to
@FindBy(id="userName")
@CacheLookup
private WebElement PageLogin_txtUserName;
@FindBy(id="password")
@CacheLookup
private WebElement PageLogin_txtPassword;
@FindBy(id="btnSubmit")
@CacheLookup
private WebElement PageLogin_btnSubmit;

This will result locators(Referred WebElements) to be cached.

Sunday 11 May 2014

What is difference between textToBePresentInElement(locator,String) vs textToBePresentInElementValue(locator,String) in WebDriver

WebDriver provides implicit wait and explicit wait. In explicit wait also, we can use predefined wait conditions and we can create our own conditions using anonymous class and implementing apply method.

So, now textToBePresentInElement(locator,String) and textToBePresentInElementValue(locator,String) are predefined by ExpectedCondition which is used to set explicit wait.

So, we can use :
WebDriverWait wait=new WebDriverWait(driver,10);
//create WebDriverWait instance with parameters passed - 1. WebDriver instance, 2. maximum wait in case ExpectedCondition fails.
wait.until(ExpectedCondition.textToBePresentInElement(By,"Looking4TextOnElement");//This verifies if text is present on element By.
wait.until(ExpectedCondition.textToBePresentInElementValue(By,"Looking4TextOnValueAttribute");//This verifies if text is present in value attribute of element By.

How To Call JMeter Using Ant

Custom task to be created using taskdef. taskdef is meant to add custom tasks which in not inbuilt provided by ant. The tool has to provide class with task which can be integrated with ant.

<taskdef
name="jmeter"
classname="org.programmerplanet.ant.taskdefs.jmeter.JMeterTask"/>

Once task in name of jmeter is created which is mapped to class name "org.programmerplanet.ant.taskdefs.jmeter.JMeterTask", then jmeter can be used with ant.

To execute jmeter script "jmx" file and specify output log "jtl" file and to pass other arguments to jmeter, we can use following approach.

<jmeter
jmeterhome="c:\jakarta-jmeter-1.8.1"
testplan="${basedir}/loadtests/JMeterLoadTest.jmx"
resultlog="${basedir}/loadtests/JMeterResults.jtl">
<jvmarg value="-Xincgc"/>
<jvmarg value="-Xmx128m"/>
<jvmarg value="-Dproperty=value"/>

</jmeter>