Scribd
Upload
466 views

Test Strategy For Ecommerce Website

The test strategy document outlines the plan to test an ecommerce website. It details the objective to ensure the website meets requirements through testing all customer and admin workflows, integrations, performance, security and compatibility. The approach involves automated and manual testing techniques across functional, load, security and usability areas. Deliverables include test cases, reports, and an automated regression suite. A team of 5 is needed for a 4 month testing effort.

Uploaded by

priyanka081708
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
466 views

Test Strategy For Ecommerce Website

The test strategy document outlines the plan to test an ecommerce website. It details the objective to ensure the website meets requirements through testing all customer and admin workflows, integrations, performance, security and compatibility. The approach involves automated and manual testing techniques across functional, load, security and usability areas. Deliverables include test cases, reports, and an automated regression suite. A team of 5 is needed for a 4 month testing effort.

Uploaded by

priyanka081708
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Test Strategy for Ecommerce Website

Objective The objective is to test the end-to-end functionality, usability and performance of
the ecommerce website and ensure it meets the business and technical requirements.

Scope

In scope:

- All customer workflows - search, browse, add to cart, checkout, payments


- Account registration and management
- Order management and tracking
- Integration with payment gateways
- Admin module and workflows
- Web and mobile site Out of scope:
- Physical fulfillment of orders
- 3rd party integrations not related to core functionality

Focus Areas
- Functional correctness of flows
- UI/navigation
- Performance
- load, stress and scalability
- Security - vulnerabilities, encryption

- Compatibility
- browsers, devices, OS
- Usability - ease of use, accessibility

Approach
- Black box and white box testing techniques
- Automated test cases using Selenium and Appium
- Exploratory testing for key workflows
- Load testing with JMeter for at least 1000 concurrent users - Security testing for OWASP
Top 10 vulnerabilities.
- Cross browser compatibility testing on IE, Chrome, Firefox - Ease of use evaluation with at
least 10 end users.
Deliverables

- Functional test cases and reports


- Performance test scripts and results - Security vulnerabilities report

- User acceptance testing report


- Test coverage and defect reports
- Automation regression suite

Team & Schedule Testing

- team of 5 members needed for 4 months testing effort Proposed schedule:


- April: Functional and security testing
- May: Load/performance testing
- June: Compatibility testing, UAT - July: Regression testing

Entry & Exit Criteria User stories

- to be tested must meet the defined 'Ready for Testing' criteria.


- Testing completes when all test cases execute with no critical defects outstanding.

Risks
Delay in test environment availability
- Lack of access to third party payment systems
- Complex workflows may require more time and resources

You might also like