Skip to main content

Soft Assertions: Where and when we can use it?




To tackle the disadvantage of Hard Assertions where we want to continue the execution even if some assert fails and see the result at the end of the test.


Soft Assertions are the type of assertions that do not throw an exception when an assertion fails and continue with the next step after assert statement. This is in the case where our test requires multiple assertions to be executed and we want all of the assertions to be executed first before marking (failing/skipping) the tests.



Consider these 2 examples:

1) We're verifying many CSS values of the same element like background-color, font-family, and color in a single test case.



element.getAttribute("background-color")

element.getCssValue("font-family")

element.getCssValue("color")



Obviously, if any one of these fails we would like to catch it and mark the test case as fail but that doesn't mean if background-color verification fails it should mark the test case fail without even checking the other 2 CSS values. In this case, we want our test to verify all and then share the final status as failed even if any one of these isn't working.



2) We're verifying that all the links present on the page are working fine or not.



Here too, if anyone of the links isn't working we would like to catch it and mark the test case as fail but that doesn't mean if one link verification fails it should mark the test case fail without even checking the other links. In this case, we want our test to verify all the links and then share the final status as fail even if any one of these isn't working.



In case we use normal asserts like Assert.assertTrue() or Assert.assertEquals() in TestNG, @Test Method will immediately fail after any of the Asserts fails.



So here, SoftAssertion helps to collect all the assertions throughout the @Test method and to see assertions result at the end of the test, we have to invoke assertAll().



Sample code:

@Test

public void testSA() {

SoftAssert softAssert = new SoftAssert();

softAssert.assertEquals("powderblue", elementBGColor, "The background color isn't matching.");

softAssert.assertTrue("lato,sans-serif".equals(elementFF), "Font-family appears to be different.");

softAssert.assertTrue("#222".equals(elementColor), "Element color appears to be different.");

softAssert.assertAll();

}

Labels:

Comments

Post a Comment

Popular posts from this blog

ARIA Snapshot in Playwright

  What is an ARIA Snapshot in Playwright? An  ARIA snapshot  in Playwright is a structured representation of a page’s  accessibility tree , which is used by assistive technologies (e.g., screen readers) to interpret the content of a web page. This snapshot helps verify if elements have the correct  roles, names, and properties  required for accessibility. Playwright provides the page.accessibility.snapshot() API to capture this accessibility tree at any given moment during test execution. How Does ARIA Work? ARIA ( Accessible Rich Internet Applications ) is a set of attributes that help improve accessibility by defining roles, states, and properties for elements that are not natively accessible. Example: In this case, the aria-label ensures that screen readers identify the button as “Submit Form.” How to Use ARIA Snapshots in Playwright? Playwright’s  accessibility.snapshot()   method retrieves the  accessible structure  of the page. Ex...
Post a Comment
Read more

Bruno vs Postman: Which API Client Should You Choose?

  As API testing becomes more central to modern software development, the tools we use to test, automate, and debug APIs can make a big difference. For years, Postman has been the go-to API client for developers and testers alike. But now, Bruno , a relatively new open-source API client, is making waves in the community. Let’s break down how Bruno compares to Postman and why you might consider switching or using both depending on your use case. ✨ What is Bruno? Bruno is an open-source, Git-friendly API client built for developers and testers who prefer simplicity, speed, and local-first development. It stores your API collections as plain text in your repo, making it easy to version, review, and collaborate on API definitions. 🌟 What is Postman? Postman is a full-fledged API platform that offers everything from API testing, documentation, and automation to mock servers and monitoring. It comes with a polished UI, robust integration, and support for collaborati...
Post a Comment
Read more

🔧 Self-Healing Selenium Automation with Java — A Smarter Way to Handle Broken Locators

  How to build smarter, more resilient automated tests? We’ve all been there — our Selenium test cases start failing because of minor UI changes like updated element IDs, renamed classes, or even reordered elements. It’s frustrating, time-consuming, and often the most dreaded part of maintaining automated tests. But what if your automation could heal itself? 💡 What is Self-Healing Automation? Self-healing automation  refers to the capability of a test automation framework to recover from minor UI changes by automatically trying alternative locators when the primary one fails. It’s like giving your test scripts a survival instinct. 🔨 🛠️ Implementation in Java + Selenium: Step by Step Step 1: Create a Self-Healing Wrapper We start by creating a custom class called SelfHealingDriver. This class wraps the standard WebDriver and handles locator failures gracefully. public   class   SelfHealingDriver { private   WebDriver driver ; public   SelfHealingDri...
Post a Comment
Read more