Skip to main content

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?

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro