logo

Software Testing

   

Added on  2023-04-21

8 Pages1409 Words125 Views
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjkl
zxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmrtyuiopasdfghjklzxcv
Software Testing
Cloud-based Personal Insulin Pump
1/1/2019

Software Testing
Table of Contents
Test Plan................................................................................................................................................2
Test Plan Identifier............................................................................................................................2
Version History.............................................................................................................................2
References.....................................................................................................................................2
Introduction.......................................................................................................................................2
Purpose..........................................................................................................................................2
Scope.............................................................................................................................................2
Background...................................................................................................................................2
Test Items..........................................................................................................................................2
Software Risk Issues..........................................................................................................................3
Features to be tested..........................................................................................................................3
Features not to be tested....................................................................................................................3
Approach...........................................................................................................................................3
Item Pass/Fail Criteria.......................................................................................................................3
Suspension Criteria and Resumption Requirements..........................................................................4
Test Deliverables...............................................................................................................................4
Remaining Test Tasks.......................................................................................................................4
Environmental Needs........................................................................................................................4
Staffing, Training Needs & Responsibilities.....................................................................................4
Schedule............................................................................................................................................5
Planning Risks and Contingencies.....................................................................................................5
Approvals..........................................................................................................................................5
Testing Practice.....................................................................................................................................5
Testing Method..................................................................................................................................5
Test Cases & Test Results.................................................................................................................5
Lessons Learned................................................................................................................................6
References.............................................................................................................................................7
1

Software Testing
Test Plan
Test Plan Identifier
Author: Test Manager
Contact: testmanager@pip.com
Version History
Version Number Type Date
1.0 Draft 01-01-2019
References
Quality Assurance Plan, Software Requirements Specification
Introduction
Purpose
The purpose of the test plan is to illustrate the mechanisms and processes that will be used
and applied to maintain the quality of cloud-based personal insulin pump.
Scope
The primary audience for the plan is the development team comprising of four requirement
analysts & testers and six trained developers. The plan is also developed for the project
stakeholders and management.
Background
Personal Insulin Pump (PIP) is a cloud-based external device that mimics the function of the
pancreas. There are embedded sensors integrated in the system to keep a track of the blood
sugar level and automate the insulin insertion process as per the need. The hardware
components used in the system include needle assembly, sensor, pump, controller, alarm,
displays, and clock. There are functional, non-functional, and user requirements that shall be
met by the system.
Test Items
Control Software
Hardware Components
o Needle Assembly
2

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Quality Assurance Plan
|10
|1867
|219

SCEI Website Report & Test Plan
|7
|1455
|316

Literature Review on Testing Methods
|9
|2294
|482

Code Repository: Benefits and Popular Options
|6
|1097
|444

Risk Management Software & Preferred Option
|8
|2053
|91

Information Technology – Software Upgrade Project Proposal
|14
|2698
|68