Test Case For Password Field: In this article, we discuss test cases for passwords. There are many ways to test the passwords for an application. Depending on the type of application you have, and the amount of security you wish to add the test cases will be different.
So instead of writing the test cases just by assuming the password field on the form. Let’s try and think of different scenarios under which the passwords can be tested.
|Post On:||Test Case For Password|
|Post Type:||Test Case Template|
|Applicable For:||Freshers & Experience|
|Don’t Miss:||SoftwareTestingo Telegram Group|
Test Cases For Password
People reset their password when they don’t remember it. That’s the most obvious scenario you can think of while writing the test cases. People also need to reset their passwords when the app has some security issues.
- Check if the user able to enter the password in the text box or not.
- Check if the user is able to paste the password in the field.
- Check the max char limit for the password fields.
- Check the min char limit for the password fields.
- Check if the entered password is visible or encrypted.
- Check if the password field allows blank spaces only.
- Check if the password field accepts alphabets.
- Check if the password field accepts numbers.
- Check if the password field accepts the lower case and upper case alphabets.
- Check if the password field accepts special characters.
- Check error message is displayed or not when the user click submits button without entering any value in the password field. (Field is mandatory)
- Check based on the inputted password text it should display the progress bar. (Weak, Medium & Strong)
- Check if the password view functionality is available so that the user can see the entered password. (Eye visible on the right side of the password text box)
- Check on the Click of eye icon entered password should be visible in a readable format.
- Check the asterisk symbol for password filed if it is a mandatory field.
Password Test Case Encryption
Almost every secure web app needs to have an encryption system. You should discuss the following scenarios while setting the requirement for the password field.
- Check if the system allows users to do md5 hashing?
- Check if the system does any form of encryption?
- Check if the system stores the password in plain text?
- Check if the system masks the password while typing?
- Check if the password stored in the database is encrypted itself?
- Check if the encrypted is easy to decrypt using known tools?
There are many other encryption features you can think of and the more complex field, the harder encryption you need for the app.
Password Test Case Management
There are tools like KeePass and LastPass that offer to save the password on a desktop or browser. And then such tools can be used to automate browser login. Tools like these require a single master password and using that single password, you can automate the login across multiple websites. So testing such password fields using automation tools is going to be different.
- Check the app is allowing usage of a password management tool?
- Check if password management works properly with the app?
- Check if the password manager is secure enough to store the password?
Password Test Case Guidelines
Each web app should have some guidelines on the choice of password users should have for better security. So make sure you consider the following test scenarios.
- Check is the password legth is displayed for the field.
- Check is the app have some guidelines for password strength?
- Check is the app informs you which characters are allowed and which are not?
- Check is the password text fields allows or restrict you to enter not allowed characters.
Also, the app should notify you if there is any form of strength indication, if there is a caps, lock if it exists there. So this makes testing the password field a lot better.
You can also check some of the other secure password fields of popular cloud apps. This gives you an idea of how to test the password field better for your use. The above-explained test scenarios and test cases should be more than enough to start your test document. You can even add more test content, test data, and scenarios to the document.
Feel free to let me know if you have any other suggestions for the discussion. I’d appreciate your comments, and please feel to share this with your friends.