Skip to main content

Java Training Tutorials for Software Testing Engineers

UPDATES: Java training tutorial with flavor of Selenium Webdriver are live now :)

The boundaries between software testing and development are beginning to blur in today’s technological environment. Knowledge of programming language would not just help you gain more knowledge in the field of software testing but also makes you more competitive in today’s job market.
When I started with Selenium Training Tutorial, I assumed that every one is from programming background. Many of you have asked me that it is very difficult for you to learn Selenium without knowledge of a programming language.
Hence I decided to create video tutorial in java, especially designed for software test engineers. Those software test engineers who have little or no programming experience. Learning one programming language would almost always make it easy for you to learn any other language.
But there is one condition :)

I would begin with java training tutorials when Software Testing forum on Facebook reaches 2000 likes. and ONLY YOU can help me achieve this -

It would be impossible to reach this target without your help. Please share 
FaceBook Testing Forum with software test Engineers on your Facebook/LinkedIn/Twitter/<Other Social Media Networks>. At the time of writing this post. There are about 300 likes on testing forum. Reaching more “likes” will help me take training program to more users free of cost.
While we are on the journey to reach 2000 likes I will continue to create testing videos in other fields of software testing.
So would you help me reach 2k likes for FaceBook Testing Forum ?


Popular posts from this blog

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

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