Skip to main content

Announcing Selenium Tests Automation Framework

Selenium Tests Framework (referred as STF from here on) is a test automation framework for automated testing of Desktop web, mobile site and mobile apps. STF is based on WebDriver, Appium, TestNG and Maven. STF source code is available on GitHub.



Please NOTICE that if you are new to selenium then you should first watch Java Training Video Tutorials and Selenium Training Video Tutorials

STF supports following features - 

• Supports running tests on following environments - 

IE, Firefox, Chrome browsers on Windows, Ubuntu and Mac

mobile web site tests on android and ios devices

mobile app tests on android and ios devices


• Awesome Test Reports with step by step details of test actions -





    • Self instantiation of most popular browsers i.e. - Firefox, chrome and IE testing, you need not set up chrome or IE server, our framework does it for you. Self serve instantiation of web browsers, hence you don't have to set up browser  yourself. STF takes care of all.  Plugin STF and start writing you tests from day one! 


  • Capture snapshot and html source on test failure (because snapshot and html sources adds in debugging test failures)


    • Retrying failed test (because test environment inconsistency is not new to us and we want to make sure if a test fails consistently)

   • Data driven tests using csv file and more complex run time data objects using TestNG (because we don't want to run tests with same data set time and again)


   • Soft Asserting the failures to continue with test execution even in the wake of failures

   • Selenium grid support (don't we love cloud)


  • Rerun only failed tests using testng failed xml file once an application defect is fixed
  • Test dependency using testng dependent method because integration tests are at times dependent on one another

  
Selenium Tests Framework Tutorials -

Have a question on STF or a feature suggestion ? Then please post it in testing forum 

Comments

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

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

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea