INDEX

Sl. Name of the Experiment Page Signature

Date
No No.

1 Develop the test plan for testing an

e-commerce web/mobile application
(www.amazon.in).

2. Design the test cases for

testing the e-commerce
application
3. Test the e-commerce application and
report the defects in it.

4. Develop the test plan and design the

test cases for an inventory control
system.
5. Execute the test cases against a client
server or desktop application and
identify the defects.

6. Test the performance of the e-

commerce application.

7. Automate the testing of e-commerce

applications using Selenium.

8. Integrate TestNG with the above test

automation.
EXP1: Develop the test plan for testing an e-commerce web/mobile
application (www.amazon.in).

AIM: To develop the test plan for testing an e-

commerce web Test Plan: Manual Testing of Amazon
Website

1. Product Analysis:

● Understand the Amazon website's main features: product search,

product details, shopping cart, checkout, user authentication, etc.

● Analyse the user journey: browsing, searching, adding to cart, checking

out.Identify key functionalities, potential areas of risk, and areas that

require special attention.

2. Designing Test Strategy:

● Focus on functional testing, usability testing, and compatibility

testing.Prioritise testing based on critical user flows and high-risk

areas.

● Consider exploratory testing to uncover unexpected issues. Use real

user scenarios to simulate realistic interactions.

3. Defining Objectives:

● To Ensure that all core features of the Amazon website are working as

expected.To Identify and report defects, ensuring they are resolved

before launch.

● To Evaluate the user experience, usability, and responsiveness of the

application.To Verify compatibility with different browsers and devices.

4. Establish Test Criteria:

● Functional: All core features must work without errors or unexpected behaviour.

● Usability: User interface elements must be intuitive and user-friendly.

● Compatibility: The website should work across popular browsers

(Chrome, Firefox, Safari) and devices (desktop, tablet, mobile).

5. Planning Resource Allocation:
 ● Assign roles: Tester (student), Test Lead (instructor).

● Determine the resources required for documentation and

communication.Allocate time for testing, defect reporting, retesting,

and test case development.

6. Planning Setup of Test Environment:

● Environments: Use development and staging environments provided by Amazon.

● Browser and device combinations: Choose common combinations

for testing compatibility.

7. Determine Test Schedule and Estimation:

● Test Planning & Test Case Development: 3 days

● Functional Testing : 5 days, Usability Testing: 2 days, Compatibility Testing: 3 days

● Defect Reporting and Retesting: Ongoing throughout testing phases.

8. Establish Test Deliverables:

● Test Cases: Detailed test scenarios for functional and usability testing.

● Defect Reports: Detailed descriptions of identified defects with steps to reproduce.

● Test Summary Report: Summary of testing activities, results, and coverage.

9. Communication and Reporting:

● Regular updates to the Test Lead on progress, issues, and

challenges.Defect reports submitted to developers for resolution and

retesting.

10. Review and Update:

● Regularly review and update the test plan based on changes in

requirements or issues identified during testing.

RESULT : Thus the test plan is successfully verified and executed .

EXP2: Design the test cases for testing the e-commerce application

AIM: To design the test cases for testing the e-commerce

application Test Cases for Amazon Website:

1. Product Search:

Test Case 1: Verify Basic Product Search

❖ Description: Test if users can search for products using the search bar.
❖ Steps:
➢ Navigate to the Amazon website.
➢ Enter a valid product name in the search bar.
➢ Click the "Search" button.
❖ Expected Result: Search results page with relevant products are displayed.
Test Case 2: Verify Advanced Product Search
❖ Description: Test if users can use advanced filters during product search.
❖ Steps:
➢ Navigate to the Amazon website.
➢ Enter a product name in the search bar.
➢ Apply filters like category, price range, and rating.
➢ Click the "Search" button.
❖ Expected Result: Search results match the applied filters.

2. User Authentication:

Test Case 3: Verify Login with Valid Credentials

