1. Introduction

This document is intended to give a simple test planning of a systematic strategy for the restaurant booking website. The restaurant manager is composed of numerous features. This test plan is actually designed to ensure those features wok up to the mark. Both directly and indirectly affected elements will be addressed here.

In the following paragraphs, we will discuss the purpose of the plan, its scope and define the acronyms used in the document.

1.1 Scope

Testing will begin at the component level and work toward the integration of the entire system. This document will mainly provide the blueprint of high-level testing approaches to the restaurant manager website. It will provide a guide to the test engineers. It will validate the major system functions of the restaurant manager against customer requirements. So the whole software specification will be strictly followed in every step. As the system has multiple features and pressed for delivery time. We have prioritized the features and testing will take place according to this priority.

2. Test Items

In this section, we will provide a list of all those components that have been identified test items. It is assumed that unit testing will be done through functional testing. The interfaces between the following subsystems will be tested:

• Landing page
• Booking Page
• Confirmation Page
• View Order page

The external interfaces to the following browser will be tested:

• Google Chrome
• Safari
• Mozilla Firefox

The basic performance test:

• TBD

The most critical performance measures to test are:

1. Response time for requested services

3. Features to be tested

The following is a list of the areas to be focused on during testing of the application.

4. Features not to be tested

The following is a list of the areas that will not be specifically addressed.

• TBD

5. Test Automation Framework

The framework will setup base on Cypress, version 4.1.0

6. Process Overview

The following represents the overall flow of the testing process:

1. Identify the requirements to be tested. All test cases shall be derived base on requirements and design.
2. Test data and test case reviewing to ensure that the test module has been fully tested and test data and test case suit for it.
3. Identify the expected result for each test
4. Test framework set up
5. Organize the test cases
6. Perform the tests
7. Successful unit testing is required before the unit is eligible for component integration testing
8. Unsuccessful testing requires generating a bug on bug tracking system or a bug report task. It should include bug description, replicate process and environment if required.
9. The bug has to be verified after fixing it.