The document provides a checklist for testing the login page of a Gmail application. It includes sections for UI testing, functional testing, compatibility testing, and security testing. The UI testing section verifies the presence, visibility, size, and responsiveness of elements on the login page. The functional testing section checks login functionality, validations, and navigation. Compatibility testing ensures browser compatibility. Security testing validates login limits, back button behavior, error messages, session expiration, and password security.
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
194 views
Gmail Check List Final
The document provides a checklist for testing the login page of a Gmail application. It includes sections for UI testing, functional testing, compatibility testing, and security testing. The UI testing section verifies the presence, visibility, size, and responsiveness of elements on the login page. The functional testing section checks login functionality, validations, and navigation. Compatibility testing ensures browser compatibility. Security testing validates login limits, back button behavior, error messages, session expiration, and password security.
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
Check list for Gmail login page
Checklist for UI Testing
1. Verify that all the labels and controls including text-boxes, buttons, and links are present on the Login page. 2. Verify that the font type and size of the labels and the text written on the different elements should be clearly visible. 3. Verify that the size, color, and UI of the different elements are as per the specifications. 4. Verify that the application’s UI is responsive i.e. it should adjust to different screen resolutions and devices.
Checklist for Functional Testing
1. To check that as soon as the login page opens, by default the cursor should remain on the username textbox. 2. To check the user is able to navigate or access the different controls by pressing the ‘Tab’ key on the keyboard. 3. Verify that the password is in masked form when entered. 4. Verify if the password can be copy-pasted or not. 5. Verify that the user is able to login by entering valid credentials and whether by clicking on the ‘Login’ button or pressing enter key. 6. Verify that the user is not able to login with an invalid username and password. 7. Check whether the validation message gets displayed in case the user leaves the username or password field as blank. 8. Check for the validation message get displayed in case the user exceeds the character limit of the user name and password fields. 9. Check the reset button functionality. Clicking on it should clear the textbox’s content. 10.To test the checkbox with the label “remember password” on the login page. 11.To check that closing the browser should not log-out an authenticated user. Launching the application should lead the user to login state only.
Checklist for Compatability testing
1. Is the HTML version being used compatible with appropriate browser
versions? 2. Verify the fonts are usable on any of the browsers 3. Is Java Code/Scripts usable by the browsers under test? Checklist for Security Testing 1. Verify that there is a limit on the total number of unsuccessful login attempts. 2. Verify that once logged in, clicking the back button doesn’t logout the user. 3. Verify the error messages should not display any important information. 4. Verify if the user is logged out from the system or user session was expired, the user should not be able to navigate the site. 5. Verify to access the secured and non-secured web pages directly without login. 6. Verify the user account gets locked out if the user is entering the wrong password several times. 7. Verify the cookies should not store passwords.