Disadvantage of using isTextPresent method and possible work around

Default Selenium class has a method called 'isTextPresent' which can be used to
verify presence of text on a page. Disadvantage of using this method is -

It checks for presence of text in entire page, hence even if text is present at
a different location test would pass and no error would be reported.

A better approach would be to find text on the basis of it's position in page.

If text which is to be validated is part of table then 'getTable' method can be
used. 'getText' method can also be used BUT element locator should be taken as
dom so that presence of text is validated at a certain position.

Ex -

Consider presence of text "Employee Number1 :*" is  to validated on a page. It
can be done as following using getText method -

verifyEquals("Asserstion Failed for getText.", "Employee Number1 :*",
selenium.getText("document.getElementsByTagName('table')[0].
getElementsByTagName('tr')[0].getElementsByTagName('td')[0]"));

verifyEquals method takes three string -

1. Error message which would be displayed if objects do not match.
2. Expected String object from app.
3. Original String Object in app. (Here getText method is used which returns
string object from the specified element locator.)

getTable method can be used here if text resides in a table. This would be as
following -

verifyEquals("Assertion Failed for getTable", "Employee Number1 :*",
selenium.getTable("document.getElementsByTagName('table')[0].0.0"));

Here Cell Address syntax is - tableLocator.row.column, where row and column
start at 0

I have used verify methods here as I didn’t want test to be aborted in case
of failure but wanted these exceptions to be raised in reports. Don't forget to
call checkForVerificationErrors as the last statement of method call or better
make it part of SelTestCase class as following -

@AfterTest(alwaysRun = true, description = "This methods checks verification
errors of testmethods.")
   public void checkAfterTest() throws Exception {       
   checkForVerificationErrors();
}

This would avoid code duplication which would be introduced if calls are made
to checkForVerificationErrors in each test method.