Skip to main content

Implementing soft assertion with selenium

Soft Assertion is a check which doesn't abort tests if assertion fails. (Same
way there is Hard Assertion which aborts tests if assertion fails.)

Selenium API has verify.* methods for this but their are draw backs of these
methods -

1. Verification methods do not take string arg hence if multiple verifications
fail in a method then there is no way to point as to which assertion failed.

2. To check verification errors checkForVerificationErrors method is called. But
if there is any verification error this method doesn't clear the verification
errors after having caught it. Hence no subsequent verification errors would be
checked.

These limitation are described here -
http://osdir.com/ml/web.selenium.devel/2007-09/msg00022.html

These methods are part of Java-Client-Driver of selenium.
I have modified checkForVerificationErrors method like this -

Here Reporter is the class in TestNG using which I get the message printed in
TestNG Report. If Selenium is to be used with JUnit then I believe it should be
replaced with System.out.println("error message");

You could use these methods in you tests as following -

Comments

  1. Hi Tarun... Thanks for this wonderful post... I have been searching for this for a long time... Could you please share me the updated java client jar, which u have mentioned in this post. My mail id is mgharikrishnan at gmail. dot com. Thanks in advance

    ReplyDelete
  2. Though I don't have access to jar any more, I would post entire class here and you could use it you tests... To do so I am going to modify this blog post

    ReplyDelete
  3. Tarun.. Thanks for updating this post... I will try to implement this in my code and get back to you, IF i have any doubt!!
    Thank you, once again!!!

    ~ Harri...

    ReplyDelete
  4. :) I will be glad if it helps you.

    ReplyDelete

Post a Comment

No spam only genuine comments :)

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