❖ Description: Test if users can successfully log in with valid credentials.
❖ Steps:
➢ Navigate to the Amazon website.
➢ Click on the "Sign In" button.
➢ Enter valid email and password.
➢ Click the "Sign In" button.
❖ Expected Result: User is successfully logged in and redirected to the home page.
Test Case 4: Verify Login with Invalid Credentials
❖ Description: Test if users receive an error message for invalid login attempts.
❖ Steps:
➢ Navigate to the Amazon website.
➢ Click on the "Sign In" button.
➢ Enter an invalid email or password.
➢ Click the "Sign In" button.
❖ Expected Result: Error message is displayed indicating invalid credentials.

3. SHOPPING CART AND CHECKOUT:

Test Case 5: Verify Adding Product to Cart

❖ Description: Test if users can add products to the shopping cart.
❖ Steps:
 ➢ Navigate to the Amazon website.
➢ Search for a product.
➢ Click on a product.
➢ Click the "Add to Cart" button.
❖ Expected Result: Product is added to the cart and cart count is updated.
Test Case 6: Verify Cart Checkout Process
❖ Description: Test if users can proceed through the checkout process.
❖ Steps:
➢ Navigate to the Amazon website.
➢ Click on the shopping cart icon.
➢ Review cart items and click "Proceed to Checkout."
➢ Provide shipping address and payment information.
➢ Click "Place your order."
❖ Expected Result: Order confirmation page is displayed, confirming
the order placement.

RESULT : Thus the test cases are successfully verified and executed .
EXP3: Test the e-commerce application and report the defects in it.

AIM: To test the e-commerce website and to report the defects in it.

PROCEDURE:
To find defects in an e-commerce website through manual testing,
begin with a structured approach. First, thoroughly review the website's
requirements and specifications to gain a clear understanding of its expected
behaviour. Next, devise comprehensive test cases covering critical functions
such as product search, cart management, and checkout processes. Execute
these test cases systematically, recording any discrepancies between the
expected and actual outcomes. Pay special attention to user interface
elements, navigation, and data handling. Keep detailed defect logs, including
issue descriptions, steps to reproduce, and screenshots for clarity.
Additionally, perform usability testing to evaluate user-friendliness and
responsiveness across different devices and browsers. Conduct security testing
to identify vulnerabilities like data leaks or injection risks. Verify
compliance with data privacy regulations and test for localization and
accessibility to ensure a broader user reach. Assign severity and priority levels to
each defect discovered, facilitating efficient resolution. Finally, document all
defects using a standard defect reporting template, sharing these reports with
the development team for prompt resolution. Continuous feedback and iterative
testing are key to enhancing the e-commerce website's quality and reliability.

OUTPUT:

BUG 1 :
An issue has been identified where the product 'pencil case' displays a single
image, but the accompanying images shown are of an unrelated product,
'bathrobe”. This inconsistency is categorised as a bug due to its deviation from
expected behaviour.
BUG 2 :
An issue has been identified where a product lacks a preview image. This is
categorised as a bug since a preview image is a fundamental component of the
user interface and essential for users to make informed decisions when browsing
or shopping on the platform. The absence of a preview image can negatively
impact the user experience, as customers rely on visual cues to assess a
product's appearance and make purchasing decisions. Therefore, this bug should

be addressed promptly to ensure the website's functionality and usability.

BUG 3 :
A bug has been identified in the search functionality of the system. Specifically,
when a user enters a search query like 'Pastel Highlighter Set,' the search engine
automatically alters it to 'Pastel + Highlighter + Set.' It's important to note that
while this modification does not affect
the accuracy of search results, it represents an inconsistency in the search box
behaviour. The user's original query should ideally be retained as entered. This
alteration in the search query format is considered a bug as it deviates from
expected user input handling.

BUG 4:
An issue has been identified in the application of filters on the platform.
Specifically, when the 'College Books' filter is applied, the search results include
'Colouring Book for Kids,' which is not aligned with the selected filter criteria.
This inconsistency in the filter's functionality is categorised as a bug. Filters are
designed to refine search results based on specific user preferences, and this
deviation from expected behaviour may lead to user
confusion and misrepresentation of available products. Therefore, it is
imperative to address this bug to ensure accurate and coherent filtering within
the platform.

