Chapter Five

Testing and Results

Introduction

The main purpose of the test plan for the Airline Reservation System is to discuss the testing
details of the use cases of the Airline Reservation System. The software project test plan also
describes the objective, scope, and approach of the software testing effort for the Airline
Reservation System project. The test plan for the Airline Reservation System also indicates the
personnel responsible for each task and also specifies the risks associated with the test plan

Objectives

The main objectives of the test plan for the Airline Reservation System are as follows:

 To identify the features of the system that will be tested.

 To identify and define all the activities necessary to prepare for and conduct the testing
process on the Airline Reservation System
 To define the pass/fail criteria for each item that will be tested.
 To identify the deliverables of the testing phase.
 To define any suspension criteria and resumption techniques
 To discuss the testing techniques being used to test the Airline Reservation System.

Manual Test Plan

NO DESCRIPTION

1 User Page Test

2 Customers Page Test

Test Case Result Summery

The summary of the test case result has been depicted in the table shown below: These are the
test cases for the User/Customer pages.

A major part of testing has been concentrated on the customer pages, as they would be the main
clients of the Flight Booking Website.

User Page Testing Result Summery

 TEST CASE # DESCRIPTION RESULTS/COMMENTS

TC#1 User Login Passed

TC#2 User Registration Passed

TC#3 Flights Passed

TC#4 Passengers Passed

TC#4 Places Passed

TC#5 Tickets Passed

TC#6 Weeks Passed

Customer Page Testing Result Summery

TEST CASE # DESCRIPTION RESULTS/COMMENTS

TC#7 Search Flights Passed

TC#8 Book Flights Passed

TC#9 Customer Ticket Information Passed

TC#9 Payment Proceeding Passed

TC#10 Printing Ticket Passed

Manual Testing

To start with, I have performed manual testing on the Airline Reservation System web
application. Manual Testing is one of the oldest and rigorous methods of software testing. This
testing strategy gives the best opportunity to check every page thoroughly and make sure it
works in the expected manner. Due to the complexity of the various automation tools and the
time available for testing the entire web application, I preferred to use manual testing because it
is one of the best methods of testing suggested for a beginner.

All the test cases mentioned in the Test Plan document were tested here. The results of the
manual testing are represented in the following tables:

User Login Manual Testing

 TEST UNIT TEST CASE RESULT

Log In Button An invalid username (which The system generates a

is the email id in this case) or message saying “invalid user
password is entered by the id” or invalid password,
user whichever is the case.

Log In Button A valid username and The system logs on the user
password are entered by the and transfers him to the
user booking page

User Registration Manual Testing

TEST UNIT TEST CASE RESULT

New User button Wrong format entered in the The system prompts a
input fields of the registration message to the user saying
(Used for Register) page that he has entered a wrong
format in the input fields.

New User button Passwords and Confirm The system generates a

Password fields do not match message to the user saying
in the registration page “please enter the confirm
password field” again.

New User button Data Fields left out empty in The system prompts a
the registration page. message to the user asking
him to fill the empty fields he
has left out

New User button Correct data entered into the The system accepts the
fields in the register page details of the customer and
then logs him onto the system
and displays the page where
he can search and book for
flights, packages, and hotels
Flights Manual Testing

TEST UNIT TEST CASE RESULT

Flights Wrong format of information The system generates an error

entered the data fields of the message to the user indicating
flight booking page that the wrong format of data
is entered and to re-enter the
data

Flights Wrong date format, in the The systems generate a

date of journey data field, message to the user saying
wrong flight number in the that he has entered an invalid
Flight Number fields etc., date format and incase of
(similarly for all the other wrong flight number, indicates
data fields of the Flight that his entry is invalid.
Search page)

Flights Correct format of data is The system allows the users to

entered into the data fields in book the flight by providing
the flight booking page. details required and directs
them to the booking
confirmation page

Passengers Manual Testing

TEST UNIT TEST CASE RESULT

Passengers Wrong format of information The system generates an error

