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?

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos . How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Updated: 2026 (Original article published August 02, 2011) Email confirmation is an integral part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding emails. Sooner or later, every automation engineer faces the same challenge: How do we verify an email confirmation link inside a Selenium test without making the test slow and flaky? Many beginners try to automate Gmail UI using Selenium. That approach is fragile, slow, and tightly coupled to a third-party UI that changes frequently. A cleaner approach is this: Use Selenium for browser automation. Use JavaMail (IMAP) to read the email directly. Extract the confirmation link. Continue the test using Selenium. This guide shows a modern, production-ready approach using Selenium 4 and JavaMail . Why Not Auto...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Capture network traffic using WebDriver

We often come across testing requirements when we need to analyze the network traffic to find - HTTP status of page Analyze header information to find if right information is passed Validating parameters related to ajax requests etc Selenium 1 has had a way to capture n/w traffic but the feature does not always work as expected. At times Selenium 1 does not capture all n/w traffic, And given that Selenium 1 APIs are almost dead it is

No Automated Testing

Search This Blog