0% found this document useful (0 votes)
26 views13 pages

2 Solved Test Plan

Uploaded by

Kuroko Moi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views13 pages

2 Solved Test Plan

Uploaded by

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

1.

a) A company has designed it’s computerized pay-roll system to


handle the following activities :
a) Provide the user with payslip, containing basic, all
allowances
all deductions.
b) Stores the employee information.
c) Secure the employee information.
d) Print various reports
e) Provide compatibility with mainframe and PCS on LAN.
Design the test plan string scope, risk, strategies, schedules,
control
Procedures, environment etc. and other desired details.
INDEX
1. Introduction
Overview of the system
Purpose of the document
2. Scope
3. Test Requirement
4. Test Strategy
Types of testing
5. Hardware and software requirements
6. Control Procedures
7. Functions to be Tested
8. Resources and Responsibilities
9. Suspension/Exit criteria
10.Dependencies
11.Risk
1. INTRODUCTION

Overview of System :

The computerized Pay roll System will be fully automated.


Automation of the LMS will have an edge over existing manual system as it
will speed up the work, efficiency, reliability, security, maintenance etc.
Paper work will get reduced as no more register works and the librarian job
will become more easy – as issuing of books, returning, re-issuing,
generating reports (say for e.g.: new editions of a week), directing members
of the library to a particular book by seeing the details of any book in the
computer (e.g.. its location), automatic records of member fines, automatic
updating of the due dates, will be done with just few clicks

Purpose of this Document:

At a high level, this System Test intends to prove that :-


The functionality, delivered by the development team, is as specified
by the business in the Business Design Specification Document and the
Requirements Documentation.
The software is of high quality; the software will replace/support the
intended business functions and achieves the standards required by the
company for the development of new systems.
The software delivered interfaces correctly with existing systems,
including Windows.
This document describes the plan for testing the British Council
Library Management System.This test plan support following objectives:
List the recommended test requirements.
Recommend and describe the testing strategies.
Identify the resources and provide effort estimation.
List the deliverables
2.Scope:
This Test Plan applies to system tests that will be conducted on the
British
Council Library Management System.This plan is providing Black box
testing that will cover testing of all module interfaces.This test plan applies
to all requirement and specification of the British Council Library
Management System like:
Searching of the data.
Adding of data.
Maintenance of the books.
Issue, reissue and returning of books.
Calculation of fine and maintenance of the defaulters
Requisition and reservation.
Generation and maintenance of the records.

3.Test Requirements:
Test requirement identifies the items like use cases, requirements.
The following list will decide what will be tested.
Verify access to database
Verify member search Use case
Verify book,cd,vcd,conference report search Use case
Verify industrial report,project report searchUse case
Verify handbook search Use case
Verify issue Use case
Verify reissue Use case
Verify fine use case
Verify requisition and reservation Use case
Verify report Use Case
Verify skip entry Use case
Verify administrator entry Use case
Verify Sr.librarian entry Use case
Verify librarian entry Use case
Verify ease of navigation
Verify response time in case of search
Verify Installation and u installation on system
4.Test strategy:

Test strategy presents how testing of software application will be


done. Test strategy is the techniques to be used and the criterion for knowing
when the testing is completed. Testing should be executed in controlled
conditions including both normal & abnormal conditions.

Types of testing:

1. Verification: In this testing we verify whether application satisfies


all specifications. Verification is:
Are we building the product right?

2. Database testing: In database testing we ensure that all database


access methods work properly and without corrupting data.

3. Usability testing: Usability testing ensure that this application is


user friendly and user can get sufficient instructions to operate this
application. All the navigations are working properly.

4. Functionality testing: Functionality testing ensure that each


module work according to its designated functionality. In functionality
testing each button is tested according to its functionality.

5. Performance testing: Performance testing measures response


times, transaction rates, throughput time, turnaround time. The goal of
Performance testing is to verify and validate the performance requirements
have been achieved.
Performance testing is performed with different-different load,
configuration and peak load.

6. Recovery Test: Recovery test will force the system to fail in a


various ways and verify the recovery is properly performed.It is vitally
important that all data is recovered after a system failure and no corruption
of data occurred.

7. Look and Feel testing: Look and feel testing ensures that the
appearance and color combination is good. Look and feel testing is
performed with various display settings, browser settings & platform
settings.

8. Monkey Testing: The system should be tested randomly to findout


the unexpected results.

5.Hardware and Software Requirement:

1) compatible PC workstations with LAN or internet connection.


2) Microprocessor.
3) 64MB RAM and above.
4) 5GB Hard Drive.
5) Windows 98 and above.
6) Internet explorer 5.0 minimum.

6.CONTROL PROCEDURES:

