Scribd
Upload
24 views20 pages

16-Module 4-23-02-2024

Static testing techniques check software products for conformance with specifications without executing the software and include inspections, walkthroughs, and reviews. Inspections are the most widely used technique which involve roles like author, inspector, moderator, and recorder reviewing a product in a formal process to find defects early.

Uploaded by

M TEJAS KUMAR
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
24 views20 pages

16-Module 4-23-02-2024

Static testing techniques check software products for conformance with specifications without executing the software and include inspections, walkthroughs, and reviews. Inspections are the most widely used technique which involve roles like author, inspector, moderator, and recorder reviewing a product in a formal process to find defects early.

Uploaded by

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

Chapter 6

Static Testing

1
Chapter 6
Static Testing

Objectives

• Static testing also improves the software quality.


• There are bugs which are detectable only through static testing.
• There are 3 types of static testing: Inspection, Walkthroughs and
Reviews
• Inspections are the most widely used technique for static testing
which is a formal process to detect the bugs at early stage.
• Benefits and effectiveness of inspection process
• Variants of Inspection process
• Walkthrough is a less formal and less rigorous method as
compared to inspection.
• Review is higher level technique as compared to inspection or
walkthrough, as it also includes management.

2
Static Testing

• Static testing techniques do not demonstrate that the software is


operational or one function of software is working;

• They check the software product at each SDLC stage for


conformance with the required specifications or standards.
Requirements, design specifications, test plans, source code,
user’s manuals, maintenance procedures are some of the items
that can be statically tested.

• Static testing has proved to be a cost-effective technique of error


detection.

• Another advantage in static testing is that a bug is found at its


exact location whereas a bug found in dynamic testing provides
no indication to the exact source code location.

3
Static Testing
Evolution of Software Testing
Types of Static Testing

• Software Inspections

• Walkthroughs

• Technical Reviews

4
Inspections

• Inspection process is an in-process manual examination of an item


to detect bugs.

• Inspection process is carried out by a group of peers. The group of


peers first inspects the product at individual level. After this, they
discuss potential defects of the product observed in a formal
meeting.

• It is a very formal process to verify a software product. The


documents which can be inspected are SRS, SDD, code and test
plan.

5
Inspections

• Inspection process involves the interaction of the following


elements:

• Inspection steps
• Roles for participants
• Item being inspected

6
Inspections

Inspection Team

• Author / Owner / Producer

• Inspector

• Moderator

• Recorder

7
Inspection Process

8
Inspection Process
Software Testing Myths
Benefits of Inspection Process
• Bug Reduction
• Bug Prevention
• Productivity
• Real-time Feedback to Software Engineers
• Reduction in Development Resource
• Quality Improvement
• Project Management
• Checking Coupling and Cohesion
• Learning through Inspection
• Process Improvement

9
Variants of Inspection process

10
Active Design Reviews

11
Formal Technical Asynchronous
review method (FTArm)

12
Gilb Inspection

13
Humphrey’s Inspection Process

14
N-Fold Inspection

15
Reading Techniques

• A reading technique can be defined as a series of steps or


procedures whose purpose is to guide an inspector in acquiring a
deep understanding of the inspected software product.

• Ad-hoc Method

• Checklists

• Scenario based Reading

16
Scenario based Reading

Perspective based Reading


• software item should be inspected from the perspective of
different stakeholders Inspectors of an inspection team have to
check software quality as well as the software quality factors of
a software artifact from different perspectives.
Usage based Reading
• This method given is applied in design inspections. Design
documentation is inspected based on use cases, which are
documented in requirements specification.
Abstraction driven Reading
• This method is designed for code inspections. In this method,
an inspector reads a sequence of statements in the code and
abstracts the functions these statements compute.

17
Scenario based Reading

Task driven Reading


• This method is also for code inspections . In this method, the
inspector has to create a data dictionary, a complete description of
the logic and a cross-reference between the code and the
specifications.
Function-point based Scenarios
• This is based on scenarios for defect detection in requirements
documents [103]. The scenarios, designed around function-points
are known as the Function Point Scenarios. A Function Point
Scenario consists of questions and directs the focus of an
inspector to a specific function-point item within the inspected
requirements document.

18
Structured Walkthroughs

It is a less formal and less rigorous technique as compared to


inspection. The very common term used in the literature for static
testing is Inspection but it is for very formal process. If you want to
go for a less formal having no bars of organized meeting, then
walkthroughs are a good option.

19
Technical Reviews

A review is similar to an inspection or walkthrough, except that the


review team also includes management. Therefore, it is considered a
higher-level technique than inspection or walkthrough.

A technical review team is generally comprised of management-level


representatives of the User and Project Management. Review agendas
should focus less on technical issues and more on oversight than an
inspection.

20

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy