Sample Test cases for Testing Email

-
  1. Check that a newly received email is displayed as highlighted in the Inbox section.
  2. Check that a newly received email has correctly displayed sender emailId or name, mail subject and mail body (trimmed to a single line) and as a display in unread.
  3. Check that on clicking the newly received email, the user is navigated to email content.
  4. Check that the email contents are correctly displayed with the desired source formatting.
  5. Check that any attachments are attached to the email and are downloadable.
  6. Check that the attachments are scanned for viruses before download.
  7. Check that all the emails marked as reading are not highlighted.
  8. Check 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.
  9. Check that count of unread emails is displayed alongside 'Inbox' text in the left sidebar of Gmail.
  10. Check that unread email count increases by one on receiving a new email.
  11. Check that unread email count decreases by one on reading an email ( marking the email as reading).
  12. Check that email recipient in cc are visible to all user.
  13. Check that email recipient in bcc are not visible to the user.
  14. Check that all received emails get piled up in the 'Inbox' section and gets deleted in cyclic fashion based on the size availability.
  15. Check that email can be received from non-Gmail emailIds like - gmail, rediff mail etc.

Comments

Post a Comment

Popular posts from this blog

What is Test case

-
A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of Creating test cases can also help find problems in the requirements or design of a Software. Test Case Format Test scenario id test case id test  case Summary Related Requirement Prerequisites Test Procedure Test Data Expected Result Actual Result Status Comment Created By execution Date Tester Test Environment
Read more

The tester should have skill

-
The tester should have skill A destructive Mindset to crack or crash system under test frequently Bring bad news Under worst time pressure  Need to take a different view, a different mindset  How should fault information be communicated 
Read more

Priority vs Severity

-
High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...
Read more