Assignment 1

Aim:

To write a test scenario for the Gmail login page, ensuring all functionalities and possible edge cases
are covered.

Prerequisite:

 A device with internet access (computer, smartphone, tablet).

 A web browser installed (e.g., Chrome, Firefox, Safari).

 A valid Gmail account for testing.

 Understanding of basic test case writing and software testing principles.

 Access to Gmail's login page (https://mail.google.com).

 Understanding of the expected behavior of a login page (input validation, error handling,
security considerations).

Learning Objectives:

 To understand how to design and write test scenarios for a web application’s login page.

 To learn how to identify different testing aspects such as functionality, usability, security, and
performance.

 To gain insight into handling edge cases and potential user errors during the login process.

 To develop the ability to verify input validation and error messaging.

Theory:

1.1 Introduction:

The login page is a critical component of any web application, serving as the gateway to a user's
personal or business account. Ensuring its reliability and security is paramount. The Gmail login page
is one of the most widely used authentication systems globally, making it essential to thoroughly test
its functionality. This includes verifying that users can successfully log in with valid credentials, that
the system correctly handles invalid inputs, and that security features such as CAPTCHA and two-
factor authentication are functioning correctly.

1.2 Test Scenario Outline:

1. Positive Scenarios:

o User successfully logs in with a valid email and password.

o User logs in with valid credentials and is redirected to their inbox.

o User logs in with valid credentials and a two-factor authentication prompt is

triggered.

2. Negative Scenarios:

o User enters an invalid email format (e.g., "user@domain" without ".com").

 o User enters a correct email but incorrect password.

o User attempts to log in with an unregistered email.

o User leaves the email or password field blank and attempts to log in.

o User enters valid credentials but the account is locked or disabled.

3. Security Scenarios:

o User is prompted with CAPTCHA after multiple failed login attempts.

o Verify that the login page is secured with HTTPS.

o Verify that sensitive information (password) is not displayed in plain text.

o Ensure that after logging out, the user is not able to access the account by pressing
the back button.

4. Usability Scenarios:

o The "Forgot password" link redirects to the password recovery process.

o The login page is responsive and displays correctly on different devices (mobile,
tablet, desktop).

o The email and password fields have appropriate placeholder text and tooltips.

o The "Show password" option works correctly, if available.

5. Performance Scenarios:

o Page load time for the login page is within acceptable limits.

o The login process completes within a reasonable time even under load (e.g., during
peak usage hours).

6. Edge Case Scenarios:

o User enters an extremely long email or password.

o User attempts to log in with spaces before or after the email/ password.

o User logs in during a server maintenance period.

o User logs in after a session timeout and is redirected to the login page.

1.3 Conclusion:

Testing the Gmail login page involves evaluating various aspects, including functionality, security,
usability, and performance. By covering a wide range of scenarios, from positive to edge cases, we
can ensure the login page is robust and secure. Successfully writing and executing these test
scenarios will contribute to the overall quality and reliability of Gmail, providing users with a secure
and seamless experience. This exercise will also enhance the tester's ability to think critically about
different testing aspects and scenarios.
 Assignment 2
Aim:

To write test cases for the Gmail login page, ensuring comprehensive coverage of all functionality,
edge cases, and security aspects.

Prerequisite:

 Access to a device with a stable internet connection.

 A web browser installed (e.g., Chrome, Firefox, Safari).

 A valid Gmail account with correct login credentials.

 Basic knowledge of writing test cases and understanding of web application behavior.

 Access to Gmail's login page (https://mail.google.com).

 Understanding of different types of testing: functional, security, usability, and performance.

Learning Objectives:

 To learn how to design and write detailed test cases for a web application's login page.

 To understand how to test various functionalities, including input validation, error handling,
and security mechanisms.

 To gain insight into how to test the login page for usability and responsiveness across
different devices.

 To develop the ability to identify and document edge cases and negative scenarios
effectively.

Introduction:

The Gmail login page is a critical interface that users interact with to access their Gmail accounts. As
such, it must be reliable, user-friendly, and secure. Testing this page involves checking the
correctness of user inputs, ensuring that error messages are properly displayed, validating security
features, and verifying the page's performance under different conditions. This assignment focuses
on creating detailed test cases that cover all these aspects, ensuring that the login process works as
expected for all possible scenarios.

