Test Plan

Product Name: OpenCart (Frontend)

Table of Contents
Description……………………………………………………………………….
Objective…………………………………………………………………………
Test Scope ……………………………………………………………………….
Test Strategy……………………………………………………………………...
Approach ………………………………………………………………………...
Risks and Mitigation……………………………………………………………..
Types of Testing………………………………………………………………….
Roles and Responsibilities……………………………………………………….
Hardware and Software Requirement……………………………………………
Defect tracking…………………………………………………………………...
Entry and Exit Criteria…………………………………………………………...
Templates………………………………………………………………………...
Tools……………………………………………………………………………..
Test Schedule…………………………………………………………………….
Test Deliverables…………………………………………………………………
Approvals………………………………………………………………………...

Description
 OpenCart is a robust, open-source e-commerce platform designed to
facilitate the creation and management of online stores. It provides a flexible,
user-friendly environment for merchants to sell products and services while
delivering a seamless shopping experience to customers. With a wide range of
features and customization options, OpenCart caters to businesses of all sizes,
from small startups to large enterprises.
This test plan is designed to ensure the functionality, security, and
performance of the OpenCart platform. The scope includes testing critical
modules such as user registration, product management, checkout, payment
gateways, and admin features. The plan outlines the testing strategy, including
functional, usability, performance, and security testing, cross browser testing,
across various environments.
Key deliverables include test cases, execution reports, and a final
summary report. The plan also addresses risk management and sets clear entry
and exit criteria to ensure the platform meets all requirements before release.
The ultimate goal is to deliver a robust and user-friendly OpenCart system ready
for deployment.

Objective
The objective of this test plan is to validate the functionality, usability,
performance, and security of the OpenCart platform. The goal is to ensure that
all modules, including user registration, product management, shopping cart,
checkout, and admin functions, operate as intended. This plan aims to identify
and resolve any defects, ensuring a reliable, secure, and user-friendly experience
for both customers and administrators before the platform is deployed.

Test Scope
The Scope of the project includes testing the following features of web
application.
In Scope:
 Registration
 Login & Logout
 Forgot Password
 Search
 Product Compare
 Product Display Page
 Add to Cart
  Wish List
 Currencies
 Home Page
 Shopping cart
 Checkout Page
 My Account Page
 Order History Page
 Downloads page
 Contact Us Page
 Menu Options
 Footer Options
 Category Pages
From our understanding, we believe above functional areas need to be
Tested.
Out Scope:
 All the features except that are mentioned under ‘In Scope’.
 Any third-party features or payment gateways.
 Test Automation.

Test Strategy
This section outlines the test strategy for the application under test (AUT)
as part of the overall test plan. The goal is to ensure that the application meets
all Functionalities mentioned in the above Test Scope section.
As part of testing the Functionalities, we will follow the below approach
for Testing:
Step1 – Creation of Test Scenarios and Test Cases for the different features
in scope.
 We will apply several Test Designing techniques while creating Test
Cases, including:
o Equivalence class partitioning: Input data will be divided into valid
and invalid partitions for test case design.
o Boundary Value Analysis: Test cases will focus on the boundaries of
input ranges.
o Decision Table Testing: Test case will cover all possible input
combinations and corresponding outputs.
o State Transition Testing: We will assess the application’s behavior
during state changes.
 o Use case Testing: Test case will be based on real-world use scenarios
to ensure practical functionality.
 Additionally, we also use our expertise in creating Test Cases by applying
the below:
o Error Guessing: We will use our experience to anticipate areas where
defects are likely to occur and design test cases to uncover these
defects.
o Exploratory Testing: Tester will explore the application to discover
defects that are not covered by predefined test cases.
 We prioritize Test Cases:
 Test Cases will be prioritized based on the criticality of the
functionality, the likelihood of defects, and the impact on users.
Step2 –Testing process, when we receive an Application for Testing:
 Smoke Testing: We will first perform Smoke Testing to verify that the
different and important functionalities of the application are working as
expected.
 If the smoke Testing fails, we will reject the build and wait for a stable
version before conducting more in-depth testing of the application’s
functionalities.
 In-depth Testing: Once we receive a stable build that passes smoke
Testing, we will proceed with in-depth testing using the test cases created
in Step1.
 Multiple test resources will be assigned to test the same application
across, multiple supported environments simultaneously, ensuring
comprehensive coverage.
 Bug Reporting: Bugs and defects discovered during testing will be
logged in the ‘Jira’ bug tracking tool.
 At the end of each day, we will send a status email summarizing the
