1.INTRODUCTION

This test plan has been created to organize the test processes to be applied for the Kloti Online Shopping System application. This document is intended to be a reference for team members on features to be tested or not tested, details of test cases, workflow and methods planned to be tested.

1.1 Version Control

1.2 Overview

In this document, we aim to check how well the AR feature of the mobile application pages fulfills the features we specified in the SRS and SDD sections. Each of the pages in the Kloti Online Shopping Application will be subjected to a test.

1.3 Scope

This document contains test cases for two types of users. It includes test scenarios for customers to login, register, log out, checkout, add to cart, edit cart, select product, try selected product with AR, edit profile and view profile pages. For employees, it includes test scenarios for viewing the map, viewing past orders, viewing current orders, logging into the system, exiting the system and editing the order status. Each page and its functions will be examined in detail. This document explains the test requirements, test scenarios, how tests will be passed or failed, and test scenarios. The purpose of the document is to explain what to test and how to perform test cases.

1.4 Terminology

2. FEATURES TO BE TESTED

The user interface of Kloti Online Shopping application contains 16 pages where users (registered customer and employee) can communicate with the application. We classify the pages as Sign In(SI), Sign Up(SU), Sign Out(SO), Add To Cart(ATC), Edit Cart(EC), Augmented Reality(AR), Edit Profile (EP), Google Maps Navigation(GMN), Past Orders (PO), Order Status(OS). Brief descriptions of all the major features to be tested are listed in below.

2.1 Main Page (MP)

The first page users will see when entering the app. It has a different interface for two types of users. Customer main page slider, buttons with products, a hamburger menu located on the left side of the appbar, buttons for sign in and sign up in the hamburger menu. If the user is logged in, there will be edit profile and sign out in the hamburger menu.

2.2 Sıgn Up (SU)

Customers enter an email, password and personal phone number. Then the user presses the Sign Up button, after this process their profiles are created successfully.

2.3 Sıgn In (SI)

Users (employee and customer) enter their email and password. After clicking the Sign In button, customers are directed to the main menu prepared for users, and employees are directed to the main page created for employees.

2.4 Add To Cart (ATC)

Customers click the Add To Cart button on the product page, then the product is successfully added to the cart.

2.5 Edit Cart (EC)

By clicking the My Cart button, customers view their carts and either remove the product in the cart or increase the amount of products.

2.6 Augmented Reality (AR)

Customer clicks the camera icon on the product page. Afterwards, the product they want to try is successfully seen on their cameras.

2.7 Edit Profile (EP)

Users click on the My Profile button from the hamburger menu. Then they are successfully redirected to my profile page and edit their profile.

2.8 Past Orders (PO)

Employees click on my previous orders button on the down bar. Then they are directed to my previous orders page.

3. FEATURES NOT TO BE TESTED

The hardware of the mobile device will not be tested. In the test scenario, features such as problems with the camera, whether the device is AR compatible, whether the internet connection is working properly will not be tested.

4. ITEM PASS/FAIL CRITERIA

The criteria for deciding under which conditions the test case succeeds and under which conditions it fails.

4.1 EXIT CRITERIA

The conditions under which the product test was successful are described below.

• 90% of Test Scenarios run successfully.
• 85% of test cases passed successfully.

5. REFERENCES

• Group4_SDD, JANUARY 1, 2022
• Group4_SRS, JANUARY 5, 2022

6. TEST DESIGN SPECIFICATIONS

6.1 Customer Operations(CO)

6.1.1 Subfeatures to be tested for customer

6.1.1.1 Sign Up Button (CO.SU_BTN)

The customer goes to the sign up page by clicking the "Sign Up" button in the hamburger menu.

6.1.1.2 Sign Up Page (CO.SUP)

The customer writes the required information and clicks the "Sign Up" button.

6.1.1.3 Login Button (CO.LG_BTN)

The customer goes to the login page by clicking the "Login" button in the hamburger menu.

6.1.1.4 Login Page (CO.LP)

The customer writes the required information and clicks the "Login" button.

6.1.1.5 Edit Profile Page (CO.EPP)

Customers can edit their profile.

6.1.1.6 Choose Catalog Page (CO.CCP)

The customer selects the catalog by clicking the pictures in the main menu.

6.1.1.7 Choose Product Page (CO.CPP)

The customer selects the product by clicking the images on the product page.

6.1.1.8 Product Review Page (CO.PRP)

The customer sees the product information and, if desired, tries on it by clicking the camera icon.

6.1.1.9 Product Trial Button (CO.PT_BTN)

