0% found this document useful (1 vote)
609 views

Test Plan-Online Library System.

This document outlines a test plan for testing an online library system. It details the objectives, background, strategies, assumptions, test items, features to be tested, completion criteria, deliverables, environment needs, responsibilities, staffing and training, and scheduling for testing the system. Black box and white box testing methods will be used to test functionality and code, with the goal of detecting errors. Test cases will cover modules for books, publishers, journals, and magazines. The plan specifies pass/fail criteria, required resources and staff, and a schedule for testing the different modules.

Uploaded by

Sumit Rajput
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
609 views

Test Plan-Online Library System.

This document outlines a test plan for testing an online library system. It details the objectives, background, strategies, assumptions, test items, features to be tested, completion criteria, deliverables, environment needs, responsibilities, staffing and training, and scheduling for testing the system. Black box and white box testing methods will be used to test functionality and code, with the goal of detecting errors. Test cases will cover modules for books, publishers, journals, and magazines. The plan specifies pass/fail criteria, required resources and staff, and a schedule for testing the different modules.

Uploaded by

Sumit Rajput
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Software Quality Assurance (SQA)Plan

Doc.No. : LMN/01
Version No.: 01
Date : 25/11/2014

Q.1. Write a test plan with scope of testing risks and contingencies,
strategy, schedule, staffing and training, deliverables, item pass/fail
criteria for Online Library System
(20 marks)

1) General Objective: To detect errors from Library Management


System and check the
requirement specification and actual expected
results.

2) Background: Library Management System” mainly focuses on basic


operations in a
library
Adding new member,
new books,
updating new information,
searching books and members
facility to borrow and return books

3) Introduction : Data Recording


Data Transcription
Data Conversion
Data Verification
Data Control
Data Transmission
Data Correction

4) Strategies : Methodologies like


a. Black box –Functional testing of library mgmt.system –to
find top level of functional errors etc.
b. White box –Structural testing –code complexity, syntax
testing, code coverage testing is carried out.

5) Assumptions:
a) Is it possible to invoke each menu function using
logical assumptions that if all parts of the system are
correct?
b) System will support more than 1000 simultaneous
users

Prepared By : Approved By:

1|P a g e s u n i l k h i l a r i @ h o t m a i l . c o m 9 8 5 0 9 7 9 6 5 5
Software Quality Assurance (SQA)Plan
Doc.No. : LMN/01
Version No.: 01
Date : 25/11/2014

c) Database storage capacity of more than 1 lacs book


information.
6) Test Items :
a. Book.prg
b. User.prg
c. Publisher.prg
d. Journals.prg
e. Magazines.prg
7) Features to be Tested :
a) Accurate and integrating
b) Recovery from failure
c) Privacy and security
d) Ease of learning and use

8) Features not to be Tested:


a) Price of the system
b) Certification
c) Network bandwidth – standalone system
d) License agreement – open source system

9) Approach : select data capture method and devices, which reduce


the number of
stages.so as to reduce both the changes of errors and
the cost .Input
classification is done.

i. External
ii. Internal
iii. Operational

Input design is rather complex since it involves procedures


for capturing data as well as inputting it to the computer.

10) Item Pass:


a. Attractive Output Screen
b. Report Generation module – borrowed book list & Available
book list
c. Search Facility system – search for books and members.
d. User friendly interface
e. Fast access to database
Prepared By : Approved By:

2|P a g e s u n i l k h i l a r i @ h o t m a i l . c o m 9 8 5 0 9 7 9 6 5 5
Software Quality Assurance (SQA)Plan
Doc.No. : LMN/01
Version No.: 01
Date : 25/11/2014

f. Less error
g. More Storage Capacity
h. Search facility
i. Look and Feel Environment
j. Quick transaction
k. Tolerance for 10% less book storage capacity

11) Completion Criteria:

The users will have to be trained upon the new system such
as the screen flows and screen design type of
help on the screen.
Type of errors while entering the data, the corresponding
validation check at each entry and the way to correct the
data entered.
It should then cover information needed by the specific user
or group to use the system.
Sr.N Module Start Date End Date
o. Name
1 Book 01/02/2013 09/02/2013
2 Publisher 10/02/2013 19/02/2013
3 Journal 20/02/2013 28/02/2013
4 Magazines 29/02/2013 03/03/2013

12) Test Deliverables:


a) Test reports
b) Defect profile documents
c) Rework required list
d) Inspection report
e) Audit findings

13) Environment Needs:


a) Software for automated testing required
b) Reviewer committee with 4 members
c) Inspection checklist
d) Hardware -10 pcs and one server
e) Internet connectivity

14) Responsibilities:

Prepared By : Approved By:

3|P a g e s u n i l k h i l a r i @ h o t m a i l . c o m 9 8 5 0 9 7 9 6 5 5
Software Quality Assurance (SQA)Plan
Doc.No. : LMN/01
Version No.: 01
Date : 25/11/2014

Member Task Task Responsibi Sectio


lity n
End- Data Interact with system Check the A(1)
User Entry expected
result
QA Test Execution of plan & Workaround C(2)
Member Objectiv ensure the product about defect
e is defect free
Identify
QA Lead Test Plan Execution of plan & Measure & D(3)
ensure the product control
is defect free quality of
library
system
Develop Bug Fix the bug from all Maintain E(4)
er Fixing modules of system common
programming
style

15) Staffing & Training : Specify the number of testers required and
indicate the skills
they should have. Specify what training is required, both in
the system
under test and any test tools -For functional testing require
special
SQA group of having –
a) QA Lead – 1 No.
b) QA Team Member(Tester) -2 Nos.
c) Developers - modulewise –who has written the code

-Training need to give to QA lead and QA team members about


a) Open source s/w
b) Latest Browsers
c) Testing techniques (BVA/Equi.Partitioning etc.)

-Training about measuring scalability and reliability of SNS s/w product.

16) Test Scheduling:

Proje Module Name Develope Reviewer Date


Prepared By : Approved By:

4|P a g e s u n i l k h i l a r i @ h o t m a i l . c o m 9 8 5 0 9 7 9 6 5 5
Software Quality Assurance (SQA)Plan
Doc.No. : LMN/01
Version No.: 01
Date : 25/11/2014

ct r
Nam
e
LMS Books Puja Ajit 04/03/201
3
LMS Journals. Maruti Arun 05/03/201
3
LMS Magazines Rohit Shruti 06/03/201
3
LMS Instant Messaging Yogesh Vikas 07/03/201
3
LMS User Interface(UI) Nitin Ashu 08/03/201
3
LMS Search Opt. Apurva Ajit 09/03/201
3

17) Risk: Library data theft


a. Book information corruption
b. Book Data redundancy
c. ISBN No.wrong for publisher
d. Stress for system usage

18) Test Tools:


a) code quality - IBM Rational Analyzer
b) Bug Tracking Tools -Bug Rat,Bugzilla
c) Functional Testing Tools-Max Q
d) Performance Testing Tools-Grinder

19) Approvals:
Test Plan – -- get prepared by Mr.Arun ,QA Lead
-- get approved by Ms.Supriya ,QA Member
DFD --prepared By –Mr.Yogesh ,QA Memer
--Submitted to Ms.Puja ,QA Lead
Audit Report : Submitted to Ms.Priyanka,Chief Moderator

Prepared By : Approved By:

5|P a g e s u n i l k h i l a r i @ h o t m a i l . c o m 9 8 5 0 9 7 9 6 5 5

You might also like