Reviews: The project team will perform reviews for each phase(ie
requirement review,design review,code review,test plan review,test case
review and final test summary review).A meating notice with related
documents will be emailed to each participants.

Bug Review Meetings: Weekly meeting will be held to discuss report


defects.The development department will provide ststus/updates on all
defects reported and the test department will provide addition defect
information if needed.All member of the project team will participate.

Defect Reporting: When defects are found the testers will complete a defect
report on the defect tracking system. The defect tracking systems is
accessible by testers, developers andall members of the project team.When a
defect has been fixed or more information is needed the developer will
change the status of the defect to indicate the current state. Once a defect is
verified as fixed by testers the testers will close the defect report.
7.FUNCTIONS TO BE TESTED:

Searching – through item code, item name, publisher, author, keywords


Members – Adding, Search & Viewing (Editing, Deleting)
Books - Adding, Search & Viewing (Editing, Deleting)
Coordinators - Adding, Search & Viewing (Editing, Deleting)
Issue – validate if reserved or check for reference copy.
Return and Reissue– Check for fine and reissue if not reserved.
Fine – Automatic updation of fine, listing of current submissions
Settings: Change library settings like amount for fine, no of days of
return
Reports Generation

8.Resources and responsibilities:

Resources:

The team will consist of:

2 project manager
1 test lead
2 Sr. Test Engineers
2 Test Engineers

Responsibilities:

Project Manager: Responsibility for project schedules


and the
overall success of the project.
Participate on CCB
Serves as a primary liaison between
the
Development department and the
project team.
Participate on CCB

Test Lead: Ensures the overall success of


STLC.He/She
Will coordinate weekly meetings and
will
communicate the testing status to the
project team.
Participate on CCB

Testers: Responsibility for performing the


actual system
Testing

End Users: Will assist in performing the Beta and


user
acceptance testing.

DESIGNATION NAME TASK ASSIGNED


Project Manager Neeraj Goyal Requisition &
Reservation
Project Manager Hadi Hussain Settings
Test Lead Tina Mahajan Members and Security
Sr.Test Engineer Priya Paul Report
Sr.Test Engineer Parangat Mukul Search & Enquiry &
Item
Test Engineer Amit Kshirsagar Issue,Reissue & Fine
Test Engineer Rohit Mahajan Issue,Reissue & Fine

9.Suspension/Exit Criteria:

The Exit Criteria detailed below must be achieved before the Phase 1
software can be recommended for promotion to Operations Acceptance
status. Furthermore, I recommend that there be a minimum 2 days effort
Final Integration testing AFTER the final fix/change has been retested

 All High Priority errors from System Test must be fixed and tested
 If any medium or low-priority errors are outstanding - the
implementation risk must be signed off as acceptable by Business
Analyst and Business Expert
 Project Integration Test must be signed off by Test Controller and
Business Analyst.
 Business Acceptance Test must be signed off by Business Expert.

Resumption Criteria:

If testing is suspended , resumption will only occur when the problem(s) that
caused the suspension has been resolved. When a critical defect is the cause
of the problem the “FIX” must be verified by the test department before
testing is resumed.

Assumptions:

 Software will be delivered on time.


 Software is of the required quality.
 The software will not be impacted by impending Y2K compliance
changes to the external software infrastructure - i.e. any external
software changes will have to be compatible with this application.
 All "Show-Stopper" bugs receive immediate attention from the
development team.
 All bugs found in a version of the software will be fixed and unit
tested by the development team before the next version is released.
 Functionality is delivered to schedule.
 Required resources available.
 All service agreements will be met.
 The automated test tool will function & interface correctly with the
software.
 All documentation will be up to date and delivered to the system test
team.
 Functional and technical specifications will be signed off by the
business.
 All service agreements will be met.
 The Intranet will be fully functional prior to project commencement.
10.Dependancies:

Personnel Dependencies:

The test team requires experienced testers to develop,perform and validate


tests.the test team will also need the application developers and end users.

Software dependencies:

Internet explorer 5.0 and above, Netscape Navigator,Windows


98,NT,2000,XP,ME.

Hardware dependencies:

Pc(with specified hardware/software) and database should also be made


available to the testers for use during testing.

Test Data and Database:

Test data(mock industry information) and database should be made available


to the testers for use during testing.

11.Risks:

Schedule:

The schedule for each phase is very aggressive and could affect testing. A
slip in the schedule in one of the phases could result in a subsequent slip in
the test phase.Close project management is crucial to meeting the forecast
completion date.

Management:

Management support is required so when the project falls behind,the test


schedule does not get squeezed to make up for the delay the Management
can reduce the risk of delay by supporting the test team throughout the
testing phase and assigning people to this project with the required skill.

Personnel:

