How "should" you name your test methods?

When writing WebDriver (or other automated tests) we are often faced with dilemma of how to name test method. For ex you may come across following test methods -

verifyLoginAsValidUser
verifyLoginAsInvalidUser
verifyLogoutAndLoginAsUserWhoSavedConsentOnLastLogin
verifyDefaultTeamSelection
verifyTeamDisplay
verifyMembersDisplay

good enough, is not it? And if not then we can add more description about test method either in @description tag when using TestNG or on test method level comments. But what if test names were descriptive enough so that we don't have to resort to any of the other means ? Let's rewrite above mentioned test method names as -

shouldLoginUserWhenCredentialsAreValid
shouldNotLoginUserWhenCredentialsAreInvalid
shouldNotShowConsentScreenWhenConsentWasSavedOnLastLogin
shouldSelectDefaultTeamOnPageLoad
shouldDisplayTeamAttributesForSelectedTeam
shouldDisplayMemberLoginNamesForSelectedTeam

Here in test method names are based on format - Should<expected>_When<condition>. There is extended discussion on this topic on SO

Do you think these method names are more descriptive than what we used earlier? How would you name your test methods?

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

Return only first or last element from webelements collection

Note: If you are new to java and selenium then start with selenium java training videos . We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" )); Now we can get the first web element from this collection as - WebElement firstElement = Iterables. getFirst (webElements, getDriver().findElement(By. id ( "defaultElement" ))); Herein second

Using chrome console to test xPath and css selectors

Note: If you are new to java and selenium then start with selenium java training videos . 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 wri

No Automated Testing

Search This Blog