Skip to main content

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? 
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