TEST PLAN

https://pcshop.ua
 CONTENTS
1. INTRODUCTION 3
2. FEATURE TO BE TEST 3
3. APPROACH 6
4. PASS/FAIL AND SUSPENSION CRITERIA 6
5. SUSPENSION CRITERIA 6
6. ACCEPTANCE CRITERIA 6
7. TEST DELIVERABLES 7
8. REMAINING TEST TASK 7
9. TEST ENVIRONMENT 7
10. STAFFING AND TRAINING NEEDS 7
11. RISKS 8
 1. INTRODUCTION

1.1. Purpose
The purpose of this test plan is to describe the testing process of a website PCshop
(https://pcshop.ua)
The document is intended a better understanding about the scheduled work of a
testing website.
Test object: the website https://pcshop.ua [hereinafter “PCshop”].
The main goal: the maximum coverage of the site in order to determine its
quality and check the basic functions characteristic for the online store.
1.2 General information

"PCshop" - PCshop is an online store of electronic and home appliances, it which

it is possible can choose and purchase electronic and home appliances.

1.3 Criteria for starting and ending a test

Testing can be started if the following conditions are met:

1. Documentation required for testing is ready and approved;
2. The functionality to be tested is completed and ready to be submitted for testing.
Testing may be completed if the following conditions are met:
1. All functionality of the site is covered to the maximum extent possible;
2. All test case are passed;
3. All defects found are documented.

2. FEATURE TO BE TEST

2.1 Banner on the home page

2.1.1 Whether the offers in the slider change automatically;
2.1.2 Whether manual change of sentences in the slider is possible;
2.1.3 Click ability of each offer in the slider;
2.1.4 Correctness of transition to the landing page when you click on the offer;
2.1.5 Display of the offers in different browsers and on different screen resolutions;
2.1.6 Display in the mobile version.

2.2 Search
2.2.1 Presence of filters in the search, such as categories and the correctness of their
selection;
2.2.2 The ability to search for the name of the product, its part number, category;
2.2.3 The relevance of the search;
2.2.4 Paging or other navigation in multi-page search results;
2.2.5 Ability to search results;
2.2.6 Ability to sort search results by various parameters (reviews, rating, etc.)

2.3 Catalog
2.3.1 Testing of sorts;
2.3.2 Testing of filters and facets;
2.3.3 Testing of paging and navigation;
2.3.4 Testing of prices and discounts;
2.3.5 Testing of categories and subcategories.

2.4 Product card

2.4.1 Product pictures;
2.4.2 Product description;
2.4.3 Product features;
2.4.4 Reviews and ratings;
2.4.5 Sizes and dimensions;
2.4.6 Stock and Availability;
2.4.7 Delivery Terms;
2.4.8 Product Variations;
2.4.9 Related products and replacements;
2.4.10 Breadcrumbs and other navigation;
 2.5 Shopping cart
2.5.1 Adding an item to cart;
2.5.2 Removing an item from cart;
2.5.3 Changing the quantity of items in cart;
2.5.4 Recalculation of orders during cart actions;
2.5.5 Matching the amount and quantity of items in the cart and informer;
2.5.6 Possibility to add items to cart and continue shopping;
2.5.7 Possibility to return to cart and order if you close the browser unexpectedly;
2.5.8 Promotional offers and coupons applied to the order;
2.5.9 Correct prices and quantities;
2.5.10 Ability to proceed to payment;
2.5.11 No action when cart is empty;
2.5.12 Shipping Terms;
2.5.13 Quantity and terms of delivery in case of lack of goods in the store.

2.6 Payment
2.6.1 Payment options and the ability to select them;
2.6.2 Transitions to online payment services;
2.6.3 Session termination at idle time;
2.6.4 Payment by registered;
2.6.5 Payment by unregistered user;
2.6.6 Confirmation of payment by email;
2.6.7 Confirmation of payment by sms.

2.7 Personal cabinet

2.7.1 Changing order (cancellation, quantity change);
2.7.2 Tracking order on delivery;
2.7.3 Return of purchase;
2.7.4 Loyalty points;
2.7.5 Special Offers;
2.7.6 Order History.

3. APPROACH
3.1 Functional testing;
3.2 Usability testing;
3.3 Cross-browser and cross-platform testing;
3.4 Load testing;
3.5 Smoke testing;
3.6 Regression testing;
3.7 Acceptance testing.

4. PASS/FAIL AND SUSPENSION CRITERIA

Pass/fail criteria
4.1 Any deviation from the expected result - fail.
4.2 Actual result is the same as the expected result - pass.

5. SUSPENSION CRITERIA
5.1 Testing can be stopped when discovered bug requires global changes in the product.
5.2 This criteria determined by the manager.
5.3 Defect regression testing should be resumed only after fixing bugs/making any
changes/implementing new features.

6. ACCEPTANCE CRITERIA
6.1 The product must satisfy all customers’ requirements.
6.2 All identified bugs and defects must be fixed and closed.
6.3 All testing results will be documented and reported.
6.4 In agreement with the customer, it’s possible to exclude certain features and to skip
certain amount of bugs with low priority.
 7. TEST DELIVERABLES
7.1 Acceptance test plan
7.2 System/Integration test plan
7.3 Unit test plans/turnover documentation
7.4 Screen prototypes
7.5 Report mock-ups
7.6 Defect/Incident reports and summaries
7.7 Test logs and reports

8. REMAINING TEST TASK

Task Assignet to Status
Create Acceptance Test Plan TM, PM, Client  
Create System/Integration Test Plan TM, PM, Dev.  
Define Unit Test rules and Procedures TM, PM, Dev.  
Define Turnover procedures for each
level TM, Dev  
Verify prototypes of Screens Dev, Client, TM  
Verify prototypes of Reports Dev, Client, TM  

9. TEST ENVIRONMENT
Google Chrome
Browser
version 79.0.3945.117
Operating system Windows 8
Screen resolution 1280х1024
Site mapping to mobile
Samsung A51 Android 10
devices

10. STAFFING AND TRAINING NEEDS

QA engineers must be qualified with a lot of experience and knowledge of creation a
test cases.
 11. RISKS
1. Failure of terms of output (at the final stage of development may arise unexpected
situations when appears critical bugs and defects. In this cases the release may be
delayed).
2. Misunderstandings between team members
3. Poor workflow organization.
4. Emergencies.