Test Cases:

Test Case 1: Successful Login with Valid Credentials

 Test Case ID: TC-001

 Preconditions: User has a valid Gmail account.

 Test Steps:

1. Navigate to the Gmail login page.

2. Enter a valid email address in the "Email or phone" field.

3. Click "Next."
 4. Enter the correct password in the "Password" field.

5. Click "Next."

 Expected Result: User is successfully logged in and redirected to the inbox.

 Postconditions: User is logged into their Gmail account.

Test Case 2: Attempt Login with Invalid Email Format

 Test Case ID: TC-002

 Preconditions: None.

 Test Steps:

1. Navigate to the Gmail login page.

2. Enter an invalid email format (e.g., "user@domain") in the "Email or phone" field.

3. Click "Next."

 Expected Result: An error message is displayed indicating that the email format is
incorrect.

 Postconditions: User remains on the login page.

Test Case 3: Attempt Login with Incorrect Password

 Test Case ID: TC-003

 Preconditions: User has a valid Gmail account.

 Test Steps:

1. Navigate to the Gmail login page.

2. Enter a valid email address in the "Email or phone" field.

3. Click "Next."

4. Enter an incorrect password in the "Password" field.

5. Click "Next."

 Expected Result: An error message is displayed indicating that the password is incorrect.

 Postconditions: User remains on the password entry page.

Test Case 4: Login Attempt with Unregistered Email

 Test Case ID: TC-004

 Preconditions: The email address entered is not registered with Gmail.

 Test Steps:

1. Navigate to the Gmail login page.

2. Enter an unregistered email address in the "Email or phone" field.

 3. Click "Next."

 Expected Result: An error message is displayed indicating that the email is not registered.

 Postconditions: User remains on the login page.

Test Case 5: Login with Empty Email or Password Field

 Test Case ID: TC-005

 Preconditions: None.

 Test Steps:

1. Navigate to the Gmail login page.

2. Leave the "Email or phone" field empty and click "Next."

3. On the password entry page, leave the "Password" field empty and click "Next."

 Expected Result: An error message is displayed indicating that the field cannot be left
empty.

 Postconditions: User remains on the same page.

Test Case 6: Security: Verify CAPTCHA Trigger After Multiple Failed Attempts

 Test Case ID: TC-006

 Preconditions: User has attempted to log in with incorrect credentials multiple times.

 Test Steps:

1. Navigate to the Gmail login page.

2. Enter an incorrect password multiple times for a valid email address.

 Expected Result: CAPTCHA is triggered after a certain number of failed attempts.

 Postconditions: User is required to complete CAPTCHA to continue.

Test Case 7: Usability: Check Responsiveness on Mobile Devices

 Test Case ID: TC-007

 Preconditions: Access to mobile devices or a browser with responsive design mode.

 Test Steps:

1. Navigate to the Gmail login page on a mobile device.

2. Enter valid credentials.

3. Click "Next."

 Expected Result: The login page should display correctly and allow successful login on
mobile devices.

 Postconditions: User is successfully logged in on the mobile device.

Test Case 8: Verify Logout and Prevent Back Navigation Access

  Test Case ID: TC-008

 Preconditions: User is logged into Gmail.

 Test Steps:

1. Log out of Gmail.

2. Attempt to use the browser's back button to return to the inbox.

 Expected Result: The user is redirected to the login page and cannot access the inbox.

 Postconditions: User remains logged out.

Conclusion:

Writing test cases for the Gmail login page involves covering all possible scenarios to ensure
functionality, security, usability, and performance. By systematically testing various inputs, handling
edge cases, and verifying security features, we can ensure that the login process is robust and user-
friendly. The exercise of writing these test cases enhances the tester’s ability to think critically about
different testing scenarios and ensures a thorough understanding of the application’s expected
behavior under various conditions.
 Assignment 3
Aim: Test Cases for Social Media Application

