Skip to main content

verifyTrue vs verifyEquals to compare strings

There is a clear winner here! Lets explore which one is better.

Here is the scenario:
“Lets say I have to test if the appropriate tooltip is flashed for a component”
To get to the code directly, lets say I already have the tooltip text stored in a variable. Now all I have to do is to compare this string to the components tooltip text which I would get at runtime.
So the algorithm would be
  1. Have the Expected Tooltip text stored in a variable
  2. Get the Actual Tooltip text for the component
  3. Compare the two strings – you should get the exact text

We usually tend to use verifyTrue to compare because according to our algorithm we are expecting the result of the string comparison to be TRUE Smile

There is nothing wrong in using verifyTrue as if your test passes there is no difference in using verifyTrue or verifyEquals. The actual difference comes into picture only when your test fails.

String varExpectedTooltipText = “Some tooltip”;
// Method 1 - verifyTrue(selenium.getAttribute("componentID"+"@title").equals(varExpectedTooltipText));
// Method 2 – verifyEquals(selenium.getAttribute("componentID"+"@title"), varExpectedTooltipText);

Log message when Method 1 fails:
java.lang.AssertionError: java.lang.AssertionError: null
Log message when Method 2 fails:
verifyEquals gives: java.lang.AssertionError: java.lang.AssertionError: Expected "Close this book list" but saw "Close this book lis" instead

Now you decide which one looks better – For me its verifyEquals wins the fight Smile
Labels:

Comments

Post a Comment

Popular posts from this blog

wget error–“zsh: parse error near &”

There is no doubt that I prefer wget way over any other type of downloads… Syntax: wget <DOWNLOAD_URL>   If you get this error “ zsh: parse error near & ” then its probably because your download URL has a “&” so you should try giving your DOWNLOAD_URL in double quotes wget “<DOWNLOAD_URL>”   If you are trying to download from a site which needs you to give your credentials then you can try giving it this way wget --http-user=<UserName> --http-password=<Password> “<DOWNLOAD_URL>”   Hope this helps
3 comments
Read more

How to Unpack a tar file on Windows?

On Windows: You can download a simple command line tool to do this. You can download the tool from here Usage can be found on the website but pasting it here too for convenience: C:\>TarTool.exe Usage : C:\>TarTool.exe sourceFile destinationDirectory C:\>TarTool.exe D:\sample.tar.gz ./ C:\>TarTool.exe sample.tgz temp C:\>TarTool.exe -x sample.tar temp TarTool 2.0 Beta supports bzip2 decompression for files with extensions like tar.bz2 and .bz2 . TarTool -xj sample.tar.bz2 temp or TarTool -j sample.bz2 Download TarTool 2.0 Beta from here Unpack a .txz file on Windows Use the 7zip tool  to unpack a .txz file on windows On Linux: You can use the bzip2 and tar combined to do this… for ex: bzip2 –cd <tar.bz_fileName> | tar –xvf - This will unpack the contents of the tar.bz file Happy Un-Tar-ing
47 comments
Read more

Apache Commons StringUtils.isEmpty() vs Java String.isEmpty()

You might want to test for if a String is empty many a times. Before we jump onto the numerous solutions available let us take a look at how we define “Empty String”   The difference in the two methods given by Apache and Java are dependent on how we define an empty string. Java String.isEmpty returns a boolean true if the string’s length is zero. If the string has null it throws NullPointerException Apache StringUtils.isEmpty returns a boolean true if the string is either null or has length is zero   Thus its purely dependent on how you are defining “empty string” in your program which will decide which function to use…BTW if you want to skip using Apache Commons funciton and would want to stick to java then you can have your own function like this:   public static boolean isEmptyOrNull(String strStringToTest) {                  return strStringToTest == null || strStringToTest.trim().isEmpty(); }
1 comment
Read more