Test Case For Gmail Login Screen Page Test Case
This article explains test cases both negative and positive for the login screen. I’m taking an example of the Gmail login screen. If you want you can take the example of WordPress or Yahoo login screen or any other of your choice. The positive and negative scenarios depend on the information given the requirement document.
As we are testing Gmail login screen we are limited to the application which is already published with a limited set of information available to test. So our best approach is exploratory testing of the web app.
|Test Scenario Overview|
|Post On:||Test Case For Gmail login screen|
|Post Type:||Test Case Template|
|Applicable For:||Freshers & Experience|
I’m laying down a process which you can follow in order to come up with a login screen test cases. First, we’ll write the test requirements based on our exploratory testing observation and after that, we’ll write the test scenarios and then form the negative and positive test cases. If you want to use existing testing templates and test cases, I suggest you check these templates out.
You can make use of following login screen of Gmail for your testing.
Gmail Test Requirements
As we don’t have the official Google requirements for the login screen. We’ll come up with our own requirement set for the login screen. We’ll write the scenario based on these requirements.
- Username should contain a letter, number and period.
- Username should not be left blank.
- Username should not be more than 40 characters.
- Username should not start with or contain any symbols.
- The password should be at least 6 characters.
- The password should contain a combination of letter, numbers, and symbols.
- The password should not contain spaces and period.
- The password should not be more than 40 characters.
Gmail Test Scenarios
Write down the test scenarios based on the following test types:
|Related Test Cases|
|☑️ Test Case For Login Attempts||☑️ Test Case For Login Page|
|☑️ Test Case For Logout||☑️ Test Case For Microwave Oven|
Outlook User Interface
You can check out the new Outlook interface and see how the interface has changed over the years.
Here are some of the questions that can help you form test cases.
- Where is the cursor focus in the text area when you load the page?
- Does enter key works as a substitute for the sign-in button action?
- Does the username and password text field appear in order?
- Does remember me checkbox selected by default?
- Does the login page has register link for new users?
- Does the user interface look as per the design specification?
- Does login screen behave responsively to mobile or tablet screen?
- Do the link on the page remain active or are dead?
Outlook Functionality Testing
Login screen functionality varies with each type of application. So there is going to be a difference between Yahoo login and Gmail login. Here are some general possible functionality scenarios.
Take the example of Lycos mail how they are not paying attention to functionality issues.
- Does the login form works successfully?
- Is logout link redirects back to the login screen? Is logout link functional?
- Does forgot password link works? Does it redirect to the valid password recovery page?
- Do forward and backward buttons work properly while logged in? and also for logged out the user?
- Does formwork similarly in every popular browser?
- How errors are handled and displayed?
Outlook Security Testing
Security of the form is very crucial and you can use the following scenarios to form your test cases. Take a look at how the Outlook handles bad username and passwords security issue.
So let’s take those cases into consideration.
- Does textbox offer masking of characters in the password field?
- Do masked characters allow deciphering if copied?
- Is it possible to copy and paste the password?
- is there any minimum password length?
- is the form giving away security information if the source is viewed?
- is the form vulnerable to SQL injection?
- Does form allows accessing pages without logging in?
- is URL manipulation allows access to the members-only area of mail?
- is multiple accounts from the same IP but different browser allowed at the same time?
- are cookies allowed? are they disabled or allowed to be edited?
Once you go through these scenarios, you need to come up with the following possible positive and negative test cases.
Gmail Login Screen Positive test cases
- Enter a valid username and password.
- Click on forgot password link and retrieve the password for the username.
- Click on the register link and fill out the form and register username and password.
- Use enter button after typing correct username and password.
- Use tab to navigate from username textbox to password textbox and then to the login button.
Gmail Login Screen Negative test cases
- Enter a valid username and invalid password.
- Enter valid password but invalid username.
- Keep both field blank and hit enter or click the login button.
- Keep username blank and enter a password.
- Keep the password blank and enter a username.
- Enter username and password wrong.
The more you know about the form requirement and developed page, the more scenarios that you can come up with to test the Gmail login screen thoroughly. There are going to be plenty of combinations but that would require more time to test and exhaustive testing is not practical though possible.
Security Testcases for Login Window
- Invalid Username/password
- Password encryption (Encrypted Password cannot be copy-pasted in notepad)
- Forgot Password Link
- Valid login name/email id for forgot password or contact administrators
- Checking cookies for username/password
- Number of invalid attempts for username/password
- Remember me(for password)
- In case of financial application (like Bank – Captha, virtual keypad etc.., for ATM – Pin etc..)
- Access Control
- SQL Injection
- Check the Admin rights to delete the already logged in user.
Following are some test cases that you may want to execute to check the login level security of any web application:
- Check if the user can access the secured area of the application without proper login.To do this, you may book mark, add to favourite or copy the URL of any secured area page and then run the URL directly without login.Application should not allow the access to the secured area in this case.
- Check if the user can work with the secured area page, that is accessed by using browser’s BACK button, after log out the application.Proper info message should be displayed in this case mentioning that user needs to be logged in the application.
- Check if the user can work in secured area after session time is out.
- Check if multiple users, with the same login ID & password can access the application.
In Security Testing you will also check for below:
- Check data is travel in network in plain text or Encrypted form
- Check data encryption for login id & Password is fixed encryption or random encryption
- Check if you are using Certificated, that certificate will follow trust chain or not
- Log File for both web page & database
- Client side validation is required for each text filed
- Error Message does not contain malicious info so that hacker will use this information to hack web site
|Tasks To Improve Your Knowledge|
|☑️ Test cases for login page Xls||☑️ Test cases for login page in excel sheet pdf|
|☑️ Test case for login page positive and negative||☑️ Test cases for password and confirm password|
|☑️ Test cases for submit button||☑️ Password test cases|
|☑️ Test cases for Gmail in Excel sheet||☑️ Forgot password test cases|
|Let We Inform you, For improves your knowledge you can take the above as a task and you can work on that. But from the above task list some of the tasks we have already completed and you can find those on our blog. After Completion if you want to share with us that then you can write to us at firstname.lastname@example.org.
In return for that maybe we plan something more surprising for your career.
So you have to choose the test cases which are more important for the product risk. I hope you have found value in this information. Feel free to let me know if you need more information or have any suggestions.