In this post, we will study – how to write test cases for a Login page. You can refer to these test cases while creating test cases for login page of your application under test.
As we know that the focus here is to cover the different features to be tested instead of the creation of formal test cases, so basically we will be presenting test scenarios here. If you want to know the exact difference between test cases and test scenarios, please refer to this post – Difference b/w Test Case and Test Scenario.
Let’s start with sample test cases of the login page now, categorized on the basis of different types of testing.
UI Test Scenarios for Login Page
- Verify that all the labels and controls including text-boxes, buttons, and links are present on the Login page.
- Verify that the font type and size of the labels and the text written on the different elements should be clearly visible.
- Verify that the size, color, and UI of the different elements are as per the specifications.
- Verify that the application’s UI is responsive i.e. it should adjust to different screen resolutions and devices.
Functional Test Scenarios for Login Page
- Verify that as soon as the login page opens, by default the cursor should remain on the username textbox.
- Verify that the user is able to navigate or access the different controls by pressing the ‘Tab’ key on the keyboard.
- Verify that the password is in masked form when entered.
- Verify if the password can be copy-pasted or not.
- Verify that the user is able to login by entering valid credentials and clicking on the ‘Login’ button.
- Verify that the user is able to login by entering valid credentials and pressing Enter key.
- Verify that the user is not able to login with an invalid username and password.
- Verify that the validation message gets displayed in case the user leaves the username or password field as blank.
- Verify that the validation message is displayed in the case the user exceeds the character limit of the user name and password fields.
- Verify that reset button functionality on the login page. Clicking on it should clear the textbox’s content.
- Verify if there is a checkbox with the label “remember password” on the login page.
- Verify that closing the browser should not log-out an authenticated user. Launching the application should lead the user to login state only.
Security Test Scenarios
- Verify that there is a limit on the total number of unsuccessful login attempts. So that a user cannot use a brute-force mechanism to try all possible combinations of username-password.
- Verify that in case of incorrect credentials, a message like “incorrect username or password” should get displayed instead of an exact message pointing to the incorrect field. This is because a message like “incorrect password” will help a hacker in knowing that the username is correct and he just needs to try a different combination on the password field only.
- Verify the login session timeout duration. So, that once logged-in a user cannot be authenticated for a life-time.
- Verify that once logged in, clicking the back button doesn’t logout the user.
- Verify if SQL Injection attacks work on the login page. The application should not be vulnerable to SQL injection attacks.
- Verify that XSS vulnerability should not work on the login page.
This concludes our post on the test cases for the login functionality. I hope these sample test cases will not only help you in your interviews but will also help you in writing test cases of similar forms. Please let us know in comments, how we did, and also, in case we have missed out on anything.
Test Case Examples
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can find him on LinkedIn.