Test report for online movie ticketing system developed by ILSE

Inc, written by Luo linbo

1. The objective of testing effort and intended audiences

The objective is to to determine if the software satisfies the business

requirements. Besides that, it will identify invalid states and values in the
system. After integration of various modules, system integrity will be
stressed-tested of its stability. The intended audiences are our clients and
our supervisor Mr. Kevin Anthony Jones.

2. Testing strategy

 both verification and validation test

 constructive test
 testing accomplished by independent test group
 testing conducted independent of debugging
 test scope: unit testing and block testing (due to the limitation of
time)

3. Software product overview

The aim of the project is to implement a new online movie ticketing system
that enable:

 client to book movie online

 client to cancel movie booked
 client to view information of movie available
 client to choose their own seating
 administrator and user to access the same database through online
interface
 administrator to organize movie information online

The advantages of this new system are:

 database system is integrated as part of the online system

 online database does not need to be duplicated for offline database
 clients can pay and book movie through electronics transaction
 clients have flexibility in choosing the seating they like
 administrator can update online (system) database at real time

3. Test scope and Test plan

Our testing team will only conduct the unit testing and block testing due to
the limitation of time.
For unit test, we will employ both static and dynamic testing techniques.
Our basic component is the .java and .jsp file. Since the inspection and
compilation has already been done by programmer, we will only do the
walkthrough for static testing. After that, we will do the white-box testing.
The test cases will be derived from basis paths. So they will not be depicted
here. Our test completion criteria is the basic function of the module and
satisfaction for the requirement.

Forthe high level testing, we divide our program into two major block-
customer interface and administrator interface. Instead of the focus on
technique aspects, our main concern is the micro-behavior of each block.
The black box testing will be employed here. We will use equivalence
partitioning, boundary value and logic-based testing techniques for Test
Data Selection.

4. Outline of testing process

Pre-requisite: The programmer has completed the unit testing by

inspection and compilation.

5. Testing environment

5.1 Hardware

 The system is hardware-independent

5.2 Operating system

 Windows 2000
 Windows XP

5.3 Required software

  Java SDK 1.2
 Apache Tomcat 1.4.3
 Brower: Microsoft explorer 5 and above, Mozart, Netscape 6 and
above
 Microsoft Access 97 or later
 Java ODBC driver

6. Roles and responsibilities

6.1 Test team

Test Controller: Luo Linbo

Test Engineer : Hartono Kasman & Choong Hon Ye

6.2 Test support team

Support programmer: Tan Chiew Hua & Yeo Tze Choog

7. Testing phases and cycles

7.1 Validation testing cycle

7.1.1 The system requirement validation

Testing procedure:

 The refined client requirement is carefully studied.

 Appropriate objects with services and attributes are studied and mapped to
the class diagram produced by designers.
 Every service in classes is matched with corresponding functions required in
the system.

Sample Test case:

 Client’s requirement 1: “The user logs in by giving his credit card ID and
his password. He selects whether he wants to book some
his tickets or cancel his tickets which he had booked earlier. If he wants to
cancel then it’s possible only if two or more hours are left for the movie. The
system has tovalidate all this.”
Client objects Designer objects
Credit card ID Credit_Card (Database)
Password Password (Database)
Tickets NA
 Client services Designer services
Login NA
Book forward (Booking)
Cancel forward (Cancel)
Validate forward (Validate)

7.1.2 The implementation validation

Testing procedure:

 The syntaxes of functions implemented are compared to the functionality

documentation in the class diagram.
 The relationship of among objects is compared to the relationship among
classes in the class diagram. e.g.. Multiplicity, associative and aggregation
relation.
 The work flow of the system implemented is matched with the working
sequence provided by the client.

7.2 Verification testing cycle

7.2.1 Unit testing

We adopt white box testing in this stage. This testing was carried out on
individual which is the .java file that programmer have designed.

(a) static testing

we did the walkthrough of the whole program. All the names of the variables are
scrutinized to make sure that they are truly reflective of the element they
represent. Some syntax errors and logic errors were captured in this phase.

(b) Dynamic testing

Component was checked and the flow graph wad constructed from the
analysis. The test cases was derived from the path path.

Basis Path testing for Admins package:

Method Flow V(G) Basis Path

graph &
test
cases
Movieedit(String) Click 6 Path 1: 1-2-3-5-6-7-8-9-10-11-12-13-14-15
Here Path 2: 1-2-3-1-2-3-5-6-7-8-10-11-12-13-14-15
Path 3: 1-2-3-5-6-7-8-6-7-8-10-11-12-13-14-15
Path 4: 1-2-3-1-2-3-5-6-7-8-6-7-8-10-11-12-13-11-12-
13-14
 Path 5: 1-2-4-5-6-7-8-10-11-12-13-14-15
Path 6: 1-2-4-5-6-7-9-10-11-12-13-14-15
Custdel(String) Click 3 Path 1: 1-2-3...
Here Path 2: 1-2-3-5-6
Path 3: 1-2-4-5-6

Basis Path testing for Customer package:

Flow V (G) Basis Path

graph &
Method test
cases
BookingRequest. Click 3 Path 1: 1-2-3...
Here Path 2: 1-2-4-5-6
Process( ) Path 3: 1-5-6
CancelRequest Click 3 Path 1: 1-2-3...
Here Path 2: 1-2-4-5-6
Process() Path 3: 1-5-6

7.2.2 Block testing

Graph-Based Testing

Administrator Block:
Test Cases and Results:

Login module

Test Data Selection method: Equivalence Partitioning

Test Case Purpose Result Expected

Output?
(Y/N)

User Name: java Test if login module for Login successful : Y

administrator working redirected to Online
Movie Ticketing
Password : sun administrator main
page

User Name: java Test if login module for Login unsuccessful : Y

administrator working redirected to invalid login
page which asks user to
Password : 000000 re-input the information

Add movie module

Test Data Selection method: Boundary Value Analysis (Note: only the input
ticket price is tested using this method. The ticket price should be in the
range 4 to 15)

Assumption: All the other necessary inputs are valid

Test Case Purpose Result Expected

Output?(Y/N)

Ticket price:$7 Check if the movie Movie was added Y

with normal price can successfully
(valid input) be added
Ticket price:$4 Check if the movie Movie was added Y
with lower boundary successfully
(lower boundary) price can be added
Ticket price:$15 Check if the movie Movie was added Y
with upper boundary successfully
(upper boundary) price can be added
 Check if the system
Ticket price:$3 Movie was
will handle the invalid
still added N
price which is lower
(invalid input) unconditionally
than boundary

Ticket price:$20 Check if the system

Movie was
will handle the invalid
still added N
price which is higher
(invalid input) unconditionally
than boundary

Ticket price: ABC Check if the system

Movie was
will handle the invalid
still added N
price which is not an
(invalid input) unconditionally
numerical value

Edit movie properties module

Test Data Selection method: Equivalence Partitioning

Classes:

The time interval is 2 hours

The time interval is less than 2 hours

The time interval is greater than 2 hours

Assumption: All the other necessary inputs are valid

Test Case Purpose Result Expected

Output?(Y/N)

Start time:2.30 Check if the movie Movie was added Y

with correctl duration edited
End time:4.30 can be edited

(valid input)
Start time:2.30 Check if the movie Movie was still N
with the duration edited wrongly
End time:9.30 higher than the
correct one will
(invalid input) generate error
message
Start time:2.30 Check if the movie Movie was still N
with the duration edited wrongly
End time:3.30 lowerr than the correct
one will generate error
(invalid input) message
Add customer, remove customer, and edit customer properties
modules's test cases was derived similarly

Customer Block

Booking Movie Module

Test Data Selection method: Equivalence Partitioning

Assumption: All the other necessary inputs are valid

Test Case Purpose Result Expected

Output?(Y/N)

Name: Luo Check if the user with Movie was added Y

valid credit no can edited
Credit No:1111- book the movie
1111-1111-1111
Name: Luo Check if the user with The data was Y
invalid credit cannot reseted
Credit No:0000- book the movie
0000-0000-0000
Cancelling Movie Module

Test Data Selection method: Equivalence Partitioning

Assumption: All the other necessary inputs are valid

Test Case Purpose Result Expected

Output?(Y/N)

Name: Luo Check if the user with Movie was Y

valid credit no can cancelled edited
Credit No:1111- cancel the movie
1111-1111-1111
Name: Luo Check if the user with The data was Y
invalid credit cannot reseted
Credit No:0000- cancel the movie
0000-0000-0000

7. Testing tool sugggested for the future testing in the project

Rational TestManager Version 2002 is suggested to do the future

testing. However, due to the limitation of time, we don't apply it in this
stage. The reason for choosing this tool is that it is adapable to the change
in the requirement. Rational TestManager provides the important ability to
trace the impact of requirements and other changes by automatically
flagging potentially impacted test cases. Such tool will ease the process of
the testing, and even in the maintainence stage.

8. References

Pressman S. Roger., Software engineering: A practitioner's

Approach, fifth edition McGraw-Hill 2001