EX.

NO: 1 Develop the test plan for testing an e-commerce

web/mobile application (www.amazon.in).
DATE:

Introduction
The purpose of this test plan is to outline the testing approach for an e-commerce
web/mobile application, specifically www.amazon.in. The goal is to ensure that the
application functions as intended, meets user requirements, and provides a seamless
shopping experience.
Scope
The scope of this test plan includes testing the core functionalities of the e-commerce
application, such as browsing products, adding items to the cart, placing orders, and
managing user accounts. It also covers testing across different platforms, including
web and mobile.

Test Objectives
1. Validate the functionality of the e-commerce application.
2. Verify that the application is user-friendly and provides a smooth shopping
experience.
3. Ensure that the application is secure and protects user data.
4. Test the application's compatibility across different browsers and devices.
5. Evaluate the performance and scalability of the application under various load
conditions.
6. Identify and report any defects or issues found during testing.
Test Environment
1. Web browsers: Chrome, Firefox, Safari, and Edge.
2. Mobile devices: iOS and Android.
3. Test management tool: Jira or any other preferred tool.
4. Test automation tool: Selenium WebDriver or any other preferred tool.
5. Load testing tool: JMeter or any other preferred tool.
 Test Approach
1. Requirements Analysis:
 Review the functional and non-functional requirements of the e-commerce
application.
 Identify testable features and prioritize them based on criticality.
2. Test Design:
 Create test scenarios and test cases for each identified feature.
 Include positive and negative test cases to cover different scenarios.
 Define test data and test environment setup requirements.
3. Test Execution:
 Execute test cases manually or using test automation tools.
 Log defects in the test management tool and track their status.
 Perform regression testing after each bug fix or application update.
4. Performance Testing:
 Design and execute performance tests to evaluate the application's response time,
throughput, and scalability.
 Simulate different user loads and monitor system resources during testing.
 Identify performance bottlenecks and suggest improvements if needed.
5. Security Testing:
 Conduct security testing to identify vulnerabilities and ensure the application protects
user data.
 Test for common security issues like SQL injection, cross-site scripting (XSS), and
authentication vulnerabilities.
 Implement security best practices and follow industry standards.
6. Compatibility Testing:
 Test the application on different browsers, versions, and mobile devices.
 Verify that the application renders correctly and functions as expected across various
platforms.
Test Deliverables
1. Test plan document.
2. Test scenarios and test cases.
3. Test execution reports.
4. Defect reports with severity and priority.
5. Performance test reports.
6. Security test reports.
Conclusion
By following this test plan, you can ensure comprehensive testing of the e-commerce
web/mobile application (www.amazon.in). It covers functional, performance, security,
and compatibility testing, enabling you to deliver a high-quality and reliable
application to end-users.
EX.NO: 2 Design the test cases for testing the e-commerce
application
DATE:

Aim:

To Design the test cases for testing the e-commerce application.

Test Case for Ecommerce Website

This post is related to the test cases which are required to test an e-
commerce website. Checking an E-commerce website is itself a challenge as it
includes many flows. To test an E-Commerce website, one must know about
testing techniques and some of theknowledge about what E-commerce is.

Test Scenario Overview

Post On: Test Case For Ecommerce Website
Post Type: Test Case Template
Published On: www.softwaretestingo.com
Applicable For: Fresher’s & Experience

Below are some of the test cases which will help you to do better testing of E-
Commerce Websites
 Check that users can navigate through all the products across different
categories.
 Check that all the links are redirecting to correct product/category pages, andnone
of the links is broken.
 Check that the company logo is visible.
 Check that all the text – product, category name, price, and product description are
visible.
 Check that all the images are visible.
 Check that category pages have a relevant product explicitly listed for the
category.
  Check that the correct count of total products is listed on the category pages.

Login Page Test Cases For Ecommerce Website

 Check that there are proper validations on Login Page.

 Check for an error message if Email, password, or any required field is left blank.
 Check the validations on Email and password.
 When you log in, check that you stay logged in as you browse products.
Also, youneed to test the behavior.
 When the user doesn’t interact with the site for some time, will the
session expireafter some time? Make sure the user has been logged out
after the session times out.
 When you are logged in, log out and make sure you are logged out
and that youcannot access any of the accounts pages.

Ecommerce Website Test Case

Related Test Cases

☑ Test Case For Digital Camera ☑ Test Case For Door

☑ Test Case For Electric Bulb ☑ Test Case For Electronic Reader