Prerequisite:

 A basic understanding of social media platforms and their core functionalities.

 Access to a social media application or website (either a test environment or live

application).

 User credentials for testing purposes (e.g., valid and invalid username/password
combinations).

 Test data like user information, content for posting, and sample media files (images/videos).

 A device (PC, smartphone, or tablet) with internet access.

Learning Objective:

 To understand the critical features of a social media application and how to test them
effectively.

 To gain proficiency in writing comprehensive and detailed test cases that cover various
scenarios within a social media platform.

 To learn how to ensure that the functionalities of a social media application meet the
specified requirements and provide a seamless user experience.

 To be able to identify and document expected outcomes and manage the testing process
effectively using an Excel sheet.

Introduction:

 A social media application serves as a platform for users to connect, share content, and
interact with others online. The application includes functionalities such as user registration,
login, profile management, content creation and sharing, and social interactions like likes,
comments, and shares. Testing these functionalities is crucial to ensure that the application is
user-friendly, secure, and performs well under various conditions.

 This documentation presents a set of test cases designed to verify the key features of a social
media application. These test cases are structured to cover various aspects of the
application, including user management, content interaction, and system behaviors.

Test Cases
Conclusion:

The above test cases are designed to comprehensively test the critical functionalities of a
social media application. By following these test cases, testers can identify potential issues
and ensure that the application delivers a seamless experience to its users. The systematic
approach to testing—covering user registration, login, profile management, content
interactions, and more—ensures that all essential features work as intended, providing
reliability and satisfaction to end-users. This documentation, when used effectively, will
contribute to the overall quality and success of the social media platform.
 Assignment 4
Aim:

To create a defect report for a web application, documenting any issues or bugs identified
during testing.

Prerequisite:

 Access to the web application that is being tested.

 A clear understanding of the application’s expected functionality and behavior.

 Knowledge of defect reporting tools (e.g., Jira, Bugzilla) or a structured format for manual
defect reporting.

 Basic understanding of software testing principles, including the types of defects (functional,
UI, performance, security, etc.).

 A clear test plan and test cases that outline the expected outcomes.

Learning Objectives:

 To learn how to identify, document, and report defects found during the testing process.

 To understand the importance of clear, concise, and detailed defect reports in the software
development lifecycle.

 To develop the ability to categorize and prioritize defects based on their severity and impact
on the application.

 To gain experience in using defect tracking tools or creating structured manual reports that
facilitate effective communication between testers and developers.

Introduction:

A defect report is a crucial document in software testing that communicates issues found in
an application to the development team. It helps ensure that any discrepancies between the
actual and expected behavior of the application are tracked, understood, and resolved. A
well-documented defect report includes details such as the defect ID, description, steps to
reproduce, expected vs. actual results, severity, and any attachments (e.g., screenshots,
logs). This process not only helps in fixing the issue but also in preventing future occurrences
of similar defects.

Example Defect Report:

Defect ID: 001

Defect Title: Login Button Does Not Respond After Entering Valid Credentials

Reported By: [Your Name]

Date Reported: 2024-08-23

Severity: Critical

Priority: High
 Environment:

 Operating System: Windows 10

 Browser: Google Chrome (Version 116.0.5845.96)

 Application Version: v2.1.0

Description: When a user enters valid email and password credentials on the login page and
clicks the "Login" button, the button becomes unresponsive. The user is not redirected to the
dashboard or inbox, and no error message is displayed.

Steps to Reproduce:

