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

Using xPath to reach parent of an element

Note: If you are new to java and selenium then start with selenium java training videos .   I prefer css locator over xPath but 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 hig...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Should selenium tests be always independent? The endless debate !!

Though unit tests have always recommended to be independent of each other, advent of selenium+TestNG has given birth to dependent integration/end to end tests. TestNG Author Cédric Beust had written about it few years ago. When I had begun writing selenium tests I used to launch browser once in one test class and test methods were usually dependent on one another. Hence 2nd test method would begin test run on same browser + application state where 1st test method stopped. Launching just one browser for five or more test methods in a class is big time saving is not it? Well not really, for the reasons I am going to describe in this post. Since then I have moved on to launching browser per test method but yet give in “charm” of dependent test methods at times. to So here are the few pros and cons for dependent tests and - Pros - Similar steps of execution don’t have to be repeated in multiple tests when steps constitutes a test method in themselves If login fails then...