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?

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

Appium and android mobile app automation

Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report

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

No Automated Testing

Search This Blog