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

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more