Skip to main content

Do you check for absence of element on page

When writing automated tests we often check presence or absence of element for assertion conditions. This is usually written as - 

assertTrue("Element is missing. Bug!!!", pageObject.isSomeElementDisplayed());

And when element is not displayed then above mentioned assert statement fails.

In the similar manner we can write following assert statement to check for absence of element - 

assertFalse("Element is present. Bug!!!", pageObject.isSomeElementDisplayed());

Above mentioned assert statement would fail if element is displayed on page.

Everything looks ok, is not it. Not really, there is catch. Let's have a closer look at assertFalse statement we used above - 


assertFalse("Element is present. Bug!!!", pageObject.isSomeElementDisplayed());

This assert statement would also succeed even if webpage results in 404/500 or any other error page, since error page would also be missing the element on which we are performing assert.

So what is the solution? My recommendation is to not use check for absence of element but presence of element for assertion. What do you think of this approach?
Labels:

Popular posts from this blog

Which location strategy to use with mobile apps

Locator Strategy for native mobile apps IDs and accessibility locators are still king. NSPredicate (iOS) and UIAutomator (Android) are great—mainly better than XPath —but they do not beat a good accessibility id or resource-id . And CSS selectors don’t exist for native apps (only for WebViews). Locator Strategy Ranking Rank iOS (native) Android (native) Why 1 Accessibility ID → name / label (via MobileBy.AccessibilityId or @iOSXCUITFindBy(accessibility = "Mehr anzeigen") ) Accessibility ID → content-desc (via MobileBy.AccessibilityId ) or @AndroidFindBy(accessibility = "Letzte Aktivitäten, Überschrift") ) Fast, readable, stable when set intentionally; improves a11y. 2 Stable identifiers (rare on iOS) resource-id (via new UiSelector().resourceId(...) ) or @AndroidFindBy(id = "load_more") id is just shorthand for matching the native Android resource-id attribute. Appium automatically maps id → resource-id If you pass only "load_more"...
Post a Comment
Read more

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can
13 comments
Read more

Selenium Tutorial: Get attribute of an element

With Selenium 1.0 Let us consider Google Search Box for example and its "max length"is to be retrieved. Using xPath -         String var = selenium.getAttribute("//input[@name='q']/@maxlength");         System.out.println(var); Using css locator -                        String var = selenium.getAttribute("css=input[name='q']@maxlength");         System.out.println(var);        With Selenium 2.0 (WebDriver)        Using xPath -         String var = webDriver.findElement(By.xpath("//input[@name='q']")).getAttribute("maxlength")         System.out.println(var); Using css locator -                     ...
2 comments
Read more