Assignment No.

i) Title
Test Scenario Design for Gmail Login Page

ii) Objective
To understand and apply test design techniques to create comprehensive test scenarios for
a login page, using Gmail as a case study.

iii) Aim
To write effective and realistic test scenarios covering all possible positive and negative
inputs for the Gmail login page.

iv) Requirements
- Internet access
- Any modern browser (Chrome, Firefox, Edge, etc.)
- Gmail account (for testing valid credentials)
- Knowledge of test case and test scenario design
- Pen and paper or test management tool (e.g., Excel, TestLink, Jira)

v) Procedure
1. Open the Gmail login page in a browser.
2. Analyze the UI elements involved in the login process (e.g., Email field, Next button,
Password field).
3. Identify the input conditions and system responses for each UI element.
4. Prepare test scenarios that include:
- Valid and invalid inputs
- Blank inputs
- Special characters
- Field validations
 - UI behavior
5. Document each test scenario clearly with expected results.

vi) Observations
- The Gmail login page has two primary input fields: Email/Phone and Password.
- The login process is two-step: email first, then password.
- Error messages are shown for invalid inputs.
- Fields have input validation checks (e.g., for blank inputs or incorrect formats).

vii) Theory Mathematical model

Software Testing Concepts Used:
- Test Scenario: A high-level documentation of what to test.
- Equivalence Partitioning: Dividing input data into valid and invalid partitions.
- Boundary Value Analysis: Testing input values at the boundary.
- Negative Testing: Testing system behavior with invalid inputs.
- Positive Testing: Testing system behavior with valid inputs.

Software Testing Concepts Used in Gmail Login Page Scenario Design

The process of designing test scenarios for the Gmail login page involves applying
black-box testing techniques and software testing principles to ensure all functional
and boundary conditions are validated. Below are the key theoretical concepts and their
detailed explanations:

1. Test Scenario

A test scenario is a high-level description of what to test. It focuses on the functionality

or feature of the system without going into detailed steps or data. For example:

"Check login functionality with valid credentials."

It helps ensure full coverage of the system’s behavior by identifying “what to test”
instead of “how to test.”
2. Equivalence Partitioning (EP)

This is a black-box test design technique that divides the input data into equivalent
partitions such that the behavior of the application is expected to be the same for each
value in the partition. Only one value from each partition is tested.

For Gmail Email Field:

 Valid Partition: Proper email format like [email protected]

 Invalid Partition:

o abc@ (missing domain)

o @gmail.com (missing username)

o abcgmail.com (missing @ symbol)

This reduces the number of test cases without compromising coverage.

3. Boundary Value Analysis (BVA)

BVA focuses on testing values at the edge of input ranges. It is effective because most
errors occur at boundaries.

For Gmail Password Field:

If the minimum length is 8 and the max is 100:

 Test for 7 (just below min) → Invalid

 Test for 8 (min valid) → Valid

 Test for 100 (max valid) → Valid

 Test for 101 (just above max) → Invalid

This helps catch errors in validations at the boundary conditions.

4. Positive Testing

Positive Testing is done to verify that the application behaves correctly with
expected/valid inputs.

Example:

 Enter valid email and password → Expect successful login

 Check "Forgot password" link → Should navigate to recovery

It ensures the basic functionality works as intended.

5. Negative Testing

Negative Testing is the process of applying invalid or unexpected inputs to ensure the
system handles them gracefully (i.e., displays appropriate error messages, doesn’t crash).

Examples:

 Enter an empty email → Should show "Enter an email"

 Use invalid email format → Should show "Invalid email"

 Wrong password → Should show "Wrong password" error

This validates the robustness and error handling capacity of the system.

6. Error Guessing

Based on the tester’s experience, certain test scenarios are guessed where the system is
likely to fail.

Example Guesses:
  Use SQL keywords in the email field to test for SQL injection

 Use JavaScript code to test for XSS attacks

 Paste copied email with trailing space

These scenarios help uncover security or usability flaws.

7. State Transition Testing

The Gmail login is a multi-step form (two pages: email → password). Each step
represents a state, and input actions trigger transitions between them.
States:
 Email page (Initial)
 Password page (on valid email input)
 Inbox (on correct password)
 Error messages (on invalid entries)
Transition Examples:
 Invalid email → Remain in email state with error
 Valid email → Move to password state
 Wrong password → Stay in password state with error
 Valid login → Move to inbox state
viii) Conclusion
Test scenario design helps ensure all aspects of a feature are validated.
Writing scenarios for the Gmail login page covered a wide range of functional,
validation, and UI-based checks that are crucial for ensuring a robust login mechanism.

ix) Oral Questions

1. What is the difference between a test case and a test scenario?
2. What are positive and negative test scenarios?
3. What happens when you enter an invalid email in Gmail login?
4. What is equivalence partitioning?
5. Why is boundary value analysis important?
6. How does Gmail handle incorrect password entries?
7. Can a test scenario be automated?
8. What is UI validation in login pages?
9. What are the common validations used in login forms?
10. Why is writing test scenarios important before coding?

x) Results
Scenario No. Test Scenario Expected Result
TS01 Enter valid email and password Login successful – Inbox
opens
TS02 Leave email field blank Show error: "Enter an
email or phone number"
TS03 Enter invalid email format (e.g., abc@) Show error: "Couldn't find
your Google Account"
TS04 Enter valid email and wrong password Show error: "Wrong
password. Try again."
TS05 Enter valid email and leave password Show error: "Enter your
blank password"
TS06 Enter email with special characters Show error: "Enter a valid
email"
TS07 Verify "Forgot email?" and "Forgot Navigate to respective
password?" links recovery pages
TS08 Check browser back button behavior Should not return to
password page once logged
in
TS09 Check visibility toggle of password Should show/hide
field password correctly
TS10 Attempt login with deactivated Gmail Show account disabled
account error