Scribd
Upload
62 views5 pages

CH3 - Static Techniques: Quick Notes

This document discusses static testing techniques. It defines static testing as testing at the specification or implementation level without software execution. The advantages of static testing are that it can start early and rework costs are low. It also describes the phases of a formal review process like planning, kick-off, individual preparation, review meeting, rework and follow-up. It outlines roles in reviews and different types of reviews like informal, walkthroughs, technical reviews and inspections. Success factors for reviews and code metrics like cyclomatic complexity are also summarized.

Uploaded by

Blabla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
62 views5 pages

CH3 - Static Techniques: Quick Notes

This document discusses static testing techniques. It defines static testing as testing at the specification or implementation level without software execution. The advantages of static testing are that it can start early and rework costs are low. It also describes the phases of a formal review process like planning, kick-off, individual preparation, review meeting, rework and follow-up. It outlines roles in reviews and different types of reviews like informal, walkthroughs, technical reviews and inspections. Success factors for reviews and code metrics like cyclomatic complexity are also summarized.

Uploaded by

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

Quick Notes

CH3 – Static Techniques

Number of Questions – 3 (K1-2, K2-1, K3-0) Duration – 60 minutes

1] Static Techniques and Test Process

Static Testing – Testing of a component or system at the specification or


implementation level without execution of that software.

Dynamic testing – Testing that involves execution of the software of a component


or system.

Advantages of static testing:

Can start early in the cycle, rework cost are low

Contributes to increase awareness of quality

2] Phases of a formal review

a) Planning - Selecting the personal, allocating roles, defining entry and exit
criteria for more formal reviews etc.

b) Kick-off - Distributing documents, explaining the objectives, checking entry


criteria etc.

c) Individual preparation - Review the work products before the review meeting
by each reviewer, Note the findings, questions and comments etc.

d) Review meeting - Discussion or logging, make recommendations for handling


the defects, or make decisions about the defects etc.

e) Rework - Fixing defects found, typically done by the author

Quick Notes 3: Static Techniques


Created by: Sagar Joshi 1
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
f) Follow-up - Checking the defects have been addressed, gathering metrics and
checking on exit criteria

3] Roles and responsibilities

a) Manager - Decides on execution of reviews, allocates time in projects


schedules, and determines if the review objectives have been met

b) Moderator - Leads the review, including planning, running the meeting, follow-
up after the meeting.

c) Author - The writer or person with chief responsibility of the document(s) to be


reviewed.

d) Reviewers - Individuals with a specific technical or business background.


Responsibility is to identify defects and describe findings.

e) Scribe (recorder) - Documents all the issues, problems, Generally author can
perform the scribe role

4] Types of review

a) Informal Review – No formal process, Undocumented, Pair programmer or a


technical lead reviewing designs and code, inexpensive way to get some benefit.

b) Walkthrough – Meeting led by the author, ‘scenarios, dry runs, peer group’,
open-ended sessions., A step by step presentation by the author in order to gather
information and to establish a common understanding, Main purpose: learning,
gaining understanding, defect finding

c) Technical Review – Documented, Defined defect detection process, Ideally lead


by trained moderator, Involved peers and technical experts, No management
participation, Purpose: discuss, make decisions, find defects, solve technical
problems and check conformance to specifications and standards

Quick Notes 3: Static Techniques


Created by: Sagar Joshi 2
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
d) Inspection – Lead by trained moderator not the author, Uses entry and exit
criteria, usually peer examination. Defined roles, includes matrices, formal
process, pre-meeting preparation, formal follow-up process, Inspection Led by
trained moderator (not the author), usually peer examination, defined roles,
includes metrics, formal process, pre-meeting preparation, formal follow-up
process. Main purpose: find defects.

Note: walkthroughs, technical reviews and inspections can be performed within a


peer group-colleague at the same organization level. This type of review is called a
“peer review”.

5] Success factors for reviews

 Each review should have a clear predefined objective.


 Selecting the right people for the review objectives are involved.
 Defects found are welcomed, and expressed objectively.
 People issues and psychological aspects are dealt with (e.g. making it a
positive experience for the author).
 Review techniques are applied that are suitable to the type and level of
software work products and reviewers.
 Checklists or roles are used if appropriate to increase effectiveness of
defect identification.
 Training is given in review techniques, especially the more formal
techniques, such as inspection.
 Management supports a good review process (e.g. by incorporating adequate
time for review activities in project schedules).
 There is an emphasis on learning and process improvement.

6] Code Matrics

 There are many different kinds of structural measurements, Cyclomatic


Complexity is one of them.

Quick Notes 3: Static Techniques


Created by: Sagar Joshi 3
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
 Complexity matrices identify high risk, complex areas of the software.
 20% of the code cause 80% of the problems

Cyclomatic Complexity –

 The number of independent paths through a program.


 Cyclomatic Complexity is defined as: L – N + 2P where L = the number of
edges/links in a graph, N = the number of nodes in a graphs, P = the number
of disconnected parts of the graph (connected components)
 Alternatively one may calculate Cyclomatic Complexity using decision point
rule - Decision points +1

7] Code Structure

a) Control flow structure –

 Addresses the sequence in which the instructions executed


 Iterations and loops in a program designed
 Finds unreachable code

b) Data flow structure -

 An abstract representation of the sequence and possible changes of state of


data objects
 Where the state of an object is created, usage, modification or destruction

c) Data structure -

 Refers to the organization of the data itself, independent of the program


 When data is arranged as a list, quest, stacks or other well defined structure

Quick Notes 3: Static Techniques


Created by: Sagar Joshi 4
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/
8] Static Analysis Measures

 Cyclomatic complexity of 10 or over should be addressed


 Commented code of 10% or less suggested to be addressed
 Repetitive code of 9 or more suggested to be addressed

Quick Notes 3: Static Techniques


Created by: Sagar Joshi 5
https://www.udemy.com/istqb-foundation-level-certification-ctfl-training/

You might also like