Due to the aggressive schedule it is very important to have experienced


testers on this project.Unexpected turnovers can have impact on the
schedule.If attrition does happen all efforts must be made to replace the
experienced individual.

Classification of Bugs:

1. An "A" bug is a either a showstopper or of such importance as to


radically affect the functionality of the system i.e. :
- Examples of showstoppers
- If, because of a consistent crash during processing of a particular
type of application, a user could not complete that type of
application.
- Incorrect data is passed to legacy system resulting in corruption or
system crashes
- Example of severally affected functionality
- Calculation of repayment term/amount are incorrect
- Incorrect credit agreements produced
2. Bugs would be classified as "B" where :
- a less important element of functionality is affected
- Example : a value is not defaulting correctly and it is necessary to
input the correct value
- data is affected which does not have a major impact
- Example : where, for instance, some element of client capture was
not propagated to the database
- there is an alternative method of completing a particular process
- Example : a problem might occur reading all the details of a credit -
this change can be manually input.
3. "C" type bugs are mainly cosmetic bugs i.e. :
- incorrect / no help text on screens
- drop down lists repeat an option

Q Test Plan:
Write detail test plan for online registration & examination application. Candidate will
register through valid email ID & will book date & time slot from available dates & time
slots. Candidate will select subject from list of subjects given. Application will send user
ID & password to the candidates email ID. On the date & time, candidate will login with
given user ID & Password Application will display multiple choice questions & will
accept choice from candidate. At the end of given time, application will display the
marks.

Solution :

Test Plan for Online Registration & Examination Application


1. Introduction
This test plan covers the testing approach, test scenarios, and test cases for the online
registration and examination application. The application allows candidates to register
using a valid email ID, book a date and time slot for their exam, select a subject, and take
the examination.
2. Objectives
 Ensure the registration process is smooth and error-free.
 Validate the email verification and user ID/password generation.
 Confirm the booking system functions correctly.
 Test the login process with the provided credentials.
 Verify the display and functionality of multiple-choice questions.
 Ensure the correct calculation and display of marks.
3. Scope
The scope of testing includes functional, usability, and performance testing of the
registration and examination application.
4. Test Environment
 Browsers: Chrome, Firefox, Safari, Edge
 Operating Systems: Windows, macOS, Linux
 Devices: Desktop, Laptop, Tablet
5. Testing Strategy
 Functional Testing: Validate all functional requirements.
 Usability Testing: Ensure the application is user-friendly.
 Performance Testing: Check the application's performance under various
conditions.
6. Test Scenarios and Test Cases
Scenario 1: Registration
 Test Case 1.1: Validate the registration form.
o Steps: Open registration form, enter valid email ID, submit form.
o Expected Result: Email verification link is sent.
 Test Case 1.2: Validate email verification.
o Steps: Click on verification link sent to email.
o Expected Result: User is redirected to a page to set a password.
 Test Case 1.3: Validate setting user ID and password.
o Steps: Set user ID and password, submit form.
o Expected Result: User ID and password are created, confirmation email is
sent.
Scenario 2: Booking Date & Time Slot
 Test Case 2.1: Validate date and time slot selection.
o Steps: Login, navigate to booking page, select available date and time slot,
submit selection.
o Expected Result: Selected slot is booked and confirmation email is sent.
Scenario 3: Subject Selection
 Test Case 3.1: Validate subject selection.
o Steps: Login, navigate to subject selection page, select subject from list,
submit selection.
o Expected Result: Selected subject is saved and confirmation email is sent.
Scenario 4: Examination Process
 Test Case 4.1: Validate login on exam day.
o Steps: Login with user ID and password on exam date and time.
o Expected Result: User is able to login successfully.
 Test Case 4.2: Validate display of multiple-choice questions.
o Steps: After login, start examination.
o Expected Result: Multiple-choice questions are displayed correctly.
 Test Case 4.3: Validate submission of answers.
o Steps: Select answers for multiple-choice questions, submit answers.
o Expected Result: Answers are recorded correctly.
 Test Case 4.4: Validate calculation and display of marks.
o Steps: Complete exam, submit all answers.
o Expected Result: Marks are calculated and displayed to the user.
7. Exit Criteria
 All test cases have been executed.
 All critical and major defects have been resolved.
8. Test Deliverables
 Test Plan
 Test Cases
 Test Summary Report
 Defect Report
9. Resources
 Testers
 Test Manager
 Development Team (for fixing defects)
10. Schedule
 Test Planning: [Start Date] to [End Date]
 Test Case Development: [Start Date] to [End Date]
 Test Execution: [Start Date] to [End Date]
 Defect Resolution: [Start Date] to [End Date]
 Test Closure: [End Date]

You might also like