Manual Test Cases to verify 'Email' Functionality
Verify Inbox functionality:-
1).Verify that total unread email count appears.
2).Verify that a newly received email is displayed as highlighted in the Inbox section.
3).Verify that a newly received email has correctly displayed sender emailId or name, mail subject, header and mail body.
4).Verify that on clicking the newly received email, the user is navigated to email content/body.
5).Verify that the email contents are correctly displayed with the desired source formatting.
6).Verify that any attachments are attached to the email and are downloadable.
7).Verify that the attachments are scanned for viruses before download.
8).Verify that all the emails marked as reading are not highlighted.
9).Verify that all the emails read as well as unread have a mail read time appended at the end of the email list displayed in the inbox section.
10).Verify that count of unread emails is displayed alongside 'Inbox' text in the left sidebar of Gmail.
11).Verify that unread email count increases by one on receiving a new email.
12).Verify that unread email count decreases by one on reading an email ( marking the email as reading).
13).Verify that email recipient in cc are visible to all user.
14).Verify that email recipient in bcc are not visible to the user.
15).Verify that all received emails get piled up in the 'Inbox' section and gets deleted in cyclic fashion based on the size availability.
16).Verify that email can be received from non-Gmail emailIds like - yahoo, Hotmail etc.
Verify Compose Mail Functionality:
1).Verify that on clicking 'Compose'/'create new' button, a frame to compose a mail gets displayed.
2).Verify that user can enter emailIds in 'To', 'cc' and 'bcc' sections and also user will get suggestions while typing the emails based on the existing emailIds in user's email list.
3).Verify that user can enter multiple commas separated emailIds in 'To', 'cc' and 'bcc' sections.
4).Verify that user can type Subject line in the 'Subject' textbox.
5).Verify that user can type the email in email body section.
6).Verify that user can format mail using editor-options provided like choosing font-family, font-size, bold-italic-underline etc.
7).Verify that user can user can attach the file as an attachment to the email.
8).Verify that user can add images in the email and select the size for the same.
9).Verify that after entering emailIds in either of the 'To', 'cc' and 'bcc' sections, entering the Subject line and mail body and clicking 'Send' button, mail gets delivered to intended receivers.
10).Verify that sent mails can be found in 'Sent Mail' sections of the sender.
11).Verify that mail can be sent to non-Gmail emailIds also.
12).Verify that all sent emails get piled up in the 'Sent Mail' section and gets deleted in cyclic fashion based on the size availability.
13).Verify that the emails composed but not sent remain in the draft section.
14).Verify the maximum number of email recipients that can be entered in 'To', 'cc' and 'bcc' sections.
15).Verify the maximum length of text that can be entered in the 'Subject' textbox.
16).Verify the content limit of text/images that can be entered and successfully delivered as mail body.
17).Verify the maximum size and number of attachment that can be attached to an email.
18).Verify that only the allowed specifications of the attachment can be attached with an email
19).Verify that if the email is sent without Subject, a pop-up is generated warning user about no subject line. Also, Check that on accepting the pop-up message, the user is able to send the email.
Type of Bounces in Email
When we send an email to an subscriber/user then sometimes it get bounce due to some reason, There are four type of bounces in emails
Email Soft bounce :-
A soft bounce occurs when the email server rejects the email due to a seemingly temporary condition,
such as a full inbox. When that happens, the system retries sending the email to the subscriber every
15 minutes for 72 hours, for up to 288 tries. Only after the system stops attempting to retry does a
subscriber appear in your tracking as bounced.
The 288 re-tries do not count as bounces. Instead, the full count of unsuccessful retries equate to one soft bounce. If the system attempts delivery 288 times and the message bounces each time, the subscriber's status is set to Bounced. If the email is delivered during the 288 tries and the subscriber opens the email, the subscriber's status is set to Active.
Examples of this type of soft bounce that would show up faster include these types of ISP responses:
mailbox would exceed maximum allowed storage
user account is over quota
mailbox is full
mailbox temporarily disabled
mailbox disabled, not accepting messages
After Marketing Cloud receives the third soft bounce for a subscriber, their status is set to Held.
Email Hard bounce :-
A hard bounce occurs when the email server rejects the email due to permanent conditions
(this typically results when "user unknown" or "domain not found" errors occur). What happens next depends
on the subscriber's current status. If the subscriber's status was already Active, their status now changes to Bounced.
If the subscriber's status was already Bounced, which indicates they had experienced a bounce previously,
the application treats the bounce differently.
Email Technical bounce :-
A technical bounce, which is considered a type of soft bounce, occurs when the email server rejects the email due
to technical errors, such as a data format or network error. When a subscriber experiences a technical bounce they are
re-tried in the next email send.
This table describes the causes of a technical bounce.
|Server Too Busy||Receiving email server is temporarily overwhelmed with delivery attempts from you and other senders|
|Data Format Error||Email is rejected due to formatting or line length errors|
|Network Error||Connection lost or timed our during delivery line length errors|
Email block bounce :-
A block bounce, which is considered a type of soft bounce,
occurs when the email server rejects the email due to filter issues,
such as URL blocks, lack of proper authentication,
or the domain or IP address is found on a blacklist utilized by the receiving domain. A subscriber who receives a block bounce is re-tried in the next email send.
This table describes the causes of a block bounce.
|Complaint||Your email is blocked due to complaints|
|Blacklist||IP address is on a blacklist|
|Content||Message was filtered due to content|
|URL Block||Emails containing your URLs are blocked|
|Authentication||Message lacks required authentication|