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

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