entered the data fields of the message to the user indicating
Passengers that the wrong format of data
is entered and to re-enter the
data
 Passengers Correct format of data is The system allows the users
entered into the data fields in to add passenger info by
the passenger’s page providing details required and
directs them to the booking
confirmation page

Places Manual Testing

TEST UNIT TEST CASE RESULT

Places Wrong format of information The system generates an error

entered the data fields of the message to the user indicating
places that the wrong format of data
is entered and to re-enter the
data

Places Correct format of data is The system allows the users

entered into the data fields in to add places by providing
the place’s page details required and directs
them to the flight search page

Tickets Manual Testing

TEST UNIT TEST CASE RESULT

Tickets Wrong format of information The system generates an error

entered the data fields of the message to the user indicating
tickets that the wrong format of data
is entered and to re-enter the
data

Tickets Correct format of data is The system allows the users

entered into the data fields in to add tickets by providing
the ticket’s page details required and directs
them to the flight search page
Weeks Manual Testing

TEST UNIT TEST CASE RESULT

Weeks Wrong format of information The system generates an error

entered the data fields of the message to the user indicating
weeks that the wrong format of data
is entered and to re-enter the
data

Weeks Correct format of data is The system allows the users

entered into the data fields in to add number of flights in
the week’s page the week and directs them to
the flight search page

Customer page Manual Testing

I've started by manually testing the web application for the airline reservation system. One of the
most traditional and exacting ways of software testing is manual testing. This testing technique
offers the best chance to carefully examine each page and ensure that it functions as intended.
Because manual testing is one of the best testing techniques advised for a novice, I opted to
utilize it due to the intricacy of the numerous automation tools and the time available for testing
the full web application.

The Customer page Manual Testing cases mentioned in the Test Plan were tested here. The
results of the manual testing are represented that.

The Customers can search for the flights they want by filling in information about the type of
flight they want, and they can choose between the flights they want by prioritizing them in terms
of money or time, which facilitates customer satisfaction. Customers can fill in their details to
cut the ticket, and finally, customers pay the required amount.

Performance Testing

In general performance testing can be defined as one form of testing where we test the system to
determine how fast the system performs under a particular workload. Several other features of
the system such as scalability and security etc. can also be tested under the performance testing
phase. For the performance testing of the Airline Reservation System, I have used the JMeter
tool. The Apache JMeter is a 100% pure Java desktop application which has been designed to
load test functional behavior and measure performance. This tool has been originally designed
for Web Applications, which has now been extended to a variety of other functions.

The Apache JMeter can be used to performance test both static and dynamic sources. With
JMeter I was able to test various combinations of load types on the Airline Reservation System
web application and analyze the strength of the system.

The inputs to the JMeter tool, generally used for the performance testing of a web application
would be as follows:

 Number of Threads /Users – The total number of people sending requests to a web page
 Ramp-Up Period - The Ramp Up period would be the time taken by J Meter to create and
make sure that all the threads are up and running.
 Loop Count – It would be the value which determines the number of times that the test
should be carried out.

The criteria selected to be the input to the JMeter tool for the Airline Reservation System would
be explained later in the document. For the performance testing of the Airline Reservation
System, I have chosen three kinds of pages.

 Home Page of the Airline Reservation System - It deals with people just accessing the
home page of the Airline Reservation System. There is no database activity involved
here. So, this would be one good choice http://127.0.0.1:8000/
 Login Page of the Airline Reservation System- This is the page where the user logs
onto the home page of the system and is redirected to the Booking.aspx page after he logs
in. So, here it involves authentication and some database activity. This would be another
good choice.
 Flight Search and Booking Page of the Airline Reservation System Here, the user
searches for the available flights in the database of flights available and makes a
reservation for a specific flight. There is a lot of database activity involved with the flight
search page. The results of the JMeter testing are as follows for each of the above-
mentioned pages:
Screenshots Of Flight Booking Website

a. User Page
b. Customer Page
I. Searching Flights

II. Booking Flights

III. Customer Information Entry

IV. Payment Details

V. Ticket Confirmation
VI. Printing Ticket