The customer presses the camera icon.The phone's camera turns on and the customer tries on the outfit.

6.1.1.10 Add To Shopping Cart Button (CO.ATC_BTN)

The customer adds the product to the cart by pressing the cart icon.

6.1.1.11 Edit The Shopping Cart Page (CO.ETCP)

The customer edits the shopping cart.

6.1.1.12 Confirm Cart Button (CO.CC_BTN)

The customer clicks the "Confirm Cart" button and goes to the payment page.

6.1.1.13 Payment Page (CO.PP)

The customer chooses the payment method and confirms the contracts.

6.1.1.14 Confirm And Finish Button (CO.CAF_BTN)

Customer clicks "Confirm And Finish" button.

6.1.2 Test Cases For Customer

6.1.2.1 Sign Up Button (CO.SU_BTN)

6.1.2.2 Sign Up Page (CO.SUP)

6.1.2.3 Login Button (CO.LG_BTN)

6.1.2.4 Login Page (CO.LP)

6.1.2.5 Edit Profile Page (CO.EPP)

6.1.2.6 Choose Catalog Page (CO.CCP)

6.1.2.7 Choose Product Page (CO.CPP)

6.1.2.8 Product Review Page (CO.PRP)

6.1.2.9 Product Trial Button (CO.PT_BTN)

6.1.2.10 Add To Shopping Cart Button (CO.ATC_BTN)

6.1.2.11 Edit The Shopping Cart Page (CO.ETCP)

6.1.2.12 Confirm Cart Button (CO.CC_BTN)

6.1.2.13 Payment Page (CO.PP)

6.1.2.14 Confirm And Finish Button (CO.CAF_BTN)

6.2 Employee Operations(EO)

6.2.1 Subfeatures to be tested for employee

6.2.1.1 Login Button (EO.LG_BTN)

Employee goes to the login page by clicking the "Login" button in the hamburger menu.

6.2.1.2 Login Page (EO.LP)

Employee writes the required information and clicks the "Login" button.

6.2.1.3 Edit Profile Page (EO.EPP)

Employees can edit their profile.

6.2.1.4 Accept Order Button (EO.AO_BTN)

The employee accepts the order by clicking the "Accept Order" button.

6.2.1.5 Reject Order Button (EO.RO_BTN)

The employee rejects the order by clicking the "Reject Order" button.

6.2.1.6 Previous Orders Button (EO.VPO_BTN)

The employee can view their past orders by clicking the my "Previous Orders" button.

6.2.1.7 Edit Order Status Button (EO.EOS_BTN)

The employee can update the order status by clicking the "Edit Order Status" button.

6.2.1.8 View Google Maps (EO.VGM_BTN)

Employee can view the order address by clicking on the map.

6.2.2 Test Cases For Employee

6.2.2.1 Login Button (EO.LG_BTN)

6.2.2.2 Login Page (EO.LP)

6.2.2.3 Edit Profile Page (EO.EPP)

6.2.2.4 Accept Order Button (EO.AO_BTN)

6.2.2.5 Reject Order Button (EO.RO_BTN)

6.2.2.6 Previous Orders Button (EO.VPO_BTN)

6.2.2.7 Edit Order Status Button (EO.EOS_BTN)

6.2.2.8 View Google Maps (EO.VGM_BTN)

7. TEST DETAİLED TEST CASES

7.1 CO.LG.01

7.2 CO.LG.02

7.3 CO.SU.01

7.4 CO.SU.02

7.5 CO.SU.03

7.6 CO.SU.04

7.7 CO.SU.05

7.8 CO.EPP_BTN.01

7.9 CO.ATC_BTN.01

7.10 CO.ETCP_BTN.01

7.11 CO.PP_BTN.01

7.12 CO.CCP_BTN.01

7.13 CO.CCP_BTN.01

7.14 CO.AR_BTN.01

7.15 EO.LG.01

7.16 EO.LG.02

7.17 EO.LG.03

7.18 EO.EPP_BTN.01

7.19 EO.AO_BTN.01

7.20 EO.RO_BTN.02

7.21 EO.VPO_BTN.01

7.22 EO.EOS_BTN.01

7.23 EO.VGM_BTN.01

8 Test Plan Results

8.1 Individual Test Results

8.1.1 Tables Of Individual Test Results For Customer

8.1.2 Tables Of Individual Test Results For Employee

8.2 Summary Of Test Results

All of the test cases have been executed and evaluated.

8.3 Exit Criteria

Exit Criteria is provided.