Skip to main content

Parameters used in Selenium Tests Framework

Following parameters can be set up in testng.xml file to make most use of Selenium Tests Framework. These parameters are already set in Sample Test Project -

  • There are two listeners available with Selenium Tests Framework - 
com.seleniumtests.reporter.SeleniumTestsReporter - controls the generation of step by step reporting 
and com.seleniumtests.core.TestRetryListener - reruns the failed test

If you don't wish to use any of these features then you can remove the listeners (you don't want to do that ;-))
  • appURL - Application URL against which tests is to be run
  • browser - Browser on which application is to be tested, available options are *firefox, *chrome, *iexplore
  • runMode - The mode in which tests are to be run either locally or on selenium grid. Corresponding configurations are - LOCAL or ExistingGrid
  • webDriverGrid - The location of selenium grid, like - http://localhost:4444/wd/hub
  • webSessionTimeOut - time out to be used before selenium tests framework gives up on loading a page
  • captureSnapshot - Should Selenium Tests Framework capture snapshots during test


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 What is ?   Using    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  ./ -daemon -host -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