E Commerce Website

E-commerce Website
Test Plan
ECMW-95
– Quy Nhon, January 2024 –

1
Revision History
Version Date A, M, D In charge Change Description
*A - Added, M - Modified, D - Deleted
1. Introduction
1.1 Purpose
2
The purpose of this test plan is to define the testing strategy, objectives, and tasks for the
testing phase of the E-Commerce Website project. It aims to ensure that the website
meets the specified requirements, functions flawlessly, and provides a positive user
experience.
1.2 Project Overview

The E-Commerce Website project involves the development of an online platform for
buying and selling products. The website includes features such as user registration,
product browsing, shopping cart management, order processing, and payment
integration.
2. Scope
2.1 In-Scope
- User registration and authentication
- Product catalog and browsing+
- Shopping cart management
- Order processing
- Payment integration
- User account management
- Additionally, the in-scope testing will cover the following aspects:
+ Interfaces: Ensure seamless communication between different system modules.
+ Third-party integrations not directly related to payment
+ Security testing beyond standard authentication measures
2.2 Out-Scope
- Offline functionality
- Mobile application testing
3. Test Strategy
3.1 Test Objectives
- Verify the functionality of all key features
- Ensure a seamless user experience across different browsers
- Validate payment processing and integration
- Identify and address performance issues under various loads
- Confirm data accuracy and integrity
3.2 Test Assumptions

- The development team follows the specified requirements and design.
- The test environment accurately reflects the production environment.
3.3 Data Approach

Test data will encompass various user profiles, product data, and payment methods to
ensure thorough testing.
3.4 Level of Testing

- Testing Levels:
3
+ Functional Testing: To validate that each function of the website works according to
specifications.
+ Usability Testing: To assess the user interface and overall user experience.
+ Security Testing: To identify and address potential vulnerabilities.
- Testing Types:
+ System Testing: To evaluate the overall system against defined functional
requirements.
+ Acceptance Testing: To ensure that the system meets user expectations.
3.5 Schedule and Resource

- Test Schedule: Start Date - MM/DD/YYYY, End Date - MM/DD/YYYY
- Resource planning: Ensure collaboration between testers, developers, and product
owners to ensure comprehensive test coverage.
5. Test Deliverables and Testing Tasks

5.1 Test Deliverables
- Test plan
- Test design specification
- Test case specification
- Test procedure specification
- Test item transmittal reports
- Test logs
- Test incident reports
- Test summary reports
5.2 Testing Tasks

- Develop test cases covering all functional requirements
- Execute test cases and document results
- Perform performance testing under different loads
- Conduct acceptance testing with stakeholders
6. Test Design
- Test Environment:
+ Web servers
+ Database servers
+ Browsers (Chrome, Firefox, Safari, Edge)
+ Payment gateway sandbox environment
- Test Scenarios:
+ User Login/Register
+ Shopping Journey
+ Discount Code
+ Search Product
+ Recommend Product
+ Shopping Cart
+ Payments
+ Homepage
+ Traffic
+ Updates
4
- Test Cases: Create test cases covering a comprehensive range of functionalities,
ensuring that the e-commerce website is thoroughly tested for usability, functionality,
security, and performance across various user interactions and system conditions.
7. Test Execution
7.1 Entry Criteria
- Completion of development and unit testing
- Availability of the test environment with necessary configurations
7.2 Exit Criteria

- Successful completion of test cases
- No critical or high-severity defects in the production environment
- Approval from stakeholders
7.3 Validate and Defect Management

- Use a defect tracking system to log and monitor issues. Validate fixes before retesting
and keep stakeholders informed of progress.
- Defect Reporting: Identified defects will be documented using a bug tracking system,
categorised by severity.
7.4 Execution Schedule

Test Execution Schedule: A phased approach will be implemented, starting with basic
functionality before progressing to more complex scenarios.
8. Test Closure
- Criteria for Test Completion: The test will be considered complete when all critical and
high-priority test cases have been executed without major defects.
- Test Summary Report: A comprehensive report summarizing test results, encountered
issues, and recommendations for improvement.
9. Risks and Contingencies

- Identified Risks: Potential server downtime, payment gateway issues.
- Contingency Plans: Regular system backups and alternative payment methods will be in
place to mitigate the impact of identified risks.
10. Approvals
- Approvals: Approval will be sought from the QA Lead and Project Manager upon
completion of the testing phase.
11. Appendices
9.1 Glossary
5
Terms Description
Testing Traffic The volume of users or requests accessing the e-

commerce website within a specific time frame. High
traffic scenarios test the system's ability to handle
increased user load.
Testing Updates Notifications or messages provided to users regarding

changes in their orders, such as order confirmation,
shipping updates, or other relevant information.
Functional Testing Testing focused on verifying that each function of the

website works according to specified requirements,
ensuring the software's correctness.
Usability Testing Evaluation of the user interface and overall user

experience to ensure the website is user-friendly,
intuitive, and provides a positive interaction.
Security Testing Testing activities designed to identify and address

potential vulnerabilities in the system, protecting against
security threats.
System Testing Evaluation of the entire system against defined

functional requirements to ensure integrated
components work together seamlessly.
Acceptance Testing Testing conducted to ensure that the system meets

user expectations and is ready for deployment.
9.2 References
- ISTQB (International Software Testing Qualifications Board)
- IEEE Standards for Software Testing
- Selenium (for web application testing), JUnit/TestNG (for Java), pytest (for Python)
- Apache JMeter for performance testing
– The End –

E Commerce Website

Uploaded by

Copyright:

Available Formats

E Commerce Website

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E Commerce Website

Uploaded by

Copyright:

Available Formats

E-commerce Website

– Quy Nhon, January 2024 –

Version Date A, M, D In charge Change Description

*A - Added, M - Modified, D - Deleted

1.2 Project Overview

3.2 Test Assumptions

3.3 Data Approach

3.4 Level of Testing

3.5 Schedule and Resource

5. Test Deliverables and Testing Tasks

5.2 Testing Tasks

7.2 Exit Criteria

7.3 Validate and Defect Management

7.4 Execution Schedule

9. Risks and Contingencies

Testing Traffic The volume of users or requests accessing the e-

Testing Updates Notifications or messages provided to users regarding

Functional Testing Testing focused on verifying that each function of the

Usability Testing Evaluation of the user interface and overall user

Security Testing Testing activities designed to identify and address

System Testing Evaluation of the entire system against defined

Acceptance Testing Testing conducted to ensure that the system meets

You might also like