Scribd
Upload
12 views2 pages

Fundamentals of Software Testing Discuss On The Error Checklists in The Inspection Process

Uploaded by

Devi Ashritha Ambitus
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
12 views2 pages

Fundamentals of Software Testing Discuss On The Error Checklists in The Inspection Process

Uploaded by

Devi Ashritha Ambitus
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/ 2

Subject: Fundamentals of Software Testing

Q: Discuss on the Error Checklists in the Inspection process.


The checklist serves as a guide for the inspection process, but it should not
replace the human judgment and expertise of the reviewers. The checklist
should be used as a tool to aid the inspection process and not as a rigid rule.
Software Inspection processes generally call for Checklist simply to provide
reviewers with hints and some recommendations for determining and
identifying defects during inspection of Software Product.
The inspection process should always need to be driven by checklist of some
common programming errors. An inspection checklist is simply an
assurance that specific software product has been inspected. An inspection
checklist should be developed by discussion with some experienced staff
and as well as regularly updated as more experience is gained from
inspection process. Guidebook generally includes checklist simply for
various artifacts such as design documents, requirements, etc.
Different checklist is also prepared for various programming Language.
Checklist for source code are given separately for different source
languages. There are some of the items of checklist that are general and
therefore require good deal of human judgment. Some possible checks that
can be made during the inspection process are given below:
1. Data Faults :
 Check Are all of the variables of program initialized before their values
are used?
 Has all constant been given name?
 Is there any chance of buffer overflow? Etc.
2. Control Faults :
 Is the condition correct for each conditional statement?
 Is each loop certain to terminate?
 Are compound statements bracketed correctly or not?
3. Input/ Output (I/O) Faults :
 Are all of the input variables used or not?
 Are all of the output variables assigned to a value before they are
output?
 Can input that are unexpected causes of corruption? Etc.
4. Interface Faults :
 Does all method and functions have the correct number of
parameters?
 Do the type of parameters i.e. actual and formal matches?
 Are the parameters present in the correct order?
 Do they have the same model of shared memory structure, if all of the
components access shared memory?
5. Storage Management Faults :
 Have all links been reassigned correctly, if a linked structure is
modified?
 Has space been correctly allocated, if dynamic storage is used?
 Does the space get de-allocated explicitly after it is no longer
required? Etc.
6. Exception Management Faults :
 Do all possible error conditions been taken into account or
consideration?
Example:
1. Requirement Inspection Checklist :
 Do requirements exhibit a clear distinction among functions and data?
 Do requirements exactly define all the information that is needed to be
displayed to users?
 Do requirements address system and user response to all conditions
of error?
 Is each of the requirements stated clearly, concisely, and
unambiguously?
 Is each of the requirements testable?
 Are there any ambiguous or implied requirements present?
 Are there any conflicting requirements?
 Are there areas that are not addressed in the Software Requirements
Specification (SRS) that is needed to be?
 Are performance requirements like response time, data storage
requirements, etc. stated?

You might also like