Please post your Web Driver questions in official Web Driver forum

Thursday, December 8, 2016

File upload and WebDriver (Where is my File?)

You may have come across file upload use case when working with WebDriver. File upload 
is quite easy since it is same as typing in a text box but herein we need to pass path of file
to be uploaded. I used to keep a static file in src/test/resources folder of maven project and 
would use it for upload operation. But you can also generate file during run time using 
java.nio.file.Files class.  Files class has createTempFile(java.lang.String, java.lang.String, java.nio.file.attribute.FileAttribute...) method which can be used to generate temporary files. For ex, you can generate a temporary pdf file and get back the File object as following - 

File file = Files.createTempFile("test-" + accountNumber, ".pdf").toFile();
generatePDF(file, StringUtils.repeat("Dummy PDF", 10));
And this is how generatePDF looks -
public static File generatePDF(File file, String content) {
    try {
        Document e = new Document();
        PdfWriter.getInstance(e, new FileOutputStream(file));
        e.open();
        e.add(new Paragraph(content));
        e.close();
        return file;
    } catch (FileNotFoundException | DocumentException var3) {
        throw new RuntimeException(var3);
    }
}

Now you can get absolute path of file and pass it to upload text box -  

getDriver.findElement(byLocator).sendKeys(file.getAbsolutePath());

Following this approach you don't have to keep a static file on my project.
So how do you handle file for file upload operation?

Thursday, December 1, 2016

Recording curl request with JMeter Recorder

Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with JMeter HTTP request
In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder.

If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder. 
Specify Global Setting > Port as 8090

If we were using browser to record web application then we would configure its proxy to 127.0.0.1 (Since http proxy server would work on localhost) and port 8090 -





Any way, we are not going to record browser actions but a curl request.

Under Test Plan element add Thread Group, Recording Controller and HTTP Request Default. Under HTTP Request Defaults mention Server IP as localhost” and port as 8090. This is to avoid duplication from HTTP Requests during recording. Recording Controller is where recorded samples would appear.

In the end Test Plan would looks as - 



To be able to record curl request on JMeter, we have to specify proxy server on curl using --proxy 127.0.0.1:8090 flag. The curl request looks as - 

curl -k --proxy 127.0.0.1:8090 -X POST --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' --header 'Authorization: bearer xxx' -F upload_file=@"/Users/tbhadauria/Documents/test.pdf"  'https://xxx'

Notice that I also added flag "k" to turn off curl's verification of certificate. Now hit the "Start" button on HTTPs Test Script Recorder and execute curl command. Following this you would find recorded elements under Recording Controller as following - 



I had already setup curl request on JMeter and comparing it to recorded elements I found that the only difference was the HTTP Request Implementation. I was using HTTP Request Implementation HTTPClient4 which would result in 400 error while recorded element had HTTP Request Implementation Java and it worked successfully. 

And this solved the issue of 400 error when uploading document using JMeter :) 

Monday, November 28, 2016

How to remove duplicate page object methods

You may come across situation when you find page object methods on various classes having similar operations. For ex in following example there are two different different methods doing almost same thing. Both methods get the count of ticket in opening and outgoing queue in a system. The only difference is the element locator. One method uses element locator openingTicketCount while other uses outgoingTicketCount -

public int getOpeningTicketCount() {
   final String count = fluent(openingTicketCount).getText();
   return count.length() == 0 ? 0 : Integer.valueOf(count);
}

public int getOutgoingTicketCount() {
   final String count = fluent(outgoingTicketCount).getText();
   return count.length() == 0 ? 0 : Integer.valueOf(count);
}

We can extract the common steps and create a new private method to encapsulate them - 

private int getTicketCount(By locator) {
   final String count = fluent(locator).getText();
   return count.length() == 0 ? 0 : Integer.valueOf(count);
}

And previous page object methods can call this method with required element locator - 

public int getOpeningTicketCount() {
   return getTicketCount(openingTicketCount);
}

public int getOutgoingTicketCount() {
   return getTicketCount(outgoingTicketCount);
}

What do you think of this approach? How would you handle duplicate element locators?
Fork me on GitHub