BUG 5 :
A bug has been identified in the behaviour of the filter button located adjacent
to the search box. When a user sets a specific filter, such as 'Baby,' and
conducts a search, the filter is automatically changed to 'All' irrespective of the
search query. Consequently, the displayed results do not align with the user's
selected filter preference. For instance, if a user selects 'Baby' as the filter and
performs a search for 'Oil,' the filter is reset to 'All,' and the results may include
unrelated products like 'Food Oil' instead of 'Baby Oil.' This inconsistency in
filter retention is considered a bug, as it disrupts the expected functionality of
filters and may lead to user dissatisfaction and difficulty in locating desired
products. It is crucial to address this issue promptly to ensure that filters remain
set as per the user's selection.
BUG 6:
In the context of the platform's filtering system, a defect has been identified
when applying price filters. Specifically, when a user selects a price filter, such
as 'Below 250,' products with prices exceeding this limit are still displayed in the
search results. This discrepancy between the applied filter and the actual results
is considered a bug. Filters serve as essential tools for users to refine product
searches based on specific criteria, in this case, price. When the system fails to
accurately restrict results according to the chosen filter, it compromises the
reliability of the filtering feature, potentially leading to user frustration and
misrepresentation of product availability. It is essential to rectify this issue to
ensure consistent and accurate filtering functionality across the platform.

BUG 7 :

An issue has been identified within the platform's filtering functionality,

specifically the absence of a filter category for stationary items. This gap in the
available filters is considered a bug from a user's perspective. Filters are vital
tools for users to efficiently narrow down product searches based on specific
criteria, such as product category. The absence of a 'Stationary' filter means that
users looking for stationary items may encounter difficulties in easily locating
and browsing through this specific category. This oversight can lead to a
less-than-optimal user experience, as users may need to sift through a broader
range of unrelated products. Addressing this bug by introducing a 'Stationary'
filter will enhance user convenience and improve the overall usability of the
platform.
BUG 8 :
In the context of product presentation within the system, a discrepancy has been
identified where the product named 'Test Data' is associated with an image
depicting a bracelet.
Notably, this product is categorised under 'Computer Accessories.' This
incongruence between the product name, image, and categorization is reported
as a bug. It results in a misalignment between product representation and
categorization, potentially leading to user confusion and misrepresentation of
available products.

BUG 9 :
There is a detected issue where the 'Sort by' option has been set to 'Low to High'
price, but the displayed prices are not in the expected ascending order. This
deviation from the anticipated behaviour is identified as a bug. However, the
current sorting implementation
results in mixed-up prices, which can lead to user frustration and
misrepresentation of product affordability.

Bug 10:
In the context of user navigation within the platform, a notable issue has been observed when
transitioning from the homepage, featuring promotional offers for 'Airpods,' to the dedicated 'Airpods'
section. Upon reaching the 'Airpods' section, the filter bar displays product categories, but it does not
include a filter option specifically related to 'Airpods' products. This inconsistency is classified as a
bug.

RESULT : Thus the defects have been reported and reviewed successfully .
EXP4: Develop the test plan and design the test cases for an inventory control
system.

AIM: Develop the test plan and design the test cases for an
inventory control system.

Test Plan for Inventory Control System

1. Introduction
● Purpose: This test plan outlines the testing approach for the
Inventory Control System.
● Scope: The testing covers all critical functionalities of the system,
including inventory management, order processing, and reporting.
● Objectives: To verify that the system operates correctly,
efficiently manages inventory, and produces accurate reports.
2. Test Strategy
● Testing Types: The testing will include functional testing,
usability testing, performance testing, and security testing.
● Testing Environment: Describe the testing environment, including
hardware, software, and network configurations.
● Test Schedule: Provide a timeline for testing activities, including start and end
dates.
3. Test Deliverables
● List the documents and reports to be produced during testing, such as
test cases, test reports, and defect logs.
4. Test Scope
● Identify the features and functionalities to be tested, including
inventory tracking, order placement, order processing, and reporting.
5. Test Cases
● Define the test cases for each identified functionality (see below).
6. Test Execution
● Describe how tests will be executed, including test data, test
environments, and the personnel responsible for conducting tests.
7. Defect Management
● Explain the process for reporting and tracking defects, including severity
and priority levels.
8. Risks and Assumptions
● Identify potential risks and assumptions related to the testing process.

