Assessment Evaluation

Online Book Store

Phase-III

Submitted in partial fulfillment of the requirements of the degree of

Master of Software Engineering

Vamsi Krishna Mummaneni

CIS 895 – MSE Project
Kansas State University

Committee Members
Dr.Torben Amtoft (Major Professor).
Dr. Dan Andresen.
Dr. Mitchell L. Neilsen.

1
 Table of Contents

1
1. Introduction................................................................................................................... 3
2. Manual Testing.............................................................................................................. 3
3. Test Cases……………………………………………………………………………...3
3.1 User…………………………………………………………………………………...3
3.3 Admin…………………………………………………………………………………5
4. Performance Testing..................................................................................................... 6
5. Observations………………………………………………………………………….10
6. References…………………………………………………………………………… 11

2
 1. Introduction
The goal of this document is to present all the test results using the test cases
defined in the Test Plan Document. I have performed Manual and Performance testing for
my Online Book store project.

2. Manual Testing
Manual testing is done to test the correctness of all the functionalities by manually
entering the data.

Test case functionalities for manual testing include:

USER:
• Registration
• Login
• Add To Cart
• Edit Cart

ADMIN:
• Create and Delete book from Category
• Create and Delete a Category
• Manage Orders
• Manage Members

3. Test Cases

3.1 USER

Registration

ID TEST CASE USER INPUT RESULT PASS CRITERIA

U_REG_1 User Registration User selects already existing user PASSED Display message to
name choose different
user name
U_REG_2 User Registration User enters different password in PASSED Display message

3
 password confirm field that Password and
Confirm Password
fields don't match
U_REG_3 User Registration User forgets to enter a particular PASSED Display message
required fields The value in field is
required
U_REG_4 User Registration User enters all the details PASSED User account
successfully created

Login

ID TEST CASE USER INPUT RESULT PASS CRITERIA

U_LOG_1 User Login User enters a wrong PASSED Display message Login or
username Password is incorrect.
U_LOG_2 User Login User enters a wrong PASSED Display message Login or
password Password is incorrect.
U_LOG_3 User Login User enters correct PASSED User logs in successfully
username and password

Add to Cart

ID TEST CASE USER INPUT RESULT PASS CRITERIA

U_AC_1 Add to Cart User selects a book and PASSED Book is added to the shopping cart
clicks add to cart button
U_AC_2 Add to Cart Guest selects a book and PASSED User should create an account.
clicks add to cart button

Edit Cart

ID TEST CASE USER INPUT RESULT PASS CRITERIA

U_EC_1 Edit Cart User changes the Quantity PASSED Quantity and total cost
of Cart should be updated
U_EC_2 Edit Cart User deletes a book from PASSED Books and total cost of Cart should
shopping Cart be updated
U_EC_3 Edit Cart User selects a new book to PASSED Books and total cost of Cart should
shopping Cart be updated

4
 3.2 ADMIN
Create and Delete a Book from Category

ID TEST CASE ADMIN INPUT RESULT PASS CRITERIA

AD_CDB_1 Create and Delete a Admin adds a new book to PASSED Book should be updated
Book from Category category in Categories list
AD_CDB_2 Create and Delete a Admin deletes a book PASSED Book should be deleted
Book from Category from category in Categories list

Create and Delete a Category

ID TEST CASE ADMIN INPUT RESULTS PASS CRITERIA

AD_CDC_1 Create and Delete Admin adds a new PASSED Category should be
a Category category updated to system

AD_CDC_1 Create and Delete Admin deletes a PASSED Category should be

a Category category deleted from system

Manage Orders

ID TEST CASE ADMIN INPUT RESULTS PASS CRITERIA

AD_MO_1 Manage Orders Admin accepts an order PASSED Order is processed

AD_MO_2 Manage Orders Admin deletes an order PASSED Order is not processed

5
 Manage Members