defects found.
 As part of the Testing, we will perform the below types of Testing:
o Smoke Testing and Sanity Testing: Ensuring the stability and
functionality of the application.
o Regression Testing and Retesting: Verifying the recent changes
haven’t introduced new defects and the reported defects have been
fixed.
o Usability Testing, UI Testing and Accessibility Testing: Accessing
the application’s user experience, interface and accessibility for all
users.
  Test Cycles: We will repeat Test cycles until we achieve product that
means all requirements and is free of critical defects.
Step3 – Best practices to Enhance Our testing:
 Context Driven Testing – We will perform testing tailored to the specific
context of the given application, ensuring relevance and effectiveness in
our approach.
 Shift Left testing: We will start testing from the beginning stages of the
development itself, instead of waiting for the stable build.
 Exploratory Testing: Using our expertise, we will perform exploratory
testing alongside the normal execution of test cases to uncover defects that
may not have been anticipated.
 End to end Testing: we will test the end-to end Scenario which involve
multiple functionalities to simulate the end users flows.

Approach
In this section, we outline the comprehensive strategy for testing
the Open cart website. The following key methodologies and practices
will guide the testing process.

Testing techniques:
Black-Box Testing: We will focus on verifying that the system meets the
business and user requirements by testing its functionality without
considering the internal code structure.
White-Box Testing: Internal code paths and logic will be examined to
ensure proper implementation, especially for critical functions.
Test Levels:
Unit Testing: Each module within OpenCart will be tested individually to
confirm that it operates correctly in isolation. This includes testing various
functions, classes, and methods.
Integration Testing: We will test the interactions between different
modules (e.g., product management, user management, payment
gateways) to ensure they work together as expected.
System Testing: The entire OpenCart system will be tested in a real-world
scenario to validate that the system performs as intended when all
modules are combined.
 User Acceptance Testing (UAT): Final testing will be conducted from the
customer's perspective to verify that the system meets user expectations
and is ready for deployment.
Test Automation:
Regression Testing: We will automate key functionalities, such as the
checkout process and product management, to ensure that any new code
changes do not negatively impact existing features.
Routine Checks: Automated scripts will be used to routinely verify core
functions, such as login, registration, and payment processing.
Exploratory Testing:
In addition to planned test cases, exploratory testing will be conducted
to identify unexpected issues or bugs, particularly in areas where changes
have been made or in complex workflows.
Usability Testing:
Real users will be involved in testing the overall usability of the
OpenCart platform. This includes evaluating the user interface,
navigation, and overall user experience from both the administrator's and
customer's perspectives.
This approach provides a structured plan for testing OpenCart,
ensuring all critical aspects of the platform are thoroughly validated.

Risk and Mitigation

Risk: Application performance issues under high load or with large
volumes of data.
Mitigation: Conduct performance and load testing using tools like
‘JMeter’.
Risk: Limited availability of skilled testers, developers, or other key
personal.
Mitigation: Plan resources effectively and allocate sufficient time for
testing. Train team members to handle multiple roles or responsibilities.
Risk: Poor communication between development, testing, and other
stakeholders.
Mitigation: Schedule regular meetings and updates with all stakeholders.
Risk: Problems integrating third-party modules, payment gateways, or
shipping providers.
Mitigation: Test integrations early in the development cycle.
Type of Testing
The following types of testing should be included to ensure the platform
is thoroughly envaulted.
1.Functional Testing: Black-box testing geared to the application's
functional requirements.
2. Integration Testing: Verify combined functionality after integration.
3. Performance Testing: Check if the system meets performance
requirements.
4.Cross-browser Testing: Ensure system support across different
browsers.
5.Security Testing (Payment): Check application security against
internal and external threats.
6. UAT (User Acceptance Testing): From a tester’s perspective.
7. Regression Testing: Validate existing functionalities as part of
regression tests (Cart, Checkout Flow).
8. Progression Testing: Validate new functionalities.
9. Fixed defects validation

Roles and Responsibilities

Name Role Responsibilities
G. Purushotham Test Manager Escalations
 Create the Test Plan.
 Interact with the application.
 Design and develop manual test
cases
 Execute manual test cases and
B. Kalyani Test Engineer report defects.
 Verify and validate fixes, and
retest as necessary.
 Document test results and prepare
manual test reports.
 Collaborate with developers to
identify root causes of defects
 during manual testing.
 Participate in manual test case