1. Navigate to the login page of the application (https://example.com/login).

2. Enter a valid email address in the "Email" field.

3. Enter a valid password in the "Password" field.

4. Click on the "Login" button.

Expected Result: The user should be redirected to their dashboard/inbox after clicking the
"Login" button, indicating a successful login.

Actual Result: The "Login" button becomes unresponsive. The user remains on the login
page, and no error message is displayed.

Attachments:

 Screenshot of the login page after clicking the "Login" button (file attached).

 Browser console log showing any errors (file attached).

Additional Notes:

 The issue was reproduced multiple times on different devices and browsers (e.g., Firefox,
Safari).

 This defect blocks users from accessing their accounts, making it a critical issue that requires
immediate attention.

Status: Open

Assigned To: [Developer's Name]

Resolution: [To be filled by the developer]

Comments:

 [Tester Name]: Please investigate the button click event and ensure that the form submission
is triggered correctly.

 [Developer Name]: Issue identified as a missing event listener. Working on a fix.

Conclusion:

Creating a defect report is an essential task in the software testing process, enabling clear
communication of issues between testers and developers. A well-documented defect report
not only helps in resolving current issues but also contributes to the overall quality of the
application by providing a record of what was tested and what was found. By practicing
defect reporting, testers can improve their attention to detail and their ability to convey
complex issues in a clear and actionable manner. This exercise also emphasizes the
importance of timely and accurate defect documentation in ensuring that software
applications are reliable and user-friendly.
 Assignment 5
Aim:

To install Selenium Grid and Selenium WebDriver with Java in Eclipse IDE for automated web
testing.

Prerequisite:

 System Requirements:

o A computer with Windows, macOS, or Linux operating system.

o Java Development Kit (JDK) installed (version 8 or above).

o Eclipse IDE installed (preferably the latest version).

o Basic knowledge of Java programming.

o An active internet connection for downloading required tools and dependencies.

o A basic understanding of Selenium and automated testing concepts.

Learning Objectives:

 To understand the process of setting up Selenium Grid for distributed web testing.

 To learn how to configure Selenium WebDriver with Java in Eclipse for writing automated
test scripts.

 To gain practical experience in setting up a test automation environment.

 To develop the skills required to execute and manage automated tests across different
browsers and platforms using Selenium Grid.

Introduction:

Selenium is one of the most popular tools for automating web applications for testing
purposes. Selenium WebDriver allows you to programmatically control a browser, and
Selenium Grid enables the parallel execution of tests across multiple machines, browsers,
and operating systems. This setup is crucial for running large-scale test suites efficiently and
ensuring that web applications function correctly across different environments.
 Steps for Installation:

1. Install Java Development Kit (JDK):

 Download JDK: Go to the official Oracle website or OpenJDK to download the latest JDK
version.

 Install JDK: Follow the installation instructions. Ensure that the JAVA_HOME environment
variable is set correctly.

2. Install Eclipse IDE:

 Download Eclipse: Visit the official Eclipse website and download the "Eclipse IDE for Java
Developers."

 Install Eclipse: Follow the installation instructions and launch Eclipse after installation.

3. Install Selenium WebDriver for Java in Eclipse:

 Step 1: Open Eclipse and create a new Java project.

 Step 2: Download the Selenium Java client library from the Selenium official website.

 Step 3: Add Selenium WebDriver JAR files to your project:

o Right-click on your project in Eclipse > Select "Build Path" > "Configure Build Path."

o Click "Add External JARs" and select the downloaded Selenium JAR files.

 Step 4: Set up a basic WebDriver test:


Step 5: Run the test script to ensure that WebDriver is correctly configured.

4. Set Up Selenium Grid:

 Step 1: Download Selenium Server (Grid) from the Selenium official website.

 Step 2: Start the Selenium Hub:

o Open a command prompt or terminal and navigate to the folder containing the
Selenium Server JAR file.

o Run the command: java -jar selenium-server-standalone-x.xx.x.jar -role hub

 Step 3: Set up a Node:

o On the same machine or a different machine, navigate to the Selenium Server JAR
location.

o Run the command: java -jar selenium-server-standalone-x.xx.x.jar -role node -hub

http://localhost:4444/grid/register

 Step 4: Verify the Grid setup by visiting http://localhost:4444/grid/console in a web browser.

5. Integrate Selenium WebDriver with Selenium Grid:

 Modify your WebDriver test script to use Selenium Grid by specifying the RemoteWebDriver:
 Step 6: Run the test and verify that it executes on the configured Grid node.

Conclusion:

By completing this setup, will have a fully functional Selenium environment for automated
testing with Java in Eclipse. This includes the capability to execute tests locally using
Selenium WebDriver and to distribute tests across multiple machines using Selenium Grid.
The skills gained from this exercise will be foundational for any further work in test
automation.