Gmail Test Cases [ Login, Sign Up Page, Inbox & Compose ]

Gmail Test Cases In Excel Sheet Of Compose Mail, Login Page, Gmail Inbox & Registration Page: In this post, we will discuss some of the test cases for the Gmail application, and we will also share test cases for Gmail in an Excel sheet. If you can only imagine the Gmail application, you will find many modules there, and you can write separate test cases for each module. For Example, test cases for compose mail, the test cases for Gmail login page in an excel sheet, test cases for Gmail inbox, test cases for Gmail registration page, Gmail sign-up test cases, test cases for sending email,

But below, we will see some test cases for only the Gmail application’s most common functionalities. We limit the test scenarios to receiving email and composing mail functionalities only. For login and Registration functionality test cases, users can check Test Scenarios for the Login Page and Test Scenarios for the Registration Page.

Post On:Test Case For Gmail
Post Type:Test Case
Applicable For:Freshers & Experience
Never Miss To Join:Telegram Group

Before writing about any test scenario, try first to find out a few things like:

  • What are the elements of that screen?
  • Write a Test case on each object.
  • Try to find out all possible positive & negative test scenarios.
  • Also, try to cover all types of test cases like functional & non-functional test cases.

If you have a mock of the screen of the requirement, then it will be easy for you to find out all the elements easily. But you never get this chance; at that time, you have to think of yourself.

Test Cases For Gmail

Gmail Test Cases [ Login, Sign Up Page, Inbox & Compose ] 1

Gmail Sign-Up Test Cases

  • Check if all fields are on the page as per the requirement document.
  • Check that all the compulsory fields are marked with *.
  • Check for a better user experience checkbox, radio button & dropdown are used on the Gmail registration page.
  • Check the position of the reset, submit, and cancel buttons location.
  • Check after filling in all mandatory fields. If the user hits the submit button, then that should be sent to the server.
  • Check after filling in all the fields. All field values should be cleared if the user clicks the reset button.
  • Check Validation messages are displaying as per the input values on the client side.
  • Check without filling in all the mandatory fields. If the user clicks on the submit button, then missed compulsory fields should be highlighted with red, and a validation message should be displayed.
  • If the user leaves some optional fields blank and clicks the submit button, the filled data should be forwarded to the server without displaying any error.
  • Check the maximum allowed characters for the input fields.
  • Check only valid dates; emails only allow for the Date and email fields.
  • Check for the input fields leading, and trailing space is trimmed automatically.
  • You should get a validation error message if you submit the same request to the server multiple times.

Test Scenarios For Gmail Sign-In Page

Gmail Login Screen Test Scenario
Gmail Login Screen Test Scenario
  • Check if the login screen has all the elements like username field, password field, submit button & forget password links present as per the specification document. [ Check Forget Password Test Case and Test Cases For Password Field ]
  • Check whether the cursor is blinking on the email field by default.
  • Check whether any email validation functionality is available for the email field. [ You can get the Complete Test Cases For the Email Field Here ]
  • Check if the user can log in successfully after entering a valid username and password.
  • If a user enters an invalid username or password, then the user should not be able to log in.
  • Check whether validation messages are displayed correctly based on the input values.
  • Check all the filled values of the user name and whether the password field is clear after clicking the reset button.
  • Check the password field values are displayed in masked formats like asterisks or bullets.
  • Check if there is any limit for unsuccessful attempts.
  • Check if there is any session time-out present for a login user.
  • Check what the time-out duration for the login screen is.
  • Check if the username and password field values can be copied or not.
  • Check if the right-click functionality is disabled or not on the login screen.

Test Cases For Gmail Inbox

Now, we will discuss the possible scenarios when you receive an email.

  • Check that the recently received unread email is highlighted and bold in the Inbox section.
  • Check if all the elements of the received email are correctly displayed or not.
  • Check whether the user clicks on the new email; it redirects the user to the email content.
  • Check if the email content is displaying in the proper format or not.
  • Check the attached documents of the email are downloadable.
  • Check the already-read emails should not be the highlight.
  • The number of unread email counts should be displayed beside the inbox text box.
  • Check if the count is increased per the number of new emails you have received.
  • Check the count is increased when you mark an email as unread.
  • Check after opening or make as read an email. The count should be decreased.
  • Check the names are visible to all the users whose names are present in the CC & To section.
  • Check those names or emails are present in the BCC section and should not be displayed to others.
  • You can receive emails from other domains like Yahoo, Outlook & Hotmail.

Test Cases For Compose Mail

  • When the user clicks the compose email button, a new popup should be displayed with the headers as a new message.
  • Check the user’s ability to enter email ID in the TO, CC, and BCC Sections.
  • Check whether the auto-suggestion list of previously entered email IDs is displaying when filling out the email.
  • Check if multiple commas can separate multiple email IDs of TO, CC, and BCC sections.
  • Check the user can enter the subject line in the subject text box.
  • Check the user can type in the email body area.
  • Check users can format the email body content by using the editor options.
  • The check is the user can add files in the attachment section.
  • The check is the user can add images in the email body area.
  • Check all the users who received the emails whose email IDs are mentioned in the TO, CC & BCC sections.
  • Contact information should be displayed when the user places the mouse hovers on the email id.
  • After hitting the send button, the recent send mail should be displayed in the sent mail section.
  • Check after hitting the send button. The email should also be delivered successfully to the NON-Gmail ID.
  • After composing the email, if not sent, then it should be stored in the Draft section.
  • Check the maximum number of email IDs that can be added in the TO, CC & BCC sections.
  • Check the maximum number of characters allowed in the email body area.
  • Check the maximum number of characters allowed in the subject text box.
  • Check the maximum size of the attached file in the email.
  • Check the maximum number of the attached files in an email.
  • Check if special characters are entered mistakenly in the TO, CC, or BCC section, and when you hit the send button, an error popup should be displayed.
  • Check if the subject is not filled; when you enter the send button, it should display that time. After accepting the popup, the user can enter the subject of the email.

Negative Test Cases For Gmail

  • Verify that a different password in the confirm password field is working fine.
  • Verify that as we hit the next Button without entering the User name, then check if it works.
  • Verify that as we hit the next Button without entering the date of birth, then check if it works.
  • Verify that as we hit the Verify Button without entering the verification code, then check if it works.


You can also get the Gmail Integration Test cases for the Gmail Application. You can also go through this for a better understanding of the application.

Final Words

We are trying to cover some primary and standard functionalities for the login screen, registration page, and inbox, as well as compose the email functionalities.

But Still, we believe you can find so many other missed scenarios. If you want to add it, you can add it in the comment section, and we will update you on this Gmail Application Test Case accordingly.

I love open-source technologies and am very passionate about software development. I like to share my knowledge with others, especially on technology that's why I have given all the examples as simple as possible to understand for beginners. All the code posted on my blog is developed, compiled, and tested in my development environment. If you find any mistakes or bugs, Please drop an email to, or You can join me on Linkedin.

6 thoughts on “Gmail Test Cases [ Login, Sign Up Page, Inbox & Compose ]”

  1. Adding one more Test scenarios for Compose mail Functionality
    – Verify the contact information by hovering mouse on E-mail id’s.

  2. verify new message can also be saved in drafts
    verify close ,minimize,maximize new message pop-up
    verify Schedule Send
    verify failed delivery if email id is wrong

  3. verify minimize,maximize and close new message option
    verify failed delivery message is generated
    verify schedule send option
    saved mails stored in drafts
    can send option have separate test scenarios or included in compose functionality??


Leave a Comment