reviews and provide feedback for
improvement.
 Attend any meeting with client.
 Create the Test Plan.
 Interact with the application.
 Design and develop manual test
H. Sneha Test Engineer cases
 Execute manual test cases and
report defects.
 Verify and validate fixes, and
retest as necessary.
 Document test results and prepare
manual test reports.
 Collaborate with developers to
identify root causes of defects
during manual testing.
 Participate in manual test case
reviews and provide feedback for
improvement.
 Attend any meeting with client.

Hardware and Software Requirement:

 Browsers: Chrome, Firefox, Safari, Edge.
 Operating Systems: Windows, macOS, Linux.
 Screen Resolutions: Desktop and laptop resolutions.

Defect tracking:
This section provides an overview of the process for identifying,
documenting, and managing defects during the manual testing of the OpenCart
application.
Defect Logging:
All defects discovered during testing will be recorded in a defect tracking
system (e.g., Jira, Bugzilla). Each defect entry will include:
- A detailed summary of the defect.
- Step-by-step instructions to reproduce the defect.
- A comparison of the actual result versus the expected outcome.
 - Visual evidence, such as screenshots or video captures (when
applicable).
- Classification of the defect by severity (e.g., Critical, Major, Minor).
- Assignment of a priority level (e.g., High, Medium, Low).
Defect Tracking System:
The use of a centralized defect tracking tool is crucial for effective
collaboration among team members. This system will enable:
- Streamlined logging and submission of defects.
- Assignment of defects to appropriate team members for resolution.
- Real-time tracking of defect statuses (e.g., Open, In Progress, Resolved
and Closed)
- Enhanced communication and coordination in resolving defects.
Defect Reporting:
Regular defect analysis reports will be generated to provide insights into
 The total number of defects identified, along with their respective
severity
 and priority levels.
 The progress of defect resolution efforts.
 Overall trends in defect discovery and closure rates.
These reports will support informed decision-making and ensure the
quality and stability of the final OpenCart application.
This version keeps the essential content but rephrases and restructures the
information to provide a different perspective.

Entry and Exit Criteria:

Entry and exit criteria define the conditions that must be met before
starting and concluding each testing phase for the OpenCart application.
Entry Criteria:
1. Test Planning Phase:
 Requirement documents are completed, reviewed, and approved by
all stakeholders.
 Test environment, including necessary hardware, software, and
network configurations, is set up and validated.
  Test data is prepared, reviewed, and approved for use in test
execution.
 Test cases and test scripts are developed, reviewed, and finalized.
 All required tools and resources are available and operational.
 Risks have been identified, assessed, and mitigation plans are in
place.
2. Test Execution Phase:
 The test plan is reviewed and approved by all relevant stakeholders.
 Test scenarios, test cases, and test scripts are documented, and test
data is available.
 Test environment is deployed, configured, and stable, ready for
testing.
 Testers are trained and familiar with the OpenCart system and
testing tools.
 All high-priority defects from previous phases are resolved, or
acceptable workarounds are in place.
 Test management tools are set up to track test execution progress
and defect logging.
Exit Criteria:
1.Test Planning Phase:
 Test plans, test cases, and test scripts are reviewed, approved, and
baseline documents are established.
 Test schedule is defined, and resources are allocated as per the
project plan.
 Entry criteria for the test execution phase are met.
2. Test Execution Phase:
 All planned test cases are executed, and results are documented.
 All critical and high-priority defects are fixed, retested, and closed.
 Defect reports are reviewed, and no critical issues remain open.
 Test summary report is prepared, reviewed, and approved by
stakeholders.
 Test metrics (e.g., pass/fail rates, defect density) are within
acceptable limits.
 Sign-off is obtained from all stakeholders to move forward with the
next phase or product release.
This version reflects a comprehensive approach, ensuring clarity and
completeness in your test plan.

Templates:
Utilizing standardized templates in a test plan ensures uniformity,
precision, and thoroughness in the documentation. Below are key templates that
will be employed in this test plan for the OpenCart application:
 Test Plan Template.
 Test Case Template.
 Defect Report Template.
 Test Summary Report Template.
These templates facilitate a structured approach to capturing and
communicating critical information throughout the testing process, ensuring
clarity and efficiency.

Tools:
 Test Case creation: Microsoft Excel.
 Test Case Tracking: Microsoft Excel.
 Test Case Execution: Manual.
 Test Case Management: Microsoft Excel.
 Defect Management: Jira.
 Test Reporting: Microsoft Excel & Jira.

Test Schedule:
Following is the test schedule planned for the project:

Task Time Duration

Creating Test Plan August-27-2024 to August-28- 2024

Test Case Creation August-29-2024 to August-31- 2024

Test Case Execution September 1-2024 to September -3-2024

Summary Reports & September 4-2024

Submission
 Test Case Test Case Total
Module
Creation Execution Hours
Register 2 hours 2 hours 4 hours
Login & Logout 2 hours 2 hours 4 hours
Forgot Password 2 hours 2 hours 4 hours
Search 2 hours 2 hours 4 hours
Product
2 hours 2 hours 4 hours
Compare
Product Display
3 hours 3 hours 6 hours
Page
Add to Cart 2 hours 2 hours 4 hours
Currencies 2 hours 2 hours 4 hours
Wish List 2 hours 2 hours 4 hours
Home Page 2 hours 2 hours 4 hours
Shopping Cart 2 hours 2 hours 4 hours
Checkout Page 3 hours 3 hours 6 hours
My Account
2 hours 2 hours 4 hours
Page
Order History
2 hours 2 hours 4 hours
Page
Contact Us Page 1 hours 1 hours 2 hours
Menu Options 2 hours 2 hours 4 hours
Footer Options 1 hour 1 hour 2 hours
Category Pages 2 hours 2 hours 4 hours
Buffer Time 1 hour 1 hour 2 hours

Detailed Daily Schedule:

Day 1 - Day 3: Test Case Creation
 Day 1: Register (2 hours), Login & Logout (2 hours), Forgot Password (2
hours), Buffer Time (1 hour), Search (2 hours).
 Day 2: Product Compare (2 hours), Wish List (2 hours), Currencies (2
hours), Product Display Page (3 hours), Add to Cart (2 hours)
 Day 3: Home Page (2 hours), Shopping Cart (2 hours), Checkout Page (3
hours), My Account Page (2 hours), Order History Page (2 hours),
Contact Us Page (1 hours).
 Day 4: Menu Options (2 hours), Footer Options (1 hour), Category Pages
(2 hours)
Day 7 - Day 8: Test Case Execution
 Day 5: Register (2 hours), Login & Logout (2 hours), Forgot Password (2
hours), Buffer Time (1 hour), Search (2 hours).
 Day 6: Product Compare (2 hours), Wish List (2 hours), Currencies (2
hours), Product Display Page (3 hours), Add to Cart (2 hours).
 Day 7: Home Page (2 hours), Shopping Cart (2 hours), Checkout Page (3
hours), My Account Page (2 hours), Order History Page (2 hours),
Contact Us Page (1 hours).
 Day 8: Menu Options (2 hours), Footer Options (1 hour), Category Pages
(2 hours).
Summary:
Register: 4 hours (2 hours creation, 2 hours execution).
Login & Logout: 4 hours (2 hours creation, 2 hours execution)
Forgot Password: 4 hours (2 hours creation, 2 hours execution)
Search: 4 hours (2 hours creation, 2 hours execution)
Product Compare: 4 hours (2 hours creation, 2 hours execution)
Wish List: 2 hours (1 hours creation, 1 hours execution)
Currencies: 4 hours (2 hours creation, 2 hours execution)
Product Display Page: 6 hours (3 hours creation, 3 hours execution)
Add to Cart: 4 hours (2 hours creation, 2 hours execution)
Home Page: 4 hours (2 hours creation, 2 hours execution)
Checkout Page: 6 hours (3 hours creation, 3 hours execution)
My Account Page: 4 hours (2 hours creation, 2 hours execution)
Order History Page: 4 hours (2 hours creation, 2 hours execution)
Contact Us Page: 2 hours (1 hours creation, 1 hours execution)
Menu Options: 4 hours (2 hours creation, 2 hours execution)
Footer Options: 2 hours (1 hour creation, 1 hour execution)
Category Pages: 4 hours (2 hours creation, 2 hours execution)
Buffer Time: 2 hours (1 hour creation, 1 hour execution)

Test Deliverables:
 This section outlines the documents and artifacts produced during the testing
process for the e-commerce website. These deliverables will serve as records of
the testing effort and provide stakeholders with insights into the quality of the
website.
 Test Plan
 Test Case
 Test Script
 Test Execution Report
 Test Closure Report
 Installation CD
 User Manual
 Defect Reporting
 Release Notes

Approvals:
We will send different types of documents for Client Approval like below:
 Test Plan
 Test Scenarios
 Test Cases
 Reports
Testing will only continue to the next steps once these approvals are done.