Professional Documents
Culture Documents
Software Testing Mini Project Report Compress
Software Testing Mini Project Report Compress
BAKTAVATCHALAM.G (08MW03)
MASTER OF ENGINEERING
of Anna University
May 2009
BAKTAVATCHALAM.G (08MW03)
MASTER OF ENGINEERING
May 2009
Acknowledgement
ACKNOWLEDGEMENT
i
SYNOPSIS
The Article Information System has been developed for easily maintaining the
information about articles and customers in the article system and to help customers to
search and view articles without visiting the library. This system replaces current manual
process of maintaining records of articles and publishing new articles about the customers
which are highly time consuming.
The Article Information system has an online catalogue using which the
customers can login, search, and publishes articles online. Customers can search articles
by title, author name and keywords. The members can view their user account. One
member is allowed only to view only subscribed articles. Unregistered members can
search for articles. New members can join by filling an online registration form.
Reviewers can login, search, accept and reject articles which are submitted by the
customers online. Each customer is subscribed to a particular period and if it expires then
he must obtain a new subscription. Single customer may possess different types of
subscription as they need.
i
TABLE OF CONTENTS
1. Introduction………………………………………………………………………..1
2. Requirement Analysis……………………………………………………………..2
2.1. Vision and Scope..............................………………………………...3
2.5. Prototype...…………………………………………………………30
3. Design……………………………………………………………………………35
4. System Implementation……………………………….…………………………35
5. Testing……………………………………………………………………………
5.1. JUnit Test Cases……………………………………………………..46
ii
1. INTRODUCTION
This chapter provides a brief overview of the problem definition, objectives and
significance of the project and an outline of this report.
This section describes the hardware and software specifications for the development of
the system and an analysis on the feasibility of the system. This section includes:
2.3 Usecases
2.5 Prototype
Vision and Scope Document
for
Prepared by G.BAKTAVATCHALAM
21-01-2009
Vision and Scope for Article Information System Page iv
Table of Contents
Revision History
1. Business Requirements
1.1. Background
Nowadays the Articles which are produced and collected in an Article Organization are increased
day by day and the amount of information residing in that Organization is growing indefinitely. So the
Manual Article Systems and its Maintenance is critical one.
Nowadays many online public digital library systems are available, but they do not consider the
private subscriptions and its security issues. But we provide a better security of various levels of
subscriptions of various levels of customers.
Our system provide better organization of articles and the specialized searching that finds needed
customer articles.
This system is successful if there is some increase of number of subscribed customers compare to
current customers count. Also our system is an additional one and it not replaces our old manual
system, so that there is no loss of current customers.
Also the management needs the better way of organizing, collecting, publishing the articles
FE-2: Secured Subscription for various levels of customers for various Articles
AS-2: Subscription is provided as per the cost of articles and subscriptions actually done using postal
and its pass code is given to our new system for accessing the articles.
AS-3: Free registered users only see the limited information about the Articles.
Feature Release 1
FE-1 Provides viewing of Title & Abstract
Release Features
Publisher codes for publishing, different level of subscription codes for article
2
accessing, enhanced search using article contents
4. Business Context
4.1. Stakeholder Profiles
Major Value
Stakeholder Attitudes Major Interests Constraints
Publish research
Educational and Institutional
articles, keep updates
Research Users relationship
on latest articles
Software Requirements
Specification
for
Prepared by G.BAKTAVATCHALAM
21-01-2009
Table of Contents
Revision History
Name Date Reason For Changes Version
IA-2: Testers
IA-5: Users
RS-1: Beginning with the overview sections and proceeding through the sections
5.5. References
1. Wiegers, Karl. Cafeteria Ordering System Vision and Scope Document,
www.processimpact.com/projects/COS/COS_vision_and_scope.doc
6. Overall Description
6.1. Product Perspective
The Article Information System overcomes current manual maintenance and it provides Systematic
approach to manage and maintain the Article System. The context diagram in Figure 1 illustrates the
external entities and system interfaces for release 1.0. The system is expected to evolve over several
releases.
Maintain Marketing
Management
Users Executives
Article
Publish, Subscribe Information
System
Finding, Subscribe
Educational and
Research Users Latest Topics Search Existing Customers
Article Storage
System
Figure 1 Context diagram for release 1.0 of the Article Information System
Educational and
Publish research articles, keep updates on latest articles
Research Users
Management
Manage the newly published articles, maintain the old articles
Users
Existing
Get inside and try different types of articles
Customers
Prepared by G.BAKTAVATCHALAM
Actors: Customers
Description: The customers may search for new/old articles with the specification of
author/issue date/title/keywords
Preconditions: All the information’s about the Articles(new & old) should be available
Postconditions: The Search History dumped into Storage for Future Analysis
1. The System displays the Search box for author name input
2. User types the author name and do searching
3. The System search the articles which are submitted by the given author
4. Then it will display the resulted articles to Users screen
5. User now view the articles relevant to his request and view the article one
by one
Alternative Flows: 1.1 Search Using Issue Date
Priority: High
Special Requirements: 1. The System must know the latest and old articles and its details.
Assumptions: 1. If the user is not logged then System only allows the minimal information
about articles.
Notes and Issues: 1. System must know the user is a Guests or Subscribed Customers
Actors: Customers
Description: The Article Management System provides multilevel Subscriptions and the
subscription code.
1. The System requests for user name, address, phone, password, subcode
2. User must enter the correct values and submit.
3. Now the system checks for subcode format and existence, then it will store
the user’s information along with validity period (generated by System
based on subcode).
4. The System informs the user as Information was saved.
5. Now the User can able to view subscribed articles and to post article for
publication
Alternative Flows: None
1. System informs user that given code is invalid format or not exist.
Includes: None
Priority: High
Assumptions: 1. The Subscribed User got the subcode via postal and he must enter the
same code here to view articles online
Notes and Issues: None
Actors: Customers
Description: The Subscribed Users may have an opportunity to publish their articles. To
publish the Article user must submit the article for reviewing. After review the
article is published.
Preconditions: User Must log in to our System to do this.
Includes: None
Priority: High
Assumptions: None
Use Case Name: Login For accessing Subscribed Articles and View the Articles
Actors: Customers
Description: The Subscribed Users may login into their account to see updated articles and
any information regarding to his article submission or to do submission.
1.2 Logout
Includes: None
Priority: High
Assumptions: None
Actors: Reviewer
Description: The Subscribed Users may have an opportunity to publish their articles. To
publish the Article user must submit the article for reviewing. After review the
article is published. Now the reviewer views the each Article and do
accept/reject.
Exceptions: None
Includes: None
Priority: High
Assumptions: None
A web application which enable the article library members to search for
Description: articles, subscribe and view books online. The customer can search new
articles and publish new articles.
Date Updated:
Overview
Test plan objectives To ensure that the Online Library Management System will:
- Function consistently and reliably in accordance with current
business operations.
- Meet or exceed user requirements and technical specifications.
- Not adversely impact other systems or the existing technology
environment.
Testing Assumptions - It is assumed that there are few reviewers and customers whose
personal details, username and password are already stored in the
database.
- The subscription codes of each customer are assumed to be unique.
Risks & Contingencies The following risks apply to the testing process and may impact either the
proposed date of readiness for the deployment of Article Information System,
or the comprehensive level of testing that can be performed in each of the
Functional Units:
- The actual deployment of Article Information System may take longer to
perform than anticipated, as the admin is also using the same
database for maintenance.
Test Scope
Features to be Tested All features, forms, reports and interfaces affected by the Article
Information System will be tested. These include:
- Login forms
- User manual
- Online help
- Logout
- Articles for session
- Database used for both authentication and validation
Features Not to be Tested - Data integrity and system functionality contained within the
Conventional Article Information System and which is not Online
Article Information System dependant, will not be tested under the
scope of this project.
Test Methodologies
Testing Approach The following approach will be used to test the Online Library
Management System
- Article Information System integration & system testing will be
conducted to provide an initial stable testing environment as follows:
• Integration Testing: Ensure operability of Article Information
System application within each of the new modules.
• System Testing: Ensure that all the test databases are
accessible for testing.
- Test cases and associated scripts for user acceptance testing are
created.
- For testing the functional specification the unit testing is performed
by the developer using JUnit.
- After Integration, system and acceptance testing user sign-off is
performed.
- Once user sign-off is received, then the actual deployment is
performed.
Test Documents The following test documents will be created and maintained throughout
the project lifecycle:
- Article Information System Test Plan
- Master test case lists for each of the following functional units:
Login, Search, Subscribe, Review, Publish, Update status, Logout.
- Test case scripts for each test case recorded in the master test case list
- Log of all problems encountered during the testing phase of the
project
Test Case Pass/Fail Each Test Case will be evaluated against the acceptance criteria as
Criteria outlined in the test case scripts to determine if the test passed or failed. In
the case of a failure, the tester will assign a severity to the problem using
the appropriate priority rating system established within Tracker for each
application.
Suspension/Resumption Test Cases that do not run to completion will be evaluated on a case by
Criteria case basis to determine if the testing must start over or resume at the point
where the failure occurred. In extremely long test cases, checkpoints will
be established for resumption in the middle of a test case where
appropriate. In general, a test may be resumed in the middle when the
error is not critical.
Problem Errors identified through testing will be logged. Resolve the problem
Logging/Resolution according to the deemed severity level, and update the master test case list.
Once the problem has been fixed, record the resolution into the database.
The failed test case will then be retested using the same test case script that
detected the error in order to verify that the problem has been rectified.
Resources
Environmental Needs In order to conduct comprehensive end-to-end system and user testing are the
networked system where the functional and non-functional testing is
performed.
Actual Testing (execution - Testing environment has Start Apr 14, 2009
of Test Case Scripts) been set up
- Integration & System
Testing has been
completed
- Test Case Scripts have
been developed
Final Functional User - Deployment of Online Apr 21 , 2009
Acceptance Testing & Library Management
Sign-off system
Prototype
for
Prepared by G.BAKTAVATCHALAM
25-02-2009
Help Page
Home Page
Article Submission
Subscription
Reviewing
Search
User’s Home
System Design
for
Prepared by G.BAKTAVATCHALAM
Customer
Login
Reviewer
View Articles
Class Diagram:
Review ArticleUtil
ServerManager
Articles
keys[] ClientManager
serverReader
serverWriter getArticles()
getKeys()
distribute() search()
sendArticles() sendResults()
sendKeys()
getACount()
Sequence Diagram:
Login:
5: UserInfo
6: validate user
7: invalid user
8: Re-direct to home
Register:
5: success
6: display status
Review:
1: Requested Articles
2: Req Articles
3: Articles
4: Articles
5: accept/reject
Search:
1: author/idate/title/contents
2: getArticles
3: Searching
Help:
4: help info
5: formatted help
Collaboration Diagram:
Login:
2: validate code
6: validate user
Customer
1: Enter Subcode and pwd
5: UserInfo
DBManager
Register:
5: accept/reject
DBManager
2: Req Articles
Reviewer1: Requested Articles
AIS
3: Articles
4: Articles
Search:
AIS
1: author/idate/title/contents 3: Searching
2: getArticles
Customer 5: formatted info
4: Article Result Set
DBManager
Help:
Customer
1: req help topic
AIS 3: search
4: help info
DBManager
Activity Diagram:
invalid
invalid code
valid user
display retrieve
articles articles get articles
articles
result set
format
articles
author/idate/keys/title
search search finding
get articles
articles
result set
show articles formatting
articles
Component Diagram:
AIS Crawler
DB
Manager
Deployment Diagram:
Crawler
AIS
Distributed
Network
6. TESTING
Test Scenario
With HTTPUnit, Java programs can access servers directly, without the need for a web
browser. HTTPUnit provides an API for interacting with HTML, submitting forms, following
hyperlinks, setting cookies and many other tasks associated with web browsers.
Test Scenario:
import com.meterware.httpunit.*;
import junit.framework.*;
The load and performance testing is done using the tool Load-Runner and the results
obtained are shown below. The system is simulated for 30 vusers.
Running Vusers
Hits per Second
Transaction Summary
Overall Report
Mercury WinRunner is the powerful test automation solution for the enterprise. It helps
you automate the testing process, from test development to execution. You create adaptable and
reusable test scripts that challenge the functionality of your application. Prior to a software
release, you can run these tests in a single overnight run—enabling you to detect defects and
release software of superior quality.
You can also convert existing WinRunner tests to scripted components, or create new scripted
components. Scripted components are part of Business Process Testing in Mercury Quality
Center, which utilizes a keyword-driven methodology for testing applications. Scripted
components are reusable modular scripts that can be created in WinRunner, and then used in
business process tests.
# _login
set_window("_login",86);
edit_set("subcode","admin");
obj_type("subcode","<kTab>");
password_edit_set("pwd","c9faca5c644fe0f0");
button_press("Login");
# _search
set_window("_search",5);
edit_set("keys","the");
button_press("Search");
# search
set_window("search",6);
button_press("example3");
# view
set_window("view",1);
button_press("Close");
# search
set_window("search",4);
button_press("gmb");
# view
set_window("view",1);
button_press("Close");
DSN=gmb;UID=scott;PWD=tiger1;SERVER=cseora;
select * from cust_ais
Thus the Article Information system was implemented successfully. This will help the
customers to search, view and publish articles online. Also the reviewer can do accept/reject for
submitted articles. This system helps Article System to remove the various bottlenecks in
maintaining manual records and also the members need not go to the article library for searching
articles.
Future Enhancement:
This Article Information system can be extended for Distributed Library. The search can
be further refined by categorizing based on various factors like education, entertainment etc. The
system can be further enhanced by providing facility for online payment of registration charges
using credit cards, automatically sending emails to customers intimating overdue and cancelled
reservation.