Top Login Page Test Cases - Manual Testing Interview Questions

In this video, we will try to cover different login page feature manual test cases. I have tried my best to cover as much as possible, tried to cover different functional and non functional test cases with performance, security and compatibility testing point of view.

================================================================================
Login Test Cases
A. Functional test cases:
1. valid un/pwd +ve
2. invalid un/pwd -ve
3. valid un but invalid pwd -ve
4. blank un/pwd -ve
5. blank un but some pwd --ve
6. valid un and blank pwd -ve
7. forgot password feature test +ve
8. after forgot pwd, user should be able to login +ve
9. Reset Password +ve
10. inavlid use cases -- messages on the UI -ve
11. valid un/pwd -- on home page -- check valid username
12. Remember me -- +ve
13. SSO - Single Sign On -- +ve
14. check password field -- ***** or ....
15. Show password -- Test123
16. Enter key +ve
17. password policy: more than 8 characters
--only alphanumeric combination
--No @#$ chars allowed
--Easy, Medium, Strong, Very Strong
18. Click on Back Button after logged out -ve
19. check password in browser cache/cookies +ve
20. expired password -ve
21. blocked user:
--for life time blocked
--for 24 hrs or for sometime blocking
22. check login feature on different browsers
23. check login on different devices : ios/Android/tablet
24. User validation in DB:
--DL/Passport/Doc is missing
--Email Confirmation is pending
25. Email notificaion for login/password +ve
26. logged in FF with UN1, open a new tab, try to
login with UN2 -ve
27. Session Expired -- -ve
--30 mins, 1 hr, 15 mins, 10 mins
28. on Differnt browsers

B. Non Functional test cases: Performance, Security
1. should not take time to login to app
2. usability testing -- proper validation messgs
3. Alignment, look and feel
4. Password policy: should be followed
5. SQL Injection:
6. SSL certificate testing
7. In backend: on PROD, customer password should not be logged in logs
8. Encryption and decryption of the password:
Test123 -- 2345@%@#$%23$%@#$%SFGSG
9. India -- logged in to APP
and at the same time
Germnay -- logged into APP

10. history of login details
11. Mobile App -- Samsung login
--Apple iphone 8: login
12. unsuccessful login attempts:
--3 times wrong password: 1 hr blocked
--10 times wrong pwd: blocked for 1 hr
==============================================================================

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation:

Follow me on my Facebook Page:

Let's join our Automation community for some amazing knowledge sharing and group discussion on Telegram:

WebServices API Automation Tutorials:

Follow me on my Facebook Page:

Let's join our Automation community for some amazing knowledge sharing and group discussion on Telegram:

Paid courses (Recorded) videos:
📗 Get My Paid Courses at
Paid courses (Recorded) videos:
-------------------------------

✔️SOCIAL NETWORKS
--------------------------------

Support My Channel✔️Or Buy Me A Coffee
--------------------------------
✔️Thanks for watching!
देखने के लिए धन्यवाद
Благодаря за гледането
感谢您观看
Merci d'avoir regardé
Grazie per la visione
Gracias por ver
شكرا للمشاهدة

[nilstoned]

I'll add a few:
1) In Inspect element for passwords, one should not see passwords in plaintext
2) Copy/paste actions should be disabled on the password field
3) If i login on chrome window, try loging in in ingognito window on same machine with same user
4) after entering correct creds, check url after hitting login button, it should not reveal cerds on url
5) check ui on mobile devices, on different desktops, on half size window
6) check for login api time on 3g, 4g networks
7) after logging in, copy url and paste on new device or in incognito. check if it reveals or redirects to log in again
8) check for suspicious logins based on AI like if the user normally logs in once or twice a day, has logged in for 50 times on a particular day, send notification email of same to user's email
9) in case of rotating screens like tab, mobile devices, check ui alignments on rotating screens randomly
10) check if its https or http. try manipulating it
11) check for localization i.e. login page language as per local such as chinese or english or hindi
12) check for at a time, how many users can login in server, part of performance testing

[sauravhateme]

Great Coverage Naveen.

Few add ons:
Functional:
1. On screen keyboard should popup having numbers and characters for all MOB devices
2. Login with Face id sign up
3. If the face id dont not recognize, user can give passcode
4. Setting visual pattern
5. OTP
6. Push Notification followed by Login and deeplink to the specific page as per notification message
7. Extend session while logged in if any
8. Recent logged in activity with device info validation
9. any footer link which leads to the product page should allow user to authenticate
10. Navigation url should be masked the user name & password
11. If you a user is logged out and lands back on log in page, and face id should not log back in again

[rishikachowdarypotturu]

Never thought that these many test cases should be covered... Appreciate it👏

[Hey_Ram]

Thank you so much, Mr. Naveen.


We can add these 3 test cases under non-functional test cases:-
1. Same time mobile app and net banking login not allowed (-ve)
2. registered security questions on the 3rd login attempt.
3. page should be logged out when network changes - Like from LAN to wifi.

[sristilohani]

The OTP which goes to mobile at the time of login, for some banking applications should not take much time. This can be covered in performance testing.

[zeshansikandar]

Sir Naveen i'm really thankful to you by watching your videos i switched my career and got a job in a reputable company, you are doing great for humanity indeed knowledge has no boundries keep sharing and keep growing .Love from Pakistan

[puneethshivalingaiah]

Thanks for this video @Naveen. You are enhancing others' knowledge as well.

[thaneeshsiddam]

Thanks Naveen, your are doing great service to the community

[sharadaa]

Hai Thank You So Video on Login understood everything easily such a Good Explanation

[margaritashamrakov]

Thank you Naveen for really going in depth on this topic. I have learned so much.

[vasupokala]

Thank you very much Naveen. Really liked your way of explanation..

[footprints]

Thank you so much for taking this topic.. I was just waiting for this..

[priyasinha.]

Thankyou Naveen, that really was 'Out of the Box' explanation

[SarangHoley]

Thanks Naveen for taking this topic into consideration as well, as being said by you always while teaching, as a tester you should have diversified mindset to cover different aspects of a scenario. Thanks 😊👍

[classicideas]

Thank u sir for giving lots of testcases for login page😊

[sumapatil]

Thank you Naveen for the Video. How it is possible for you to think this much out of the Box :-). Its really amazing. you have covered a lot for Login scenario. Nobody covers all these scenarios. Its simply GREAT !!! thanks a Ton.

[automationtestingempire]

Thank you so much Naveen to make our life bright 🌞🌞🌞🌞

[piyushjain]

My suggestions:
1. In case OTP is required for multifactor authentication, the user should recieve OTP within an appreciable time limit even when the application is getting heavy traffic. That can be part of performance testing.
2. Password field should be case sensitive.
3. Suspicious login (Multiple wrong attempts, New device Logins, Inactive user) should be notified to the user immediately, along with a Logout from all devices option.
4. Captcha working properly or not.

[sunitkulkarni]

Thank you Naveen.... Its very helpful.

[cashedge]

Nice video. Thanks
I can think of just one more test in security test=> Login using URL Rewriting. This issue came in real time in financial application(Wells Fargo Bank) where we have user with multiple roles can login to application as customer and as vendor and performing payments.
In functional => Login with Facebook with valid account / invalid account
Login with Google with valid account / invalid account