Skip to main content

assertTrue vs assertEquals for text verification

  

We all do text validation in our automation tests to validate whether the returned value is the same as the expected one or not. I see that many folks use the assertTrue command instead of assertEquals to validate the returned text while using assertions from TestNG or JUnit. Let's see why using assertTrue is bad practice for text comparison.

 

assertEquals

public static void assertEquals(String actual, String expected)

Asserts that two Strings are equal. If they are not, an AssertionError is thrown.

Parameters:

  • actual - the actual value
  • expected - the expected value


assertTrue

public static void assertTrue(boolean condition)

Asserts that a condition is true. If it isn't, an AssertionError is thrown.

Parameters:

  • condition - the condition to evaluate

 

Let’s say that I have an automated test script where I would like to verify the Title of the home page -  we are doing the check using assertTrue as well as assertEquals methods.

 

String ExpectedTitle = "My All Testing Stories";


@Test

              public void verifyTitleUsingTrue() {

                             assertTrue(driver.getTitle().equals(ExpectedTitle));

              }

 

@Test

              public void verifyTitleUsingEquals() {

                             assertEquals(driver.getTitle(), ExpectedTitle);

}

             

Note* The actual result of driver.getTitle() will be "My Testing Stories" but the expected one is "My All Testing Stories".

 

When you execute this, it will fail as expected and you will see an error message like this for assertTrue:

FAILED: verifyTitleUsingTrue

java.lang.AssertionError: expected [true] but found [false]

 

Were you able to understand the problem through the error message? I doubt that.

 

And this is the error message you will see for assertEquals:

FAILED: verifyTitleUsingEquals

java.lang.AssertionError: expected [My All Testing Stories] but found [My Testing Stories]

 

As you can see that the use of assertEquals makes it much easier to understand what the actual difference between the expected and actual results is. Also, we can catch the failure without opening the code and trying to search for the text differences. So, use the proper method as per the context :)

 

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