Skip to main content

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.

Comments

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a