ID TEST CASE ADMIN INPUT RESULTS PASS CRITERIA

AD_MM_1 Manage Members Admin accepts Members PASSED Member is accepted

AD_MM_2 Manage Members Admin deletes Members PASSED Member is not accepted

4. Performance Testing

The system should meet the performance requirements as mentioned in the Vision
document. The performance will be evaluated based on the response time of the GUI and
the database commands. Using JMETER tool performance testing will be done.

Apache JMETER is a 100% pure Java desktop application designed to load test
functional behavior and measure performance. Originally designed to test web
applications, it is now a general tool for testing client/server applications like database
servers, FTP servers and others. It lets you test your applications under different work
loads, and graphically represent the application's behavior.

I have tested the performance of three different pages of my Online Book Store
Website as mentioned in the Test Plan document during Phase-2.

Pages Tested

• Home Page
• Search Page
• Shopping Cart Page

Initially The Performance testing has been done using a sample of 8 threads which are
generated with a loop of 100.

6
 Home Page

http://localhost:3062/vamsi-bookstore/Default.aspx

The graph below in Fig.1 shows the test results of Homepage of Online Book Store
Website.

Performance Graph

Fig.1

7
Search Page

http://localhost:3062/vamsi-bookstore/Books.aspx?

The graph results below in Fig.2 shows the test results of Search Page of Online Book
Store Website.

Performance Graph

Fig.2

8
Shopping Cart Page

http://localhost:3062/vamsi-bookstore/ShoppingCart.aspx?

The graph results below in Fig.3 shows the test results of Shopping Cart Page of Online
Book Store Website.

Performance Graph

Fig.3

9
Below are the observations made from the above performance graph for Online Book
Store Project.

• The average value represents the average amount time taken to load a particular
page.
• Average response time is low for home page because it doesn’t many database
interactions.
• Average response time for Search page is more since it should wait for the results
from the database.
• The throughput number represents the actual number of requests/minute the
server handled.
• Here the overall throughput is around 74/sec
• The deviation characterizes the network and the system performance.
• If the deviation is high, some users will have good response time from the system
while other users will have long response time from the system.
• The smaller deviation value is good.

Later again I have done the performance testing with a sample of 1000 threads with a
loop count of 1000 and ramp up period of 1sec.Below are the graphs for all three pages.
.

10
Home page

The graph below in Fig.1 shows the test results of Homepage of Online Book Store
Website.

Fig.4

11
Advanced search page with parameters

The graph below in Fig.4 shows the test results of Searchpage of Online Book Store
Website.

Fig.5

12
Shopping Cart

The graph below in Fig.6 shows the test results of Homepage of Online Book Store
Website.

Fig.6

13
Observations

Since the total number of request increased to 10,000 when compared to 800 before all
the performance graph parameters will increase.

The response time is more for shopping cart page since there are more data base actions
to be taken place and also from different tables. So since it has data transactions with
different tables, to run the query and wait for results it would count for the response time.

Similarly the response time is less for search page when I passed category value as
parameter is because may be the search criteria is very easy and straight forward from a
single table data in the database.

As observed from the second case of performance graphs the response time is more for
home page when compared to search page because the home page for the Online Book
store application needs data to be requested from the database to load the page. So due to
extensive data access from the database to retrieve data, images to be derived from the
database, handle may user read requests and may also depend on the limited hardware
resources.

But the response time increases linearly with number of users. And after some time the
response time will reach a saturation level at the end of 10,000 user requests.

Since all the three pages have response time less than 5 sec in general the application is a
good application. In general users will be happy to use the website with a response time.

I have chosen a maximum of 1000 users due to the hardware capabilities of my system.

14
References

1. file:///C:/Documents%20and%20Settings/Owner/Desktop/jakarta-jmeter-
2.3RC3/docs/usermanual/build-adv-web-test-plan.html

2. http://en.wikipedia.org/wiki/Manual_testing

15