Gmail Test Cases [ Inbox, Draft & Sent ] Template Example

Module wise test cases for Gmail, definitely helpful to you all.

Test Scenarios Login Page

• Verify that the login screen is having the option to enter a username and password with submit button and option of forgot password
• Verify that the user is able to login with valid username and password
• Verify that the user is not able to login with invalid username and password
• Verify that validation message gets displayed in case user leaves username or password field as blank
• Verify that validation message is displayed in case user exceeds the character limit of the user name and password fields
• Verify that there is a reset button to clear the field’s text
• Verify if there is a checkbox with label “remember password” in the login page
• Verify that the password is in encrypted form when entered
• Verify that there is a limit on the total number of unsuccessful attempts
• For the security point of view, in case of incorrect credentials, the user has displayed the message like “incorrect username or password” instead of exact message pointing at the field that is incorrect. A message like “incorrect username” will aid hacker in brute-forcing the fields one by one
• Verify the timeout of the login session
• Verify if the password can be copy-pasted or not
• Verify that once logged in, clicking back button doesn’t log out user
• Verify if SQL Injection attacks work on the login page
• Verify if XSS vulnerability work on the login page

Test scenarios for Registration Page

• Verify that all the specified fields are present on the registration page
• Verify that the required/mandatory fields are marked with * against the field
• Verify that for better user interface dropdowns, radio buttons and checkboxes etc fields are displayed wherever possible instead of just textboxes
• Verify the page has both submit and cancel/reset buttons at the end
• Verify that clicking submit button after entering all the required fields, submits the data to the server
• Verify that clicking cancel/reset button after entering all the required fields, cancels the submit request and resets all the fields
• Verify that whenever possible validation should take place at client side
• Verify that not filling the mandatory fields and clicking the submit button will lead to a validation error
• Verify that not filling the optional fields and clicking submit button will still send data to the server without any validation error
• Check the upper limit of the textboxes
• Check validation on a date and email fields (only valid dates and valid email Ids should be allowed
• Check validation on numeric fields by entering alphabets and special characters
• Verify that leading and trailing spaces are trimmed
• Verify that entering blank spaces on mandatory fields lead to a validation error
• Verify that after making a request to the server and then sending the same request again with the same unique key will lead to a server-side validation error

Test Scenarios for Inbox Functionality (Receive Email)

• Verify that a newly received email is displayed as highlighted in the Inbox section.
• Verify that a newly received email has correctly displayed sender email or name, mail subject and mail body(trimmed to a single line).
• Verify that on clicking the newly received email, the user is navigated to email content.
• Verify that the email contents are correctly displayed with the desired source formatting.
• Verify that any attachments are attached to the email and are downloadable.
• Verify that the attachments are scanned for viruses before download.
• Verify that all the emails marked as read are not highlighted.
• Verify that all the emails read as well as unread have a mail read time appended at the end on the email list displayed in the inbox section.
• Verify that count of unread emails is displayed alongside ‘Inbox’ text in the left sidebar of Gmail.
• Verify that unread email count increases by one on receiving a new email.
• Verify that unread email count decreases by one on reading an email ( marking the email as read).
• Verify that email recipients in cc are visible to all user.
• Verify that email recipients in bcc are not visible to the user.
• Verify that all received emails get piled up in the ‘Inbox’ section and gets deleted in cyclic fashion based on the size availability.
• Verify that email can be received from non-Gmail emails like – Yahoo, Hotmail etc.

Test scenarios for Compose mail Functionality

• Verify that on clicking ‘Compose’ button, a frame to compose a mail gets displayed.
• Verify that user can enter emails in ‘To’, ‘cc’ and ‘bcc’ sections and also user will get suggestions while typing the emails based on the existing emails in user’s email list.
• Verify that the user can enter multiple commas separated emails in ‘To’, ‘cc’ and ‘bcc’ sections.
• Verify that user can type Subject line in the ‘Subject’ textbox.
• Verify that the user can type the email in email-body section.
• Verify that user can format mail using editor-options provided like choosing font-family, font-size, bold-italic-underline etc.
• Verify that the user can attach the file as an attachment to the email.
• Verify that the user can add images in the email and select the size for the same.
• Verify that after entering emails in either of the ‘To’, ‘cc’ and ‘bcc’ sections, entering Subject line and mail body and clicking ‘Send’ button, mail gets delivered to intended receivers.
• Verify that sent emails can be found in ‘Sent Mail’ sections of the sender.
• Verify that mail can be sent to non-Gmail emails also.
• Verify that all sent emails get piled up in the ‘Sent Mail’ section and gets deleted in cyclic fashion based on the size availability.
• Verify that the emails composed but not sent remain in the draft section.
• Verify the maximum number of email recipients that can be entered in ‘To’, ‘cc’ and ‘bcc’ sections.
• Verify the maximum length of text that can be entered in the ‘Subject’ textbox.
• Verify the content limit of text/images that can be entered and successfully delivered as mail body.
• Verify the maximum size and number of attachment that can be attached with an email.
• Verify that only the allowed specifications of the attachment can be attached with an email/
• Verify that if the email is sent without Subject, a pop-up is generated warning user about no subject line. Also, verify that on accepting the pop-up message, the user is able to send the email.

if you got any missed test case scenario then you can inform us by commenting on the comment section.