Test Cases for Inventory Control System (i.e., GMAIL)

1. Login Test:
a. Objective: Verify that users can successfully log in to their Gmail account.
b. Steps:
i. Open the Gmail login page.
ii. Enter valid username and password.
iii. Click the 'Sign In' button.
 c. Expected Result: The user should be logged into their Gmail
account and directed to the inbox.
2. Compose Email Test:
a. Objective: Ensure that users can compose and send emails.
b. Steps:
i. Log in to Gmail.
ii. Click the 'Compose' button.
iii. Fill in the recipient's email address, subject, and message.
iv. Click 'Send.'
c. Expected Result: The email should be sent successfully, and the
sent email should appear in the 'Sent' folder.
3. Attachment Test:
a. Objective: Verify that users can attach files to emails.
b. Steps:
i. Compose a new email.
ii. Click the 'Attach' button.
iii. Select a file to attach.
iv. Send the email.
c. Expected Result: The email should be sent with the attached
file, and the recipient should be able to open the attachment.
4. Spam Filter Test:
a. Objective: Ensure that the spam filter effectively identifies and
moves spam emails to the spam folder.
b. Steps:
i. Send a known spam email to the Gmail account.
ii. Check the spam folder for the email.
c. Expected Result: The spam email should be detected and placed in
the spam folder.
5. Search Test:
a. Objective: Verify that the search functionality works correctly.
b. Steps:
i. Log in to Gmail.
ii. Enter a keyword in the search bar.
iii. Click 'Search.'
c. Expected Result: Relevant emails containing the keyword
should be displayed in the search results.

RESULT : Thus the test plan and test cases are successfully developed and reviewed .
EXP5:Execute the test cases against a client server or desktop application
and identify the defects.

AIM: Execute the test cases against a client server or desktop

application and identify the defects.

