1. Introduction

1.1. Version Control

Version Control part will be specified after finishing the project.

1.2. Overview

In this test plan document, the purpose is to test the functions of the Restaurant Reviews according to Geographical Location project according to the Software Requirement Specification (SRS) and Software Design Description (SDD) files that were uploaded in the CENG-407 project.

1.3. Scope

This test plan document has test cases for User Type Choice (Logged User and Anonymous User), Log-In (also for Logged User and Anonymous User), Commenting (Making Review and Comment, Give Rating), Showing Reviews and Filtering. Each of these functions will be detailed in this document.

1.4. Glossary

2. Features to be tested

2.1 Open Page (OP)

The start page contains basic buttons to interact with the application such as sign up and sign in.

2.2 Login Up (LU)

Members using the app enter an email and password. Then click the Sign Up button and the account should be created successfully

2.3 Login (LG)

Users enter their email and password. After clicking the Member Login button, it redirects to the homepage.

2.4 Filtering (FR)

It includes features such as food type and distance. The user clicks on the desired filtering feature and selects the save button. Afterwards, suitable restaurants are listed.

2.5 Give Rate (GR)

Users give points to the restaurants they go to. These scores are then kept and averaged.

2.6 Show Reviews (SR)

Users can access the comments by clicking the show reviews button.

2.7 Give Reviews (GR)

Members can make critiques and recommendations about the restaurant they go to by clicking on the comment section.

2.8 Mapping (MP)

It runs location information and directions that take users to the restaurant they want.

3. Features not to be tested

Technical work related to the hardware of the mobile device will not be tested. Features such as whether the internet connection is working will not be tested during the test scenario.

4. Pass/Fail Criteria

If given function is handling the way it is detailed in Software Requirement Specification (SRS) and Software Design Description (SDD), then the function passes the test case; else the task fails. There might be some further time or performance constraints for certain tasks which are going to be detailed further.

4.1. Exit Criteria

In this document, “H” refers to Highest priority and “M” refers to Medium priority. If all the High (also called “H”) and Medium (also called “M”) priority cases are passed the product is considered to be successful. Optional priorities will be discussed later.

5.Test Cases

5.1 Login Part

5.2 Reviewing Part

5.3 Searching Part

5.4 UserError Part

6.Detailed Test Cases

6.1 LG.US01

6.2 LG.US02

6.3 LG.US03

6.4 LG.US04

6.5 GR.RS01

6.6 GR.RS02

6.7 GR.RS03

6.8 GR.DR01

6.9 GR.SR01

6.10 FR.TF01

6.11 MP.SL01

6.12 UE.RL01

6.13 UE.RL02

6.14 UE.RL03