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.
Note: If you are new to java and selenium then start with selenium java training videos . I generally prefer CSS selectors over XPath when writing Selenium locators. CSS selectors are concise, readable, and usually provide everything I need. However, there are situations where XPath is a better fit—particularly when I need to navigate through an element's hierarchy, such as moving from an element to its parent, grandparent, or sibling. This post shows one such real-world example. The Problem I came across a situation where I needed to click a link based on the value of an input field. The HTML structure contained multiple similar groups of elements. The input field and the link I wanted to click were not directly related, but they shared a common parent structure. In the following example above, the input element is highlighted, and I need to click the corresponding anchor ( <a> ) element . The challenge is that there may be multiple similar structures on the page. I th...
Comments
Post a Comment
No spam only genuine comments :)