Test Cases:
● Login Functionality
○ Test Case 1: Verify that a user can log in with a valid Gmail account.
○ Test Case 2: Verify that login fails with an invalid password.
○ Test Case 3: Verify that login fails with an invalid username.
● Email Composition
○ Test Case 4: Compose a new email and send it to a valid recipient.
○ Test Case 5: Compose a new email and attach a file to it.
○ Test Case 6: Verify that email composition is not allowed without entering a
recipient's email address.
● Inbox Functionality
○ Test Case 7: Check the inbox for new emails.
○ Test Case 8: Open an email from the inbox.
○ Test Case 9: Delete an email from the inbox.
● Search Functionality
○ Test Case 10: Search for a specific email by subject.
○ Test Case 11: Search for emails from a specific sender.
○ Test Case 12: Search for emails containing specific keywords.
● Attachments and Download
○ Test Case 13: Open an email with an attachment and download the
attachment.
○ Test Case 14: Verify that the downloaded attachment can be opened
successfully.
Procedure:
● Open a web browser and navigate to the Gmail website (https://mail.google.com/).
● Log in to your Gmail account using the provided credentials or your test account.
● Execute each test case as described in the lab manual, following the
steps meticulously.Note any unexpected behaviour, errors, or defects
encountered during the test execution.

Defect Identification:
● Defect 1: In Test Case 10, searching for emails by subject does not
return the expected results.
● Defect 2: In Test Case 12, searching for emails by subject does not
return the expected results.
● Defect 3: In Test Case 14, The attachment download process encounters
an error. When attempting to open the downloaded attachment, an
error message appears, indicating that the file is corrupted or
inaccessible.

RESULT : Thus the test cases are successfully executed and reviewed .
EXP 6 :Test the performance of the e-commerce

application. AIM: To test the performance of the e-

commerce application PROCEDURE :

1. Product Search:

Following are the steps for defining a JMeter Test Plan for Product Search thread:

Step 1: Add one thread group inside test. Name that thread group as “Product Search”.

Step 2: Then add User Defined Variables and HTTP request defaults Config elements.

User Defined Variables to be added are as follows:

Name of Variable Value of Variable

VARIABLE_VALUE_OF_PRODUCT ${ P(VARIABLE_VALUE_OF_PRODUCT)}

VARIABLE_VALUE_OF_PRODUCT_NA ${ P(VARIABLE_VALUE_OF_PRODUCT_NAM

ME E)}
 COUNT ${ P(COUNT, 0)}

PRODUCTS_STRING ${ P(PRODUCT_STRING,Micro Chrome

Widget&Tiny Chrome Widget)}

CATEGORY_STRING ${ P(CATEGORY_STRING,Gizmos&Widgets)}

Step 3: Add one loop controller (with loop count of 2) for iterating each thread for

searching products two times. Inside the loop controller, add one HTTP request

sampler to hit the main page of eCommerce site (Url: /ecommerce/control/main).

Step 4: Add one BeanShell PostProcessor to randomize the product search and

category search in the thread. Do it as shown in following picture:

Step 5: Add if controller inside loop based on the value of

“KEYWORD_OR_CATEGORY” variable generated in last step.

If this variable is “1” then go for keyword search and if “2” then go for category search.

Step 6: Add one HTTP request sampler with path /ecommerce/control/keywordsearch

and POST data request to go for keyword search. Parameters to be posted are as

follows:
 Parameter Name Value of Parameter Details about

parameter

SEARCH_STRING ${VARIABLE_VALUE_OF_PRODUCT} This value will

dynamically

fetched using

BeanShell

script and user

defined

variables

VIEW_SIZE 10 Number of

results per

page

PAGING Y Flag for

pagination

SEARCH_CATEGORY_ID CATALOG1_SEARCH

SEARCH_OPERATOR OR

Step 7: Add the following BeanShell script inside keyword search request to

manipulate the loop count and string to be searched dynamically.

String productListInString = vars.get( "PRODUCTS_STRING"

).toString(); String[] productListArray =

productListInString.split( "&" );

int productListLength = productListArray.length;

Random random = new Random();

int count = random.nextInt(productListLength);

if (count > productListLength)

{ count = 0 ;

vars.put( "VARIABLE_VALUE_OF_PRODUCT" ,

productListArray[count]); print( "Product" +

productListArray[count]);

Step 8: Add one Regular expression extractor to extract the value of the product

page url from the rendered page after search result to hit the product page. It

should be stored into the

“VARIABLE_VALUE_OF_PRODUCT” variable.

Step 9: Add HTTP request sampler with the path value

/ecommerce/${VARIABLE_VALUE_OF_PRODUCT_NAME}. It will redirect request to the

product detail page.

Step 10: The case is the same for the category search. Only difference in category

search is we pickup category url from main page itself and randomize the category

page visits by using BeanShell script.

Step 11: After that we add some pause timer and then we stop the thread. Total

structure and BeanShell of randomizing the category page url will look like the

following picture:

RESULT : Thus the test performance of the e-commerce application has

been successfully reported.
EXP 7 : Automate the testing of e-commerce applications using Selenium.

AIM: To automate the testing of e-commerce applications.

EXP 7.1 : Locators of selenium : ID

AIM:To Implement automated testing for e-commerce platforms

using the ‘ID’ locator in Selenium.

ALGORITHM :

Step 1: Download Web Driver for

chrome. Step 2: Import necessary
modules.
Step 3: Initialize
WebDriver. Step 4: Open
Website.
Step 5: Find Search Bar.
Step 6: Clear Search Bar.
Step 7: Enter Search
Query. Step 8: Submit
Search Query. Step 9:
Print Current URL. Step
10: Close Browser.

SOURCE CODE :
from selenium import webdriver
from selenium.webdriver.common.keys
import Keys from
selenium.webdriver.common.by import By
import time
driver = webdriver.Chrome()
driver.maximize_window()
driver.get("https://www.amazon.in/")
search_bar = driver.find_element(By.ID,"twotabsearchtextbox")
search_bar.clear()
search_bar.send_keys("slipper")
time.sleep(5)
search_bar.send_keys(Keys.RETURN)
print(driver.current_url)
driver.close()
OUTPUT:

RESULT : Thus the program is successfully executed and output is verified.

EXP 7.2 : Locators of selenium : LINK TEXT

AIM: To Implement automated testing for e-commerce platforms

using the ‘Link Text’ locator in Selenium.

ALGORITHM :

Step 1: Download Web Driver for

chrome. Step 2: Import necessary
modules.
Step 3: Initialize
WebDriver. Step 4: Open
Website.
Step 5: Find Search Bar.
Step 6: Clear Search Bar.
Step 7: Enter Search
Query. Step 8: Submit
Search Query. Step 9:
Print Current URL. Step
10: Close Browser.

SOURCE CODE :
from selenium import webdriver
from selenium.webdriver.common.by import
By import time
driver = webdriver.Chrome()
driver.maximize_window()
driver.get("https://www.amazon.in/")
element = driver.find_element(By.LINK_TEXT, "See all
offers") time.sleep(5)
element.click()
time.sleep(5)
print(element)
driver.close()
OUTPUT:

RESULT : Thus the program is successfully executed and output is verified.

EXP 7.3 : Locators of selenium : XPATH

AIM: To Implement automated testing for e-commerce platforms

using the ‘XPath’ locator in Selenium.

ALGORITHM :

Step 1: Download Web Driver for

chrome. Step 2: Import necessary
modules.
Step 3: Initialize
WebDriver. Step 4: Open
Website.
Step 5: Find Search Bar.
Step 6: Clear Search Bar.
Step 7: Enter Search
Query. Step 8: Submit
Search Query. Step 9:
Print Current URL. Step
10: Close Browser.

SOURCE CODE :
from selenium import webdriver
from selenium.webdriver.common.by import
By import time
driver = webdriver.Chrome()
driver.maximize_window()
driver.get("https://www.amazon.in/")
element = driver.find_element(By.XPATH,
'//*[@id="icp-nav-flyout"]/span/span[2]/span[1]') time.sleep(5)
element.click()
time.sleep(5)
print(element)
driver.close()
OUTPUT:

RESULT : Thus the program is successfully executed and output is verified.

EXP 8 : Integrate TestNG with the above test

automation. AIM: To Integrate TestNG with the

above test automation. ALGORITHM:

Step 1 :The @BeforeClass annotation is used to set up the test environment

before any tests are run. In this case, it initialises the ChromeDriver and
navigates to the Amazon homepage.
Step 2 :The @Test annotation is used to mark a method as a test method. In
this case, it checks if the language button is displayed on the page.
Step 3 :The @AfterClass annotation is used to clean up the test environment
after all tests have been run. In this case, it quits the ChromeDriver.

SOURCE CODE :

package TestNGPKG;
import
org.testng.annotations.*;
import
org.openqa.selenium.*;
import
org.openqa.selenium.chrome.*;
import
java.util.concurrent.TimeUnit;

public class testNGClass

{ WebDriver driver;
@BeforeClass
public void beforeClass()
{
System.
setProperty("webdriver.chrome.driver",
"/Users/mychromedriverpath/Downloads/chromedri
ver2");
driver = new ChromeDriver();
driver.manage().window().maximize();
driver.get("https://www.amazon.com/");
driver.manage().timeouts().pageLoadTimeout(40, TimeUnit.SECONDS);
}
@Test
public void testMyApplication()
{
// To validate 'wikipedia' Logo

if(driver.findElement(By.xpath("//*[@id="icp-nav-flyout"]/span/span[2]/
span[1]")).isDisplayed()
)
{System.out.println("LANGUAGE BUTTON IS WORKING");}
 }

@AfterClass
public void afterClass()
{
driver.quit(); // To Close the Application....
}
}

OUTPUT:

RESULT : Thus the program is successfully executed and output is verified.