Selenium Page Objects

Have been reading about page objects in selenium of late and came across a couple of pointers which I wanted to share here -

1. If user action causes ctrl to appear on a different page then that corresponding page object should be returned else same page object should be returned.

2. Test code (Verification/Assertion) should be included in test and should not be part of page Objects them selves

3. Page object need not represent entire page, it may represent part of page which may appear on site multiple times or multiple times on same page.

4. Page Object offers the services represented by that page.

Reference:
http://www.slideshare.net/dantebriones/using-the-page-object-pattern
http://www.theautomatedtester.co.uk/tutorials/selenium/page-object-pattern.htm
http://code.google.com/p/selenium/wiki/PageObjects

of late contributed an article on Page Object on Selenium Head Quarter. It could be found here.

Comments

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 ; } }

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

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

No Automated Testing

Search This Blog