Registration Page Ecommerce Website Test Cases

 Check that all the required fields are present on the registration page.
 Check that the required/mandatory fields are marked with * against the field.
 Check that for better user interface dropdowns, radio buttons and
checkboxes, etc.fields are displayed wherever possible instead of just
text boxes.
 Check the page has both submit and cancel/reset buttons at the end.
  Check that on clicking the submit button after entering all the required
fields, andthe data is sent to the server.
 Check that clicking cancel/reset button after entering all the
required fields,cancels the submit request, and reset all the fields.
 Check that whenever possible, validation should take place on the client-side.
 Check that not filling the mandatory fields and clicking the submit
button willlead to the validation error.
 Check that not filling the optional fields and clicking the submit
button will senddata to the server without any validation error.
 Check the upper limit of the text boxes.
 Check validation on the date and email fields (only valid dates and
valid email Idsshould be allowed.
 Check validation on numeric fields by entering alphabets and special characters.
 Check that leading and trailing spaces are trimmed.
 Check that entering blank spaces on mandatory fields lead to validation error.

Address Book Test Cases Of Ecommerce Website

 Check validations on Address Book Page.

 Verify Address entered by the customer.
 Check Add New Address functionality.
 Check Change Address functionality.
 Check the availability of the product on the Address entered by the customer.

Search Page Test Cases for Ecommerce Website

 Check that the products displayed are related to what was searched for.
 Check that the products should display an image, name, price,
and maybecustomer ratings and number of reviews.
 Check the more relevant product for the search term is displayed on
the top for aparticular search term.
 Check that all items on the next page are different from the previous
page, i.e., noduplicates.
 Check that when both sorts and filters have been applied, they
remain as wepaginate or more products are loaded.
 Check that count of products is correctly displayed on the search result
page for aparticular search term.
 Check that filtering functionality correctly filters products based
on the filterapplied.
 Check that filtering works correctly on category pages.
 Check that filtering works correctly on the search result page.
  Check that the correct count of total products is displayed after a filter is applied.
 Check that all the sort options work correctly – correctly sort the
products basedon the sort option chosen.
 Check that sorting works correctly on the category pages.
 Check that sorting works correctly on the search result page.
 Check that sorting works correctly on the pages containing the
filtered result,after applying filters.
 Check that product count remains intact irrespective of the sorting option applied.

Wish list Page Test Cases

 Verify that the added product is present on the wish list page.
 Check that Update of the wish list is working correctly.
 Check the Share wish list functionality.
 Check that user can add products to the cart from the wish list page.
Product Details Page Test Cases

 Verify Actual product details with expected product details.

 Verify Add to Cart should work correctly.
 Check that user can add products in the wish list.
 Check that a complete description of the product, including
images, isappropriately shown.
 Check that option to check the availability of the product is present.
 Check that users can rate, review the product.

Cart Test Cases

 Check that user can add products to the cart.

 Check that the cart is updated with the correct name, image, and
price of theproduct.
 Check that users can add the same product multiple times.
 Check that the price increase accordingly when a product is added multiple times.
 Check that user can add multiple products of different types.
 Check that For each item added, a corresponding name, image, and
price and thetotal price of all things are shown.
 Check that when a product is removed from the cart, the cart gets
updated and shows the actual items in the cart, total price according to
the products left in thecart.
 Check that when all the products are removed from the cart, then
 cart balancebecomes zero, no items should be displayed in the cart.
 Check that customers should be able to see more about the product
when clickedon the product either as a popup or redirect to the product
page.
 When a user adds products to cart and then closes the tab, then ideally,
the cart should still hold your items or mainly depends on the
requirements on how the cartshould behave.
 Check that the cart’s price is discounted when we apply a
coupon and notdiscounted when we use an invalid or expired
coupon.

Product Buy Flow Test Cases

 Check that on the product page, and a user can select the desired
attribute of theproduct, e.g., size, color, etc.
 Check that users can add to cart one or more products.
 Check that user can add products to the wish list.
 Check that user can buy products added to cart after signing in to the
application(or as per the functionality of the website).
 Check that user can successfully buy more than one products that
were added tohis/her cart.
 Check that the limit to the number of products a user can by is
working correctly by displaying an error message and preventing the
user from buying more than thethreshold.
 Check the availability of products at desired locations.
 Check that Cash on the Delivery option of payment is working fine.
 Verify that the different pre-paid methods of payments are working fine.
 Check that product return functionality works fine.
 Check that the Cancel Order option is present.

Payment Page Test Cases

 Check that After fill shipping address and payment, the product is
purchasedsuccessfully.
 Check that Different payment types should be present, e.g., Credit
Card, PayPal,Bank Transfers, Installments, etc.
 Check the security of the client’s card details when entered for payment.

Seller – Product creation Test Cases

 Check that authenticated sellers get access to product creation panels

 specific tothe authorized categories.
 Check that product creation is working fine for single product creation.
 Check that product creation is working fine for multiple product creations.
 Check that the maximum product creation limit for the seller is
working fine,limiting the seller to create more than the desired
number of products.
 Check validation for checking mandatory fields.
 Check that duplicate product creation is restricted.
 Check that seller can update the information and price of existing products.
 Check that product created by sellers get visible on the website after
a specificperiod.
 Check that updation made by the seller get visible on the website after
the specificperiod.

Post Purchase Test Cases

 Check that customer can cancel the order or change the quantity of the order.
 Check that customer can Review recent order and history of purchased items.
 Check that customers can Change information, such as billing address,
shipping address, change password, change profile information such as
name, email address, and even deleting an account.

Tasks To Improve Your Knowledge

☑ Test cases for Flipkart website ☑ E-commerce testing pdf

☑ How to automate e-commerce website using

☑ Load testing for e-commerce website
selenium

☑ How to test e Commerce

☑ Test cases for home page of website
websiteautomatically

☑ Introduction to testing in e-commerce ☑ API testing in e Commerce

 EX.NO: 3
Test the e-commerce application and report the defects in it
DATE:

Aim:

To test the e-commerce application and report the defects in it.

Func tiona l Tes t Cases f or Ec ommerce Webs ites :

 The registration and login processes are working correctly

 Users can add products to their cart
 Users can view their cart and remove items if necessary
 The checkout process is working correctly
 Users can search for products on the website
 Users can view product details and purchase the products
User I nte rface Test C ases for Ec ommerce We bsites :

The user interface is an essential part of any ecommerce website. It's important to
ensure that the user interface is easy to use and navigate. Here are some user interface
test cases to consider:
 Website has a professional and visually appealing design

 The website has a clear and concise layout

 Website is easy to navigate

 The website has clear call-to-action buttons

 Website has a user-friendly search function

 The website has clear and concise product descriptions.
 Naviga tion Tes t Cases f or Ec ommerce Webs ites :
Navigation testing is essential to ensure that users can navigate the website easily
and find what they are looking for.
Here are some navigation test cases to consider:
 The website has a clear and concise menu

 The website has a breadcrumb trail for easy navigation

 Users can access their account and order history easily

 Website has a clear and concise footer with important links

 The website has a search function that works correctly

Cart a nd C hec kout Tes t Cases f or Ecommerce Webs ites :

The cart and checkout process is where users can review and complete their purchase.
Therefore, it's important to test this process thoroughly.
Here are some cart and checkout test cases to consider:
 Users can add and remove products from their cart
 The cart subtotal, taxes, and shipping costs are accurate
 Users can enter their payment details securely
 Users can place an order successfully
 Users receive a confirmation email with the order details .
 Payme nt Ga te way Tes t Cases f or Ec ommerc e We bsites:

Payment gateway testing is essential to ensure that users can make payments securely
and easily. Here are some payment gateway test cases to consider:
 The payment gateway is secure and that sensitive data is protected
 Users can enter their payment details without any issues
 The payment gateway accepts different payment methods
 Payment gateway has a clear and concise error message for any issues
 Pe rf o rman c e T est Ca se s fo r E co m me rc e Web si t es:
Performance testing is essential to ensure that the website performs well under
different conditions. Here are some performance test cases to consider:
 The website performs well under heavy traffic
 The website loads quickly on different devices and internet connections
 Website is optimized for different devices and screen sizes
 The website can handle a large number of products and users

S ecu ri t y T est Ca s es fo r Eco m me rce W eb si t e s:

Security testing ensures that the ecommerce website's security is robust, protecting
user data and preventing unauthorized access. Here are some essential secu rity test
cases for ecommerce websites:
Verify the Security Test Cases:
1. User data protection:
The user data is protected securely, with no vulnerabilities or loopholes.
2. Payment gateway security:
The payment gateway is secure, with all the necessary checks and verifications in place
to prevent fraud and unauthorized access.

M ob i le R esp on si v en e s s Te st Ca se s fo r Eco m me rce W eb s i t es:

Mobile responsiveness testing ensures that the ecommerce website is optimized for
mobile devices, providing a seamless user experience on mobile devices. Here are
some essential mobile responsiveness test cases for ecommerce websites:
Verify the Mobile Responsiveness Test Cases:
1. Mobile compatibility:
The website is compatible with all mobile devices, with no display or performance
issues.
2. Mobile user experience:
The website provides a seamless user experience on mobile devices, with all the
necessary information and options eas ily accessible.

Comp at i b i li t y T est Ca se s fo r E co m me r ce Web si t e s:

Compatibilit y testing ensures that the ecommerce website works seamlessly on all
browsers and devices, providing a consistent user experience across all platforms. Here
are some essential compatibility test cases for ecommerce websites:
Verify the Compatibility Test Cases:
1. Browser compatibility:
The website works seamlessly on all popular browsers, such as Chrome, Firefox, and
Safari.
2. Device compatibility:
The website works seamlessly on all devices, including desktops, laptops, tablets, and
mobile devices.
Con c lu si on :
In conclusion, testing is a crucial aspect of ecommerce website development, ensuring
that the website is reliable, secure, and user-friendly. Functional testing, user interface
testing, navigation testing, cart and checkout testing, payment gateway testing,
performance testing, security testing, mobile responsiveness testing, and compatibility
testing are all essential test cases for ecommerce websites. As an Ecommerce website
development company, we ensure that all our ecommerce websites undergo thorough
testing, providing our clients with a reliable and user -friendly website that meets their
business goals and objectives.
EX.NO: 4 Develop the test plan and design the test cases for an
DATE: inventory control system

Aim:

To develop the test plan and design the test cases for an inventory control system.

Unit testing

Unit testing is a software testing method by which individual units of

source code, sets of one or more computer program modules together with
associated control data, usage procedures, and operating procedures, are tested
to determine whether they are fit for use

Black Box testing

Black-box testing is a method of software testing that examines the

functionality of an application without peering into its internal structures or
workings. This method of test can be applied virtually to every level of software
testing: unit, integration, system and acceptance. It is sometimes referred to as
specification-based testing .

White box testing

White-box testing (also known as clear box testing, glass box testing,
transparent box testing, and structural testing) is a method of testing software
that tests internal structures or workings of an application, as opposed to its
functionality (i.e. black-box testing). In white-box testing an internal perspective
of the system, as well as programming skills, are used to design test cases.
Integration testing

Integration testing (sometimes called integration and testing, abbreviated

I&T) is the phase in software testing in which individual software modules are
combined and tested as a group .

System Testing

System testing of software or hardware is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified
requirements. System testing falls within the scope of black-box testing, and as
such, should require no knowledge of the inner design of the code or logic. As a
rule, system testing takes, as its input, all of the "integrated" software components
that have passed integration testing and also the software system itself integrated
with any applicable hardware system(s)

User acceptance Testing (Beta Testing)

User acceptance testing (UAT) consists of a process of verifying that a

solution works for the user. It is not system testing (ensuring software does not
crash and meets documented requirements), but rather ensures that the solution
will work for the user (i.e., tests that the user accepts the solution); software
vendors often refer to this as "Beta testing".
Inventory Control System

Catalog Sheet from the Inventory Spreadsheet.

EX.NO: 5 Execute The Test Cases Against A Client Server Or Desktop
DATE: Application And Identify The Defects

AIM:

To execute the test cases against a client server or desktop application and identify
the defects.

Client Server Testing:

 The Client-Server application consists of two systems, one is the Client and
the other is the Server. Here, the client and server interact with each other
over the computer network.
 In Client-Server application testing, the client sends requests to the server
for specific information and the server sends the response back to the client
with the requested information. Hence, this testing is also known as two-tier
application testing.
 Few client-server applications are Email, Web Server, FTP, etc
 This type of testing is usually done for 2 tier applications (usually developed
for LAN). We will be having Front-end and Backend here.
 Applications launched on the front-end will have forms and reports which
will be monitoring and manipulating data.

Desktop Testing:
 A Desktop Application is a software program that is used to run on a
personal computer, machine, or laptop.
 Required applications or software are installed on a stand-alone
machine and the installed application is accessible by only one user
at a time.
 Hence, desktop application testing is also known as stand-alone
application testing.
  Few desktop applications are MS-Office, Calculator, Adobe Acrobat
Reader, etc

Client Server Testing

Desktop Testing:
Conclusion
 Hope you have a better understanding now after diving deep into each
testing type and understanding the difference between desktop, client-server,
and web application testing.

 Almost every tester might be involved in testing in any one of the testing
categories like Desktop application, Client-Server application, or Web
Application Testing.