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

Have the Expected Tooltip text stored in a variable
Get the Actual Tooltip text for the component
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

Comments

How to check if my xpath is valid using firebug?

Yes, you can verify if your xpath is pointing to the right source on the web application under test using FireBug. Here is how:

Go to the Web Application under test We'll take Google for simplicity reasons
Open FireBug - Go to the Console Console can also be seen at the bottom of the page, so don't worry they both are the same. They can be switched as follows:

Type in $x("Your xpath here") on the command line prompt as shown below:

Hit Enter/RunYou will get to see the element which was filtered out with your XPath expression

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 quoteswget “<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 waywget --http-user=<UserName> --http-password=<Password> “<DOWNLOAD_URL>”Hope this helps

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

Tech Talk

Search This Blog