Copy of Hotel booking test strategy

1. About Project

1.1. Project goals

1.1.1. - Hotel Booking System - Available 24/7 - System available for users from different countries

1.2. Technical description

1.2.1. - Communication with clients by using REST API - The data centers are in the United States and Russia - A single database are in the US - System Available 24/7

2. Functional testing

2.1. The server correctly process incoming requests (create/read/update/delete booking objects)

2.2. The server correctly responds to requests

2.3. All servers receive timely information about data changes.

3. Perfomance testing

3.1. How fast the system processes incoming requests and sends responses

3.2. Increasing the number of incoming requests per unit of time. Check the number of concurrent incoming requests. The behavior of the system at excessive number of requests.

3.3. Clients from different countries the default must be connected to the nearest servers for yourself. Network optimitation

4. Testing of data consistency

4.1. Race condition

4.1.1. How the server processes the request to read data, while another server carries out change / delete the same data

4.1.2. synchronous requests on booking the same room when requests processed by one server and two servers

4.2. Transactions

4.2.1. Third party is requesting booking the room, but this room is already on the booking stage. Check two scenarios when requests processed by one server and two servers

4.2.2. How the system processes incomplete transaction at the time when it unexpectedly aborted or canceled correctly

5. Reliability testing

5.1. Working system for a long time and after large quantity of requests processed

5.2. Redirect requests to another server if the default server is not available

5.3. How the server processes requests, at the time when database is not available

5.4. Check the database backup. Check the database recovery from backup.

5.5. The ability to restore the system state based on the history of transactions if damaged database (if applicable)

6. Security

6.1. Data encryption, certificates, signatures, if applicable.

6.2. Reliability of protection against DoS attacks

7. Scalability

7.1. Support new servers. How easy it would be to add.

7.2. Escalating the number of users compared to the current number of users. Are servers and database ready to it?

7.3. Increase in number of hotels and rooms

7.4. Possibility of booking through the system not only a hotel rooms, but also, for example, a restaurants. How easy it would be to add.

7.5. How easy is it to add a new database, for example, in the Russian Federation and synchronize two databases. How easy is scalable this system.

7.6. Ability to add new localization

8. Compatibility

8.1. Hardware compatibility

8.2. Software compatibility (verification work of the system with the software components which it supports or with which may be conflict)

8.3. Work on the supported operating systems

9. Stress testing

9.1. The system is in a hardware resource deficiency: RAM, disk space, processing power, a slow data transfer rate (variable MTU?)