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

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 -

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .     How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Updated: 2026 (Original article published August 02, 2011) Email confirmation is an integral part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding emails. Sooner or later, every automation engineer faces the same challenge: How do we verify an email confirmation link inside a Selenium test without making the test slow and flaky? Many beginners try to automate Gmail UI using Selenium. That approach is fragile, slow, and tightly coupled to a third-party UI that changes frequently. A cleaner approach is this: Use Selenium for browser automation. Use JavaMail (IMAP) to read the email directly. Extract the confirmation link. Continue the test using Selenium. This guide shows a modern, production-ready approach using Selenium 4 and JavaMail . Why Not Auto...

Capture network traffic using WebDriver

We often come across testing requirements when we need to analyze the network traffic to find - HTTP status of page Analyze header information to find if right information is passed Validating parameters related to ajax requests etc Selenium 1 has had a way to capture n/w traffic but the feature does not always work as expected. At times Selenium 1 does not capture all n/w traffic, And given that Selenium 1 APIs are almost dead it is