tài liệu ISTQB CTFL Foundation Syllabus 2011

In
t

F
t
ernati
o
C
oun
d
o
nal So


C
ertif
i
d
atio
n
R
Ve
r
ftware
i
ed T
n
Le
v

R

eleased
r
sion 20
1
Testin
g
este
r
v
el S
y
1
1
g
Quali
f
r

y
llab
u
f
icatio
n
u
s
n
s Boa
r
r

d
Certi
f
Found
a


Version
2
© Internation
a

Copyrig
h
This do
c

Copyrig
h
ISTQB i
s

Copyrig
h
the IST
Q

Copyrig
h
Klonk,

R

Copyrig
h
Frieden
b

Copyrig
h
Klaus O
l

A
ll right
s

The aut
h
(ISTQB)
have ag
r

1)
A
ny
auth
and
afte
r
Nati

o
2)
A
ny
oth
e
cop
y
3)
A
ny
its t
r
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
h
t Notice
c
ument may
h
t Notice © I

n
s
a registere
d
h
t © 2011 th
e
Q
B WG Fou
n
h
t © 2010 th
e
R
ahul Verma
)
h
t © 2007 th
e
b
erg and Eri
k
h
t © 2005, t
h
l
sen, Maaret
s
reserved.
h

ors hereby
t
. The autho
r
r
eed to the f
o
individual o
r
ors and the
provided th
a
r
submissio
n
o
nal Board.
individual o
r
e
r derivative
y
right owner
s
ISTQB-rec
o
r
anslation) t
o
e

r
y
llabus

Q
ualifications Board
be copied in
n
ternational
d
trademark
e
authors fo
r
n
dation Leve
e
authors fo
r
)

e
authors fo
r
k
van Veene
h
e authors (
T
Pyhäjärvi,

G
t
ransfer the
c
r
s (as curren
t
o
llowing con
d
r
training co
m
ISTQB are
a
t any adve
r
n
for official
r
group of i
n
writings if t
h
s
of the sylla
o
gnized Nati
o
o

other partie

its entirety,
Software T
e
of the Inter
n
r
the update
l)
r
the update
r
the update
ndaal)
T
homas Müll
e
G
eoff Thomp
c
opyright to
t
t
copyright h
d
itions of us
e
m
pany may

u
acknowledg
e
r
tisement of
accreditati
o
n
dividuals m
a
h
e authors
a
bus.
o
nal Board
m
s.

Page 2 of
7
or extracts
m
e
sting Qualifi
c
n
ational Soft
w
2011 (Thom

2010 (Thom
2007 (Thom
e
r (chair), R
e
son and Eri
k
t
he Internati
o
olders) and
I
e
:
u
se this syll
a
e
d as the s
o
such a trai
n
o
n of the tr
a
a
y use this
s
a
nd the IST

m
ay translat
e
7
8
m
ade, if the
s
c
ations Boa
r
w
are Testin
g
as Müller (c
h
as Müller (c
h
as Müller (c
h
e
x Black, Si
g
k
van Veene
n
o
nal Softwa
r
I

STQB (as t
h
a
bus as the
b
o
urce and c
o
n
ing course
m
a
ining mate
r
s
yllabus as
t
QB are ack
e
this syllab
u
Q


s
ource is ac
k
r
d (hereinaft
e

g
Qualificatio
h
air), Debra
h
air),
A
rmin
B
h
air), Doroth
y
g
rid Eldh, Do
n
daal).
r
e Testing Q
u
h
e future co
p
b
asis for a tr
a
o
pyright own
m
ay mentio
n

r
ials to an
I
t
he basis for
nowledged
a
u
s and licen
s
Internatio
Software T
e
Q
ualification
s
31-Ma
r
k
nowledged.
e
r called IST
ns Board,
Friedenberg
B
eer, Martin
y
Graham,
D
rothy Graha

u
alifications
p
yright holde
a
ining cours
e
ers of the s
y
n
the syllab
u
I
STQB reco
articles, bo
o
a
s the sour
c
s
e the sylla
b
nal
e
sting
s
Board
r
-2011
QB®)

, and
D
ebra
m,
B
oard
r)
e
if the
y
llabus
u
s only
gnized
o
ks, or
c
e and
b
us (or
Certi
f
Found
a


Version
2
© Internation
a

Revis

Version
ISTQB
2
ISTQB
2
ISTQB
2
ISTQB
2
A
SQF V
ISEB V
2

f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
ion Hist
o

D
2
011
E
2
010
E
2
007
0
2
005
0
2.2
J
2
.0
2
e
r
y
llabus

Q
ualifications Board
o
ry
D
ate
E

ffective 1-
Ap
E
ffective 30-
M
0
1-May-200
7
0
1-July-2005
J
uly-2003
2
5-Feb-1999

p
r-2011
M
ar-2010
7

Page 3 of
7
Remark
s

Certified
Mainten
a
Notes

Certified
Mainten
a
Notes
Certified
Mainten
a
Certified
A
SQF S
y
“Lehrpla
n
ISEB So
f
25 Febru
7
8
s

Tester Foun
a
nce Releas
e
Tester Foun
a
nce Releas
e
Tester Foun
a

nce Releas
e
Tester Foun
y
llabus Foun
n
Grundlage
n
f
tware Testi
n
ary 1999
Q


dation Leve
l
e
– see
A
pp
e
dation Leve
l
e
– see
A
pp
e
dation Leve

l
e

dation Leve
l
dation Level
n
des Softw
a
n
g Foundati
o
Internatio
Software T
e
Q
ualification
s
31-Ma
r
l
Syllabus
e
ndix E – R
e
l
Syllabus
e
ndix E – R
e

l
Syllabus
l
Syllabus
Version 2.2
a
re-testens“
o
n Syllabus
V
nal
e
sting
s
Board
r
-2011
e
lease
e
lease
V
2.0
Certi
f
Found
a


Version

2
© Internation
a

Table

A
cknowl
Introduc
t
Purp
o
The
C
Lear
n
The
E
A
ccr
e
Level
How
t
1. Fu
n
1.1
1.1
1.1
1.1

1.1
1.1
1.2

1.3
1.4
1.
4
1.
4
1.
4
1.
4
1.
4
1.5
1.6
2. Te
s
2.1
2.1
2.1
2.1
2.2

2.
2
2.
2

2.
2
2.
2
2.3
2.
3
2.
3
2.
3
2.
3
2.4
3. St
a
3.1
3.2
3.
2
3.
2
3.
2
3.
2
3.3
4. Te
s
4.1

4.2
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
of Cont
e
edgements.
.
t
ion to this
S
o
se of this D
o
C
ertified Tes
t
n
ing Objectiv
e
E
xamination

.
e
ditation
.
of Detail
.
t
his Syllabus
n
damentals
o
Why is T
e
.1 Softwa
.2 Cause
s
.3 Role o
f
.4 Testin
g
.5 How M
What is T
Seven Te
Fundame
4
.1 Test Pl
4
.2 Test A
n
4

.3 Test I
m
4
.4 Evalua
4
.5 Test C
l
The Psyc
h
Code of
E
s
ting Throu
g
Software
.1 V-mod
e
.2 Iterativ
e
.3 Testin
g
Test Lev
e
2
.1 Comp
o
2
.2 Integr
a
2

.3 Syste
m
2
.4
A
ccept
Test Typ
e
3
.1 Testin
g
3
.2 Testin
g
3
.3 Testin
g
3
.4 Testin
g
Maintena
n
a
tic Techniq
u
Static Te
c
Review P
2
.1

A
ctiviti
e
2
.2 Roles
a
2
.3 Types
o
2
.4 Succe
s
Static An
a
s
t Design T
e
The Test
Categori
e
e
r
y
llabus

Q
ualifications Board
e
nts
.

S
yllabus
o
cumen
t

t
er Foundati
o
e
s/Cognitive
.

.

.

is Organize
o
f Testing (
K
e
sting Neces
re Systems
C
s
of Softwar
e
f

Testing in
S
g
and Qualit
y
uch Testing
esting? (K2)
sting Princi
p
ntal Test Pr
o
anning and
C
n
alysis and
D
m
plementati
o
ting Exit Cri
t
l
osure Activi
t
h
ology of Te
E
thics
g
hout the So

f
Developme
n
e
l (Sequenti
a
e
-increment
a
g
within a Lif
e
e
ls (K2)
o
nent Testin
g
a
tion Testing
m
Testing (K
2
ance Testin
g
e
s (K2)
g
of Functio
n
g

of Non-fun
c
g
of Softwar
e
g
Related to
n
ce Testing
(
u
es (K2)
c
hniques an
d
rocess (K2) .
e
s of a For
m
a
nd Respon
s
o
f Reviews
(
s
s Factors f
o
a
lysis by To

o
e
chniques (
K
Developme
n
e
s of Test D
e


.

.

.
o
n Level in
S
Level of Kn
o

.

.

.
d
.
K

2)
.
sary (K2)
.
C
ontext (K1
)
e
Defects (K
2
S
oftware De
v
y
(K2)
.
is Enough?

.
p
les (K2)
.
o
cess (K1)
.
C
ontrol (K1)
D
esign (K1)
.

o
n and Exec
u
t
eria and Re
p
t
ies (K1)
.
sting (K2)
.

.
f
tware Life
C
n
t Models (K
2
a
l Developm
a
l Developm
e
Cycle Mod

.
g
(K2)
.

(K2)
.
2
)
.
g
(K2)
.

.
n
(Functional
c
tional Soft
w
e
Structure/
A
Changes: R
e
(
K2)
.

.
d
the Test P
r

.

m
al Review (
K
s
ibilities (K1
)
(
K2)
.
o
r Reviews (
K
o
ls (K2)
.
K
4)
.
n
t Process (
K
e
sign Techni
q
Page 4 of
7
.

.

.

S
oftware Tes
o
wledge
.

.

.

.

.

.

)

2
)
v
elopment,
M
.

(K2)
.

.

.


.

u
tion (K1)
p
orting (K1) .
.

.

.

C
ycle (K2)
2
)
ent Model) (
ent Models
(
el (K2)
.

.

.

.

.

.

Testing) (K
2
w
are Charact
e
A
rchitecture (
e
-testing an
d
.

.

r
ocess (K2)
.

K
1)
)

.

K
2)
.

.

K
3)
q
ues (K2)
7
8

.

.

.
ting
.

.

.

.

.

.

.

.

.

.
M
aintenance

.

.

.

.

.

.

.

.

.

.

.

.

.

.
K2)
.
(
K2)
.

.

.

.

.

.

.

.
2
)

.
e
ristics (No
n
Structural T
e
d
Regressio
n

.

.

.

.

.

.

.

.

.

.

.

.
Q


.

.

.

.

.

.

.

.

.

.

.

.

.

and Operati
.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

n
-functional
T
e
sting) (K2) .
n
Testing (K
2
.

.

.

.

.

.

.

.

.

.

.

.

Internatio
Software T
e
Q
ualification
s
31-Ma

r













ons (K2)

T
esting) (K2)

2
)












nal
e
sting
s

Board
r
-2011
7
8
8
8
8
8
8
9
9
10
11
11
11
11
11
12
13
14
15
15
15
16
16
16
18
20
21

22
22
22
22
24
24
25
26
26
28
28
28
29
29
30
31
32
33
33
33
34
35
36
37
38
39
Certi
f
Found
a

Version
2
© Internation
a

4.3
4.
3
4.
3
4.
3
4.
3
4.
3
4.4
4.
4
4.
4
4.
4
4.5
4.6
5. Te
s
5.1

5.1
5.1
5.2

5.
2
5.
2
5.
2
5.
2
5.
2
5.
2
5.3
5.
3
5.
3
5.
3
5.4
5.5
5.
5
5.
5
5.6

6. To
o
6.1
6.1
6.1
6.1
6.1
6.1
6.1
6.1
6.1
6.2

6.
2
6.
2
6.3
7. Re
Stan
d
Book
s
8.
A
p
Histo
r
Obje
c

Obje
c
Nove
m
Entry
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
Specifica
t
3
.1 Equiva
3
.2 Bound
a
3
.3 Decisi
o
3
.4 State
T
3

.5 Use C
a
Structure
-
4
.1 State
m
4
.2 Decisi
o
4
.3 Other
S
Experien
c
Choosing
s
t Managem
Test Org
a
.1 Test O
.2 Tasks
o
Test Plan
2
.1 Test Pl
2
.2 Test Pl
2
.3 Entry

C
2
.4 Exit Cr
2
.5 Test E
s
2
.6 Test S
t
Test Pro
g
3
.1 Test P
r
3
.2 Test R
e
3
.3 Test C
o
Configur
a
Risk and
T
5
.1 Projec
t
5
.2 Produ
c

Incident
M
o
l Support f
o
Types of
T
.1 Tool S
u
.2 Test T
o
.3 Tool S
u
.4 Tool S
u
.5 Tool S
u
.6 Tool S
u
.7 Tool S
u
.8 Tool S
u
Effective
U
2
.1 Potenti
2
.2 Specia
Introduci

n
ferences
.
d
ards
.
s

.
pendix A –
S
r
y of this Do
c
c
tives of the
F
c
tives of the
I
m
ber 2001) .
.
Requireme
n
e
r
y
llabus

Q
ualifications Board
t
ion-based o
r
lence Partiti
o
a
ry Value A
n
o
n Table Te
s
T
ransition Te
a
se Testing
(
-
based or W
h
m
ent Testing
a
o
n Testing a
n
S
tructure-ba
s

c
e-based Te
c
Test Techn
i
ent (K3)
a
nization (K
2
rganization
a
o
f the Test
L
ning and Es
t
anning (K2)
anning Acti
v
C
riteria (K2) .
iteria (K2)
s
timation (K
2
t
rategy, Tes
t
g
ress Monito

r
r
ogress Mon
e
porting (K2
o
ntrol (K2)
a
tion Manag
e
T
esting (K2)
t
Risks (K2) .
c
t Risks (K2)
M
anagement
o
r Testing (K
2
T
est Tools (
K
u
pport for T
e
o
ol Classific
a

u
pport for M
a
u
pport for St
a
u
pport for T
e
u
pport for T
e
u
pport for P
e
u
pport for S
p
U
se of Tool
s
al Benefits
a
l Considerat
n
g a Tool int
o
.

.

.

S
yllabus Bac
c
umen
t

F
oundation
C
I
nternational
.

n
ts for this Q
u

r
Black-box
T
o
ning (K3)
.
n
alysis (K3) .
.
s

ting (K3)
.
sting (K3)
.
(
K2)
.
h
ite-box Tec
a
nd Covera
g
n
d Coverag
e
s
ed Techniq
u
c
hniques (K
2
i
ques (K2)
.

.
2
)
.
a

nd Indepen
d
L
eader and
T
t
imation (K3
)

.
v
ities (K3)
.

.

.
2
)
.
t

A
pproach (
K
r
ing and Co
n
itoring (K1) .
.

)
.

.
e
ment (K2)
.

.

.

.
(K3)
.
2
)
.
K
2)
.
e
sting (K2)
.
a
tion (K2)
.
a
nagement
o

a
tic Testing
e
st Specifica
t
e
st Executio
n
e
rformance
a
p
ecific Testi
n
s
: Potential
B
a
nd Risks of
ions for So
m
o
an Organi
z

.

.

.

kground
.

.
C
ertificate Q
Qualificatio
n

.
u
alification
.
Page 5 of
7
T
echniques
(
.

.

.

.

.

hniques (K
4

g
e (K4)
e
(K4)
u
es (K1)
2
)
.

.

.

d
ence (K2)
T
ester (K1)
)

.

.

.

.

.

K
2)
n
trol (K2)
.

.

.

.

.

.

.

.

.

.

.

.

o
f Testing a

n
(K1)
t
ion (K1)
n
and Loggi
n
a
nd Monitori
n
n
g Needs (K
1
B
enefits and
Tool Suppo
r
m
e Types of
T
z
ation (K1)
.

.

.

.

.

ualification
n
(adapted f
r
.

.

7
8
(
K3)
.

.

.

.

.

.
4
)
.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.
n
d Tests (K1
)

.

.
n
g (K1)
.
n
g (K1)
.
1
)
.
Risks (K2) .
.
r
t for Testing
T
ools (K1)
.

.

.

.

.

.

.

.
r
om ISTQB
m

.

.
Q


.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

)

.

.

.

.

.

.

(for all tool
s
.

.

.

.

.

.

.

.

m
eeting at S
o

.

.

Internatio
Software T
e
Q
ualification
s
31-Ma
r

s
) (K2)

o
llentuna,


nal
e
sting
s
Board
r
-2011
40
40
40
40
41
41
42
42
42
42
43
44
45
47

47
47
49
49
49
49
49
50
50
51
51
51
51
52
53
53
53
55
57
58
58
58
59
59
59
60
60
60
62
62

62
64
65
65
65
67
67
67
67
67
Certi
f
Found
a


Version
2
© Internation
a

Back
g
9.
A
p
Level
Level
Level
Level

10.

A
Foun
d
10
.
10
.
10
.
10
.
11.
A
12.
A
Rele
a
Rele
a
13.

f
ied Test
e
a
tion Level S
y
2

011
a
l Software Testing
Q
g
round and
H
pendix B –
L
1: Rememb
2: Understa
3: Apply (K
3
4: Analyze
(
A
ppendix C
–
d
ation Sylla
b
.
1.1 Gener
a
.
1.2 Curren
.
1.3 Learni
n
.

1.4 Overal
l
A
ppendix D
–
A
ppendix E
–
a
se 2010
.
a
se 2011
.
Index
.
e
r
y
llabus

Q
ualifications Board
H
istory of th
e
L
earning Obj
e
er (K1)

nd (K2)
3
)
(
K4)
–
Rules Ap
p
b
us
a
l Rules
t Content
n
g Objective
s
l
Structure
–
Notice to
T
–
Release N
.

.

.

e
Foundatio
n
e
ctives/Cog
n

.

.

.

.
p
lied to the I
S

.

.

.
s

.

.
T
raining Pro

v
otes
.

.

.

.
Page 6 of
7
n
Certificate i
n
itive Level
o
.

.

.

.

S
TQB
.

.

.

.

.

v
iders
.

.

.

.

7
8
n Software
T
o
f Knowledg
e

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.
Q


T
esting
e

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

Internatio
Software T
e
Q
ualification
s
31-Ma
r

















nal
e
sting
s
Board

r
-2011
68
69
69
69
69
69
71
71
71
71
71
71
73
74
74
74
76
Certi
f
Found
a


Version
2
© Internation
a

Ackn
o
Internati
o
Thomas
A
rmin B
e
Schaefe
the curr
e
Internati
o
Thomas
review t
e
Tuula P
ä
Veenen
d
Internati
o
Thomas
team th
a
Petterss
Internati
o
Thomas
Geoff T

h
suggesti
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
o
wledge
o
nal Softwa
r
Müller (chai
e
er, Rex Bla
r, Stephanie
e
nt version
o
o
nal Softwa
r
Müller (chai
e

am (Rex Bl
a
ä
äkkönen,
M
d
aal) and all
o
nal Softwa
r
Müller (chai
a
nks the revi
e
on, and Wo
n
o
nal Softwa
r
Müller (chai
h
ompson an
d
ons.
e
r
y
llabus

Q

ualifications Board
ments
r
e Testing Q
u
r), Debra Fri
ck, Julie Ga
r
Ulrich, Erik
o
f the syllabu
r
e Testing Q
u
r), Rahul Ve
a
ck, Mette
B
M
eile Posthu
m
National Bo
a
r
e Testing Q
u
r), Dorothy
G
e
w team (H

a
n
il Kwon) an
d
r
e Testing Q
u
r), Rex Blac
k
d
Erik van V
e

u
alifications
edenberg.
T
r
diner, Judy
van Veenen
s.
u
alifications
rma, Martin
K
B
ruhn-Peder
s
m
a, Hans S

c
a
rds for thei
r
u
alifications
G
raham, De
b
a
ns Schaefe
r
d
all the Nati
u
alifications
k
, Sigrid Eld
h
e
enendaal a
n
Page 7 of
7
Board Work
T
he core tea
m
McKay, Tuu
l

daal) and all
Board Work
K
lonk and A
r
s
on, Debra
F
c
haefer, Ste
p
r
suggestion
s
Board Work
b
ra Friedenb
r
, Stephanie
onal Boards
Board Work
h
, Dorothy
G
n
d the revie
w
7
8
ing Group F

o
m
thanks the
l
a Pääkkön
e
National B
o
ing Group F
o
r
min Beer.
T
F
riedenberg,
p
hanie Ulrich
s
.
ing Group F
o
erg, and Eri
k
Ulrich, Meil
e
for their su
g
ing Group F
o
G

raham, Kla
u
w
team and
a
Q


o
undation L
e
review tea
m
e
n, Eric Riou
o
ards for the
o
undation L
e
T
he core tea
m
Klaus Olse
n
, Pete Willia
m
o
undation L
e

k
van Veene
e
Posthuma,
g
gestions.
o
undation L
e
u
s Olsen, M
a
a
ll National
B
Internatio
Software T
e
Q
ualification
s
31-Ma
r
e
vel (Edition
m
(Dan Almo
g
du Cosquie
r

suggestion
s
e
vel (Edition
m
thanks the
n
, Judy McK
a
m
s, Erik van
e
vel (Edition
ndaal. The
c
Anders
e
vel (Edition
a
aret Pyhäjä
r
B
oards for th
nal
e
sting
s
Board
r
-2011

2011):
g
,
r
Hans
for
2010):

a
y,

2007):
c
ore
2005):
r
vi,
eir
Certi
f
Found
a


Version
2
© Internation
a

Intro

d
Purp
o
This syll
a
Level. T
h
Boards
f
languag
e
for accr
e
Informat
The
C
The Fou
people i
n
accepta
n
for anyo
manage
r
consult
a
testing
q
Learn
i

Learnin
g
o K1:
r
o K2:
u
o K3:
a
o K4:
a
Further
d

A
ll term
s
explicitl
y
The
E
The Fou
examin
a
syllabus
The for
m
Exams
m
examin
a

requisit
e
Accre
d
A
n IST
Q
syllabus
perform
s
is allow
e

Further
g
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
d
uctio
n
o

se of thi
s
a
bus forms
t
h
e Internati
o
f
or them to a
e
. Training
p
e
ditation. Th
ion on the hi
C
ertified
T
ndation Lev
e
n
roles such
n
ce testers
a
ne who wan
t
r
s, software

a
nts. Holders
q
ualification.
i
ng Obje
c
g
objectives
a
r
emember
u
nderstand
a
pply
a
nalyze
d
etails and
e
s
listed unde
y
mentioned
E
xaminati
o
ndation Lev
e

a
tion questio
n
. All section
s
m
at of the ex
a
m
ay be take
n
a
tion center
o
e
for the exa
m
d
itation
Q
B National
B
. Training pr
o
s
the accredi
e
d to have a
n
g

uidance for
e
r
y
llabus

Q
ualifications Board
n
to thi
s
s
Docum
e
t
he basis for
o
nal Softwar
e
ccredit the t
r
p
roviders will
e syllabus
w
story and b
a
T
ester Fo
e

l qualificati
o
as testers, t
e
a
nd software
t
s a basic u
n
developme
n
of the Foun
c
tives/C
o
a
re indicate
d
e
xamples of
l
r “Terms” ju
s
in the learni
n
o
n
e
l Certificate
n

s may requ
s
of the sylla
b
a
mination is
n
as part of
a
o
r in a public
m
.
B
oard may a
o
viders sho
u
tation. An a
c
n
ISTQB ex
a
training pro
v

s
Syllab
e
nt

the Internati
e
Testing Qu
r
aining provi
d
determine
a
w
ill help cand
a
ckground o
f
undation
o
n is aimed
a
e
st analysts
,
developers.
n
derstanding
n
t managers,
dation Certi
f
o
gnitive L
d

for each se
l
earning obj
e
s
t below cha
p
n
g objective
s
examinatio
n
ire the use
o
b
us are exa
m
multiple ch
o
a
n accredite
d
exam). Co
m
ccredit traini
u
ld obtain ac
c
c
credited co

u
a
mination as
v
iders is giv
e
Page 8 of
7
us
onal Softwa
r
alifications
B
d
ers and to
d
a
ppropriate t
e
idates in the
f
the syllabu
s
Level in
a
t anyone in
v
,
test engine
e

This Found
a
of software
business a
n
f
icate will be
evel of
K
ction in this
s
e
ctives are g
p
ter headin
g
s
.
n
will be bas
e
o
f material b
a
m
inable.
o
ice.
d
training co

u
m
pletion of
a
ng provider
s
c
reditation g
u
rse is reco
g
part of the c
e
n in Appen
d
7
8
r
e Testing Q
B
oard (ISTQ
B
d
erive exami
e
aching met
h
ir preparatio
s
can be fou

n
Softwar
e
v
olved in sof
t
e
rs, test con
s
a
tion Level
q
testing, suc
h
n
alysts, IT di
r
able to go o
n
K
nowledg
e
s
yllabus an
d
iven in App
e
g
s shall be r
e

e
d on this s
y
a
sed on mor
e
u
rse or take
n
a
n accredite
d
s
whose cou
r
uidelines fro
g
nized as co
n
ourse.
d
ix D.
Q


ualification
a
B
) provides i
nation ques

t
h
ods and pr
o
n for the ex
a
n
d in Appen
d
e
Testin
g

t
ware testin
g
s
ultants, tes
t
q
ualification
i
h
as project
m
r
ectors and
m
n
to a highe

r
e

d
classified a
s
e
ndix B.
e
membered
(
y
llabus. Ans
w
e
than one s
n
independe
n
d
training co
u
r
se material
f
m the board
n
forming to t
Internatio
Software T

e
Q
ualification
s
31-Ma
r
a
t the Found
a
t to the Nati
o
t
ions in their
o
duce cours
e
a
mination.
d
ix A.
g
. This inclu
d
t
managers,
i
s also appr
o
m
anagers, q

m
anagemen
r
-level softw
a
s follows:
(
K1), even if
w
ers to
ection of thi
s
n
tly (e.g., at
a
u
rse is not a
f
ollows this
or body tha
t
his syllabus,
nal
e
sting
s
Board
r
-2011
a

tion
o
nal
local
e
ware
d
es
user
o
priate
uality
t

a
re
not
s

a
n
pre-
t

and
Certi
f
Found
a

Version
2
© Internation
a

Level
The lev
e
order to
o Gen
o
A
lis
req
u
o Lea
r
min
d
o
A
lis
o
A
d
e
stan

The syll

a
the level
How t
h
There a
r
learning
exampl
e

2. Te
s

This he
a
shown)
a
chapter.
objectiv
e
within th

f
ied Test
e
a
tion Level S
y
2
011

a
l Software Testing
Q
of Detai
l

e
l of detail in
achieve this
eral instructi
t of informat
i
u
ired
r
ning objecti
v
d
set to be a
c
t of terms th
a
e
scription of
t
dards
a
bus conten
t
of detail to

b
h
is Sylla
b
r
e six major
c
objectives t
h
e
:
s
ting Th
r
a
ding shows
a
nd K2 (but
n
Within each
e
s and the a
m
e time for th
e
e
r
y
llabus

Q
ualifications Board
this syllabu
s
goal, the sy
onal objecti
v
i
on to teach,
v
es for each
c
hieved
a
t students
m
t
he key con
c
t
is not a de
s
b
e covered i
n
b
us is O
r
c
hapters. Th

h
at is cover
e
r
oughou
t
that Chapte
r
n
ot K3), and
chapter the
m
ount of tim
e
e
section.

s
allows inte
r
llabus consi
s
v
es describi
n
including a
d
knowledge
a
m

ust be abl
e
c
epts to teac
s
cription of t
h
n
Foundatio
n
r
ganized
e top-level
h
e
d within the
t
the So
f
r
2 has learn
it is intende
d
re are a nu
m
e
required.
S
Page 9 of
7

r
nationally c
o
s
ts of:
n
g the intenti
o
d
escription,
a
a
rea, descri
b
e
to recall an
d
h, including
s
h
e entire kn
o
n
Level train
i
h
eading for e
chapter and
f
tware Li

ing objectiv
e
d
to take 11
5
m
ber of secti
o
S
ubsections
7
8
o
nsistent tea
o
n of the Fo
u
a
nd referen
c
b
ing the cog
n
d
understan
d
s
ources suc
h
o

wledge are
a
i
ng courses.
ach chapter
specifies th
e
fe Cycle
e
s of K1 (as
s
5
minutes to
o
ns. Each s
e
that do not
h
Q


ching and e
x
u
ndation Le
v
c
es to additi
o
n

itive learnin
d

h
as accept
e
a
of software
shows the
h
e
time for th
e
(K2)
s
umed when
teach the m
e
ction also h
a
h
ave a time
g
Internatio
Software T
e
Q
ualification
s
31-Ma

r
x
amination.
I
v
el
o
nal sources
g outcome
a
e
d literature
o
testing; it re
f
h
ighest level
e
chapter. F
o
115 mi
n
a higher lev
aterial in th
e
a
s the learni
g
iven are inc
nal

e
sting
s
Board
r
-2011
n
if
a
nd
o
r
f
lects
of
o
r
n
utes
el is
e

n
g
luded
Certi
f
Found
a

Version
2
© Internation
a

1.

Learn
i
The obj
e

1.1 W
h
LO-1.1.
1
LO-1.1.
2
LO-1.1.
3
LO-1.1.
4
LO-1.1.
5

1.2 W
h
LO-1.2.
1

LO-1.2.
2
LO-1.2.
3

1.3 Se
v
LO-1.3.
1

1.4 Fu
n
LO-1.4.
1

1.5 Th
e
LO-1.5.
1
LO-1.5.
2
f
ied Test
e
a
tion Level S
y
2
011
a

l Software Testing
Q
Funda
m
i
ng Obje
c
e
ctives identi
h
y is Testi
1
Describ
e
person,
t
2
Distingu
3
Give re
a
4
Describ
e
contribu
t
5
Explain
a
mistake

h
at is Test
1
Recall t
h
2
Provide
cycle (K
2
3
Differen
t
v
en Testi
n
1
Explain
t
n
dament
a
1
Recall t
h
(K1)
e
Psychol
1
Recall t
h

2
Contras
t
e
r
y
llabus

Q
ualifications Board
m
entals
c
tives fo
r

fy what you
ng Neces
s
e
, with exam
t
o the envir
o
ish between
a
sons why te
e
why testin
g

t
es to highe
r
a
nd compar
e
and bug, us
i
ing? (K2)
h
e common
o
examples fo
2
)
t
iate testing
f
n
g Princi
p
t
he seven p
r
a
l Test Pr
o
h
e five funda
ogy of Te

s
h
e psycholo
g
t
the mindse
t

of Tes
t
r
Funda
m
will be able
t
s
ary? (K2
ples, the wa
y
o
nment or to
the root ca
u
sting is nec
e
g
is part of q
u
r
quality (K2)

e
the terms
e
i
ng example
s
o
bjectives o
f

r the objecti
v
f
rom debug
g
p
les (K2)
r
inciples in t
e
o
cess (K1
)
mental test
a
s
ting (K2
)
g
ical factors

t
t
of a tester
a
Page 10 of
t
ing (K
2
m
entals o
f
t
o do followi
n
)
y
in which a
a company
(
u
se of a defe
c
e
ssary by gi
v
u
ality assura

e
rror, defect,

s
(K2)
f
testing (K1)
v
es of testin
g
g
ing (K2)
e
sting (K2)
)

a
ctivities an
d
)

t
hat influenc
e
a
nd of a dev
e
78
2
)
f
Testing
n

g the comp
l
defect in so
f
(
K2)
c
t and its eff
e
v
ing exampl
e
nce and giv
e
fault, failur
e

g
in different
d
respective
t
e
the succe
s
e
loper (K2)
Q

1
5
l
etion of eac
h
f
tware can c
a
e
cts (K2)
e
s (K2)
e
examples
o
e
, and the co
r
phases of t
h
t
asks from p
s
s of testing
(
Internatio
Software T
e
Q
ualification

s
31-M
a
5
5 min
u
h
module.
a
use harm t
o
o
f how testin
r
responding
h
e software l
lanning to cl
(
K1)
nal
e
sting
s
Board
a
r-2011
u
tes
o

a
g
terms
ife
osure
Certi
f
Found
a


Version
2
© Internation
a

1.1

Terms
Bug, de
f
1.1.1
Softwar
e
product
s
expecte
d
money,
t

1.1.2
A
huma
n
code, or
(or do s
o
result in

Defects
code, c
o

Failures
electron
i
changin
g
1.1.3
Opera
t
Rigorou
s
during o
correcte
d

Softwar
e
standar

d
1.1.4
With the
for both
f
usability
see Ch
a
Softwar
e

Testing
c
designe
d
defects,

Lesson
s
found in
reoccurr
quality a

Testing
s
standar
d
f
ied Test
e

a
tion Level S
y
2
011
a
l Software Testing
Q
Why is
f
ect, error, f
a
Softwar
e
e
systems a
r
s
(e.g., cars)
.
d
. Software
t
t
ime or busi
n
Causes
o
n
being can

m
in a docum
e
o
mething it s
failures, but
occur becau
o
mplexity of i
can be cau
s
i
c fields, and
g
the hardw
a
Role of
T
t
ions (K2)
s
testing of
s
peration an
d
d
before the
e
testing ma
y

d
s.
Testing
a
help of testi
f
unctional a
n
, efficiency,
m
a
pter 2; for m
e
Product Q
u
c
an give co
n
d
test that p
a
the quality
o
s
should be l
e
other proje
c
ing and, as
a

ssurance.
s
hould be in
t
d
s, training a
e
r
y
llabus

Q
ualifications Board
Testin
g
a
ilure, fault,
m
e
System
s
r
e an integra
l
.
Most peopl
e
t
hat does no
t

n
ess reputati
o
f Softwa
r
m
ake an err
o
e
nt. If a defe
c
houldn’t), c
a
not all defe
c
se human b
e
nfrastructur
e
s
ed by envir
o
pollution ca
a
re condition
T
esting in
s
ystems and
d

contribute t
o
system is r
e
y
also be re
q
a
nd Quali
t
ng, it is pos
s
n
d non-funct
i
m
aintainabili
ore informa
t
u
ality’ (ISO 9
n
fidence in t
h
a
sses reduc
e
o
f the softwa
r

e
arned from
c
ts, process
e
a
conseque
n
t
egrated as
o
nd defect a
n

g
Neces
s
m
istake, qua
l
s
Context
(
l
part of life,
f
e
have had
a
t

work corre
c
on, and cou
l
r
e Defect
s
o
r (mistake),
c
t in code is
a
using a failu
c
ts do so.
e
ings are fal
e
, changing
t
o
nmental co
n
n cause faul
s.
Software
documentat
i
o
the quality

e
leased for o
q
uired to me
e
t
y (K2)
s
ible to mea
s
i
onal softwa
r
ty and porta
b
t
ion on softw
126).
h
e quality of
t
e
s the overal
r
e system in
c
previous pr
o
e
s can be im

p
n
ce, improve
o
ne of the q
u
n
alysis).
Page 11 of
s
ary (K
2
l
ity, risk
(
K1)
f
rom busine
s
a
n experien
c
c
tly can lead
l
d even cau
s
s
(K2)
which prod

u
executed, t
h
re. Defects i
lible and be
c
t
echnologies
n
ditions as
w
ts in firmwa
r
Develop
m
i
on can help
of the softw
perational u
s
e
t contractu
a
s
ure the qua
l
r
e requirem
e
b

ility). For m
are charact
e
t
he software
l level of ris
k
c
reases wh
e
o
jects. By un
p
roved, whi
c
the quality
o
u
ality assura
78
2
)
s
s applicatio
c
e with softw
a
to many pr
o
s

e injury or d
e
u
ces a defec
h
e system m
a
n software,
s
c
ause there i
, and/or ma
n
w
ell. For exa
r
e or influen
c
m
ent, Mai
n
to reduce t
h
are system,
s
e.
a
l or legal re
q
l

ity of softwa
e
nts and cha
r
ore informat
e
ristics see ‘
S
if it finds fe
w
k
in a syste
m
e
n those def
e
derstanding
c
h in turn sh
o
o
f future sys
t
nce activitie
s
Q


ns (e.g., ba
n

a
re that did
n
o
blems, inclu
e
ath.
t (fault, bug)
a
y fail to do
w
s
ystems or
d
s time pres
s
n
y system in
t
mple, radiati
c
e the execu
t
n
tenance
a
h
e risk of pro
if the defect
s

q
uirements,
o
re in terms
o
r
acteristics (
e
ion on non-f
u
S
oftware En
g
w
or no defe
c
m
. When testi
e
cts are fixe
d
the root cau
o
uld prevent
t
ems. This is
s
(i.e., along
s
Internatio

Software T
e
Q
ualification
s
31-M
a
20 minu
t
n
king) to con
s
n
ot work as
ding loss of
in the progr
a
w
hat it shou
l
d
ocuments
m
s
ure, comple
x
t
eractions.
i
on, magneti

s
t
ion of softw
a
a
nd
blems occur
s
found are
o
r industry-s
o
f defects fo
u
e
.g., reliabili
t
u
nctional te
s
g
ineering –
c
ts. A prope
r
ng does fin
d
d
.
ses of defe

c
those defec
t
an aspect
o
s
ide develo
p
nal
e
sting
s
Board
a
r-2011
t
es
s
umer
a
m
l
d do
m
ay
x

s
m,
a

re by
ring
pecific
u
nd,
t
y,
s
ting
r
ly
d

c
ts
t
s from
o
f
p
ment
Certi
f
Found
a


Version
2
© Internation

a

1.1.5
Decidin
g
safety,
a
further i
n

Testing
s
release
o
custom
e
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
How Mu
c
g

how much
t
a
nd busines
s
n
Chapter 5.
s
hould provi
d
o
f the softw
a
e
rs.
e
r
y
llabus

Q
ualifications Board
c
h Testin
g
t
esting is en
o
s
risks, and

p
d
e sufficient
a
re or syste
m

g
is Enou
g
o
ugh should
p
roject const
r
information
t
m
being test
e
Page 12 of
g
h? (K2)
take accou
n
r
aints such
a
t
o stakehold

e
d, for the n
e
78
n
t of the lev
e
a
s time and
b
ers to make
xt developm
Q


e
l of risk, incl
u
b
udget. Ris
k
informed de
ent step or
h
Internatio
Software T
e
Q
ualification
s

31-M
a
u
ding techni
c
k
is discusse
d
cisions abo
u
h
andover to
nal
e
sting
s
Board
a
r-2011
c
al,
d

u
t the
Certi
f
Found
a

Version
2
© Internation
a

1.2

Terms

Debuggi

Backg
r
A
comm
This is
p

Test act
i
choosin
g
criteria,
r
activitie
s
(includin

Both dy

n
and will
develop
m

Testing
c
o Find
o Gai
n
o Pro
v
o Pre
v

The tho
u
test basi
docume
n
defects
a

Differen
t
testing (
e
many fa
i
accepta

n
gain co
n
be to as
s
stakehol
testing t
h
operatio
availabil

Debuggi
Debuggi
Subseq
u
respons
i

The pro
c
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing

Q
What i
s

ng, require
m
r
ound

on percepti
o
p
art of testin
g
i
vities exist
b
g
test conditi
r
eporting on
s
after a test
g source co
d
n
amic testin
g
provide info
r

m
ent and te
s
c
an have th
e
ing defects
n
ing confide
n
v
iding inform
v
enting defe
c
u
ght proces
s
s via test de
n
ts (e.g., re
q
a
ppearing in
t
viewpoints
e
.g., compo
n
i

lures as po
s
n
ce testing,
t
n
fidence that
s
ess the qu
a
ders of the
r
h
at no new
d
nal testing, t
ity.
ng and testi
n
ng is the de
v
u
ent re-testi
n
i
bility for the
s
c
ess of testi
n

e
r
y
llabus

Q
ualifications Board
s
Testin
m
ent, review,
o
n of testing
i
g
, but not all
o
b
efore and a
f
ons, designi
the testing
p
phase has
b
d
e) and con
d
g
and static t

e
r
mation that
c
s
ting proces
s
e
following o
b
n
ce about th
e
ation for de
c
c
ts
s
and activiti
e
sign) can h
e
q
uirements)
a
the code.
in testing ta
k
n
ent, integra

t
s
sible so tha
t
t
he main obj
e
it has met t
h
a
lity of the s
o
r
isk of releas
d
efects have
he main obj
e
n
g are differ
e
v
elopment a
c
n
g by a teste
s
e activities
i
n

g and the t
e

g? (K2)
test case, t
e
i
s that it onl
y
o
f the testin
g
f
ter test exe
c
ng and exe
c
p
rocess and
b
een comple
t
d
ucting stati
c
e
sting can b
c
an be used
s

es.
b
jectives:
e
level of qu
a
c
ision-makin
g
e
s involved i
n
e
lp to preven
t
a
nd the iden
t
k
e different
o
t
ion and sys
t
t
defects in t
h
e
ctive may
b

h
e requirem
e
o
ftware (with
ing the syst
e
been introd
u
e
ctive may b
e
nt. Dynami
c
c
tivity that fi
n
r ensures th
a
i
s usually te
s
e
sting activiti
e
Page 13 of
e
sting, test
o
y

consists of
g
activities.
c
ution. The
s
c
uting test c
a
system und
e
t
ed. Testing
c
analysis.
e used as a
to improve
b
a
lity
g

n
designing
t
t
defects fro
m
t
ification an

d
o
bjectives int
o
t
em testing),
h
e software
a
b
e to confirm
e
nts. In som
e
no intention
e
m at a give
n
u
ced during
d
e to assess
s
c
testing can
n
ds, analyze
a
t the fix do
e

s
ters test an
d
e
s are expla
78
o
bjective
running test
s
s
e activities i
n
ses, checki
n
e
r test, and f
i
also include
s
means for a
c
b
oth the sys
t
t
ests early in
m
being intr
o

d
resolution
o
o
account.
F
the main o
b
a
re identifie
d
that the sys
e
cases the
m
of fixing def
e
n
time. Main
t
d
evelopmen
s
ystem char
a
show failur
e
s and remo
v
e

s indeed re
s
d
developer
s
ined in Secti
Q


s
, i.e., exec
u
n
clude plan
n
n
g results, e
v
i
nalizing or
c
s
reviewing
d
c
hieving si
m
t
em being te
s

the life cycl
e
o
duced into
c
o
f issues als
o
F
or example,
b
jective may
d
and can b
e
tem works a
m
ain objecti
v
e
cts), to giv
e
t
enance testi
t of the cha
n
a
cteristics s
u
e

s that are c
a
v
es the caus
e
s
olve the fail
s
debug.
on 1.4.
Internatio
Software T
e
Q
ualification
s
31-M
a
30 minu
t
u
ting the soft
w
n
ing and con
t
v
aluating exi
t
c

ompleting cl
d
ocuments
m
ilar objectiv
e
s
ted and th
e
e
(verifying t
c
ode. Revie
w
o
help to pre
v
in develop
m
be to cause
e
fixed. In
s expected,
v
e of testing
e
informatio
n
i
ng often inc

l
n
ges. During
u
ch as relia
b
a
used by de
f
e
of the failu
r
ure. The
nal
e
sting
s
Board
a
r-2011
t
es
w
are.
t
rol,
t

osure
e

s,
e

he
w
s of
v
ent
m
ent
as
to
may
n
to
l
udes
b
ility or
f
ects.
r
e.
Certi
f
Found
a


Version

2
© Internation
a

1.3

Terms
Exhaust

Princi
p
A
numb
e
guidelin
e

Principl
Testing
c
reduces
found, it

Principl
Testing
e
cases. I
n
efforts.

Principl
To find
d
develop
m

Principl
Testing
e
module
s
release
t

Principl
If the sa
m
longer fi
n
reviewe
d
the soft
w

Principl
Testing
i
different
l

Principl
Finding
a
needs a
n

f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
Seven
ive testing
p
les

e
r of testing
p
e
s common
f
e 1 – Testin
c

an show th
a
the probabil
is not a pro
o
e 2 – Exha
u
e
verything (
a
n
stead of ex
h
e 3 – Early
t
d
efects early
m
ent life cyc
e 4 – Defec
t
e
ffort shall b
e
s
. A small nu
t
esting, or is
e 5 – Pesti
c

m
e tests are
n
d any new
d
d
and revise
d
w
are or syst
e
e 6 – Testin
i
s done diffe
r
l
y from an e
-
e 7 – Abse
n
a
nd fixing d
e
n
d expectati
o
e
r
y
llabus

Q
ualifications Board
Testing
p
rinciples h
a
f
or all testin
g
g shows pr
e
a
t defects ar
ity of undisc
o
o
f of correct
n
u
stive testin
a
ll combinati
o
h
austive tes
t
t
esting
, testing acti

v
le, and shall
t
clustering
e
focused p
r
mber of mo
d
responsible
c
ide parado
x
repeated o
v
d
efects. To
o
d
, and new
a
e
m to find po
g is contex
t
r
ently in diff
e
-
commerce

s
n
ce-of-error
s
e
fects does
n
o
ns.

Princip
a
ve been su
g
g
.
e
sence of
d
e present, b
u
o
vered defe
c
n
ess.
g is impos
s
o
ns of input

s
t
ing, risk an
a
v
ities shall b
be focused
r
oportionally
d
ules usuall
y
for most of
t
x

v
er and over
o
vercome th
i
a
nd different
tentially mo
r
t
dependen
t
e
rent contex

t
s
ite.
s
fallacy
n
ot help if th
e
Page 14 of
les (K2
)
g
gested ove
r
d
efects
u
t cannot pr
o
c
ts remainin
g
s
ible
s
and preco
n
a
lysis and pri
e started as

on defined
o
to the expe
c
y
contains m
o
t
he operatio
n
again, even
t
i
s “pesticide
tests need t
o
r
e defects.
t

t
s. For exam
e
system bui
78
)

r
the past 40
o

ve that ther
e
g
in the soft
w
n
ditions) is n
o
orities shoul
d
early as po
s
o
bjectives.
c
ted and late
o
st of the de
f
n
al failures.
t
ually the sa
m
parado
x
”, te
o
be written
t

ple, safet
y
-c
lt is unusabl
e
Q


years and o
e
are no def
e
w
are but, ev
e
o
t feasible e
x
d
be used t
o
s
sible in the
s
r observed
d
f
ects discov
e
m

e set of te
s
st cases ne
e
t
o exercise
d
ritical softw
a
e
and does
n
Internatio
Software T
e
Q
ualification
s
31-M
a
35 minu
t
ffer general
e
cts. Testin
g
e
n if no defe
c
x

cept for triv
i
o
focus testin
s
oftware or
s
d
efect densit
y
e
red during
p
s
t cases will
e
d to be reg
u
d
ifferent part
s
a
re is tested
n
ot fulfill the
nal
e
sting
s
Board

a
r-2011
t
es
g

c
ts are
i
al
g
s
ystem
y
of
p
re-
no
u
larly
s
of
u
sers’
Certi
f
Found
a

Version
2
© Internation
a

1.4

Terms
Confirm
a
test cov
e
summar
y

Backg
r
The mo
s
also incl
u
and eva
l

The fun
d
o Tes
t
o Tes
t

o Tes
t
o Eval
o Tes
t

A
lthoug
h
Tailorin
g
1.4.1
Test pla
n
in order

Test co
n
status, i
n
and obj
e
through
o
activitie
s

Test pla
n
1.4.2

Test an
a
tangible

The test
o Rev
i
anal
o Eval
o Iden
beh
a
o Des
i
o Iden
o Des
i
o Cre
a

1

The deg
r
system ch
a
reliability,
o
f
ied Test

e
a
tion Level S
y
2
011
a
l Software Testing
Q
Funda
m
a
tion testing
,
e
rage, test d
a
y
report, tes
t
r
ound
s
t visible par
t
u
de time to
b
l
uating resul

t
d
amental te
s
t
planning a
n
t
analysis an
t
implement
a
uating exit
c
t
closure acti
h
logically s
e
g
these main
Test Pla
n
n
ning is the
a
to meet the
o
n
trol is the o

n
n
cluding dev
e
ctives of th
e
o
ut the proje
c
s
.
n
ning and c
o
Test An
a
a
lysis and d
e
test conditi
o
analysis an
d
i
ewing the t
e
ysis reports,
uating testa
b
tifying and

p
a
vior and str
u
i
gning and p
tifying nece
s
i
gning the te
s
a
ting bi-dire
c

r
ee to which so
f
a
racteristics (e.
g
o
r cost) which
a
e
r
y
llabus

Q

ualifications Board
m
ental
T
,
re-testing,
e
a
ta, test exe
t
ware
t
of testing i
s
b
e spent on
p
t
s.
s
t process c
o
n
d control
d design
a
tion and ex
e
c
riteria and r

e
vities
e
quential, th
e
activities wi
t
n
ning an
d
a
ctivity of d
e
o
bjectives a
n
n
going activi
t
iations from
e
project. In
o
c
t. Test plan
o
ntrol tasks
a
a
lysis and

e
sign is the
a
o
ns and test
c
d
design act
i
e
st basis (su
c
architectur
e
b
ility of the t
e
p
rioritizing te
s
u
cture of th
e
rioritizing hi
g
s
sary test da
s
t environm
e

c
tional trace
a

f
tware complie
s
g
., software co
m
a
re defined to r
e

T
est Pr
o
e
xit criteria, i
cution, test l
s
test execut
i
p
lanning the
o
nsists of the
e
cution
e

porting
e
activities in
t
hin the cont
d
Control
(
e
fining the o
b
n
d mission.
t
y of compar
the plan. It i
n
o
rder to cont
r
ning takes i
n
a
re defined i
n
Design (
K
a
ctivity durin
g

c
ases.
i
vity has the
c
h as requir
e
e
, design, int
e
e
st basis an
d
s
t conditions
e
software
g
h level test
c
ta to suppor
t
e
nt setup an
d
a
bility betwe
e
s
or must compl

y
m
plexity, risk a
s
e
flect the import
a
Page 15 of
o
cess (
K
ncident, reg
r
og, test plan
i
on. But to b
e
tests, desig
following m
a
the process
ext of the sy
(
K1)

b
jectives of t
e
ing actual p
r

n
volves taki
n
r
ol testing, t
h
n
to account t
n
Chapter 5
o
K
1)

g
which gen
e
following m
a
e
ments, soft
w
e
rface speci
f
d
test object
s
based on a
n

c
ases
t
the test co
n
d
identifying
e
n test basis
y
with a set of
s
s
sessment, saf
e
a
nce of the sof
t
78
K
1)
r
ession testi
n
, test proce
d
e
effective a
n
ning test ca

s
a
in activities
may overla
p
stem and th
e
e
sting and t
h
r
ogress agai
n
n
g actions n
e
h
e testing ac
he feedbac
k
o
f this sylla
b
e
ral testing o
a
jor tasks:
w
are integrit
y

f
ications)
s

n
alysis of te
s
n
ditions and
any require
d
and test ca
s
s
takeholde
r
-sel
e
e
ty level, securi
t
t
ware to its sta
k
Q


n
g, test basi
s

d
ure, test pol
n
d efficient,
t
s
es, prepari
n
:
p
or take pla
c
e
project is
u
h
e specificati
o
n
st the plan,
e
cessary to
m
tivities shou
l
k
from monit
o
b
us.

bjectives ar
e
y
level
1
(risk
s
t items, the
test cases
d
infrastruct
u
s
es
e
cted software
a
t
y level, desired
k
eholders.

Internatio
Software T
e
Q
ualification
s
31-M
a

35 minu
t
s
, test condi
t
icy, test suit
e
t
est plans s
h
n
g for execut
c
e concurre
n
u
sually requi
r
on of test a
c
and reporti
n
m
eet the mi
s
l
d be monito
r
o
ring and co

n
e
transforme
d
level), risk
specificatio
n
u
re and tools
a
nd/or software
-
performance,
nal
e
sting
s
Board
a
r-2011
t
es
t
ion,
e
, test
h
ould
i
on

n
tly.
r
ed.
c
tivities
n
g the
s
sion
r
ed
n
trol
d
into
n
,

-
based
Certi
f
Found
a


Version
2
© Internation

a

1.4.3
Test im
p
combini
n
executi
o

Test im
p
o Fin
a
o Dev
e
har
n
o Cre
a
o Veri
f
o Veri
f
o Exe
c
plan
o Log
g
und

e
o Co
m
o Rep
o
a d
e
was
o Rep
e
exe
c
of a
intr
o
def
e
1.4.4
Evaluati
n
objectiv
e

Evaluati
n
o Che
c
o
A
ss

e
o Writ
i
1.4.5
Test clo
s
testwar
e
softwar
e
achieve
d

f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
Test Im
p
p
lementation
n
g the test c

a
o
n, the envir
o
p
lementation
a
lizing, imple
m
e
loping and
n
esses and
w
a
ting test sui
t
f
ying that th
e
f
ying and up
c
uting test p
r
ned sequen
c
g
ing the out
c

e
r test, test t
o
m
paring actu
a
o
rting discre
e
fect in the c
o
executed)
e
ating test a
c
ution of a t
e
corrected te
s
o
duced in un
c
e
cts (regress
i
Evaluati
n
n
g exit criter
e

s. This sho
u
n
g exit criter
c
king test lo
g
e
ssing if mo
r
i
ng a test su
m
Test Clo
s
s
ure activitie
e
, facts and
n
e
system is r
e
d
, or a maint
e
e
r
y
llabus

Q
ualifications Board
p
lementati
and executi
o
a
ses in a pa
r
o
nment is se
t
and executi
o
m
enting and
prioritizing t
e
w
riting auto
m
t
es from the
e
test enviro
n
dating bi-dir
e
r

ocedures ei
c
e
c
ome of test
o
ols and tes
t
a
l results wit
h
pancies as i
n
o
de, in speci
ctivities as
a
e
st that previ
o
s
t and/or ex
e
c
hanged are
i
on testing)
n
g Exit C
r

ia is the acti
v
u
ld be done
f
ia has the fo
g
s against t
h
r
e tests are
n
m
mary repo
r
s
ure Acti
v
s collect dat
a
n
umbers. Te
s
e
leased, a t
e
e
nance rele
a

on and E
x
o
n is the act
r
ticular orde
r
t
up and the
o
n has the f
o
prioritizing
t
e
st procedur
e
m
ated test sc
r
test proced
u
n
ment has b
e
e
ctional trac
e
ther manual

l
execution a
n
t
ware
h
expected
r
n
cidents an
d
fied test dat
a
a
result of ac
t
o
usly failed i
e
cution of te
s
as of the so
f
r
iteria and
v
ity where t
e
f
or each test

llowing maj
o
h
e exit criteri
a
n
eeded or if
t
r
t for stakeh
o
v
ities (K1)
a
from com
p
s
t closure a
c
e
st project is
a
se has bee
n
Page 16 of
x
ecution (
ivity where t
e
r

and includi
n
tests are ru
n
o
llowing maj
o
t
est cases (i
n
e
s, creating
t
r
ipts
u
res for effic
i
e
en set up c
o
e
ability betw
l
y or by usin
g
n
d recording
r
esul

t
s
d
analyzing t
h
a
, in the test
t
ion taken fo
n order to c
o
s
ts in order
t
f
tware or tha
Reportin
g
e
st execution
level (see
S
o
r tasks:
a
specified i
n
t
he exit crite
r

o
lders

p
leted test a
c
c
tivities occu
r
completed (
o
n
completed
78
K1)

e
st procedu
r
n
g any other
n
.
o
r tasks:
n
cluding the
t
est data an
d

ent test exe
c
o
rrectly
e
en the test
g
test execu
t
the identitie
s
h
em in orde
r
document,
o
r each discr
e
o
nfirm a fix (
c
t
o ensure th
a
t defect fixin
g
(K1)

is assesse
d

S
ection 2.2).
n
test planni
n
r
ia specified
c
tivities to co
r
at project
m
o
r cancelled
.
Q


r
es or script
s
information
identificatio
n
d
, optionally,
c
ution
basis and t
e

t
ion tools, a
c
s
and versio
r
to establis
h
o
r a mistake
e
pancy, for
e
c
onfirmation
a
t defects ha
g did not un
c
d
against the
n
g
should be c
h
nsolidate ex
p
m
ilestones s
u

), a mileston
Internatio
Software T
e
Q
ualification
s
31-M
a
s
are specifi
e
needed for
t
n
of test dat
a
preparing t
e
e
st cases
c
cording to t
h
ns of the so
f
h
their cause
in the way t
h

e
xample, re-
testing), ex
e
ve not been
c
over other
defined
h
anged
p
erience,
u
ch as when
e has been
nal
e
sting
s
Board
a
r-2011
e
d by
t
est
a
)
e
st

h
e
f
tware
(e.g.,
h
e test
e
cution
a
Certi
f
Found
a


Version
2
© Internation
a

Test clo
s
o Che
c
o Clo
s
o Doc
u
o Fin

a
o Han
d
o
A
na
l
o Usi
n
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
s
ure activitie
c
king which
s
ing incident
u
menting th
e
a

lizing and a
r
d
ing over th
e
l
yzing lesso
n
n
g the inform
e
r
y
llabus

Q
ualifications Board
s include th
e
planned deli
reports or r
a
e
acceptanc
e
r
chiving test
w
e
testware t

o
n
s learned t
o
ation gather
e

e
following
m
verables ha
v
a
ising chang
e
e
of the syst
e
w
are, the te
s
o
the mainte
n
o
determine
c
e
d to impro
v

Page 17 of
m
ajor tasks:
v
e been deli
v
e
records fo
r
e
m
s
t environme
n
n
ance organ
i
c
hanges ne
e
v
e test matur
78
v
ered
r
any that re
m
n
t and the t

e
i
zation
e
ded for futu
r
ity
Q


m
ain open
e
st infrastruc
t
r
e releases
a
Internatio
Software T
e
Q
ualification
s
31-M
a
t
ure for later
a
nd projects

nal
e
sting
s
Board
a
r-2011
reuse
Certi
f
Found
a


Version
2
© Internation
a

1.5

Terms
Error gu
e

Backg
r
The min
d
softwar

e
respons
i
an inde
p
carried
o

A
certai
n
at findin
g
develop
e
be defin
e
o Tes
t
o Tes
t
o Tes
t
tea
m
o Tes
t
certi

People

a
by man
a
meets it
s

Identifyi
n
author.
A
in the m
a
pessimi
s
experie
n

If errors,
testers
a
during r
e

The test
e
defects,
defect i
n
save tim

Commu
n
unwant
e
relation
s
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
The P
s
e
ssing, inde
p
r
ound
d
set to be u
s
e
. With the ri
g

i
bility to a te
s
p
endent vie
w
o
ut at any le
v
n
degree of i
n
g
defects an
d
e
rs can effici
e
d as show
n
t
s designed
b
t
s designed
b
t
s designed
b
m

) or test sp
e
t
s designed
b
fication by a
a
nd projects
a
gement and
s
objectives.
n
g failures d
u
A
s a result, t
e
a
nagement
o
s
m, a critical
n
ce on which
defects or f
a
a
nd the anal
y

e
views as w
e
e
r and test l
e
progress an
n
formation c
a
e and mone
y
n
ication pro
b
e
d news abo
u
s
hips betwe
e
e
r
y
llabus

Q
ualifications Board
s
ycholo

g
p
endence
s
ed while te
s
g
ht mindset
d
s
ter is typica
w
by trained
a
v
el of testing
n
dependen
c
d
failures. In
d
ently find m
a
n
here from l
o
b
y the perso
b

y another p
b
y a person(
e
cialists (e.g
.
b
y a person(
n external b
o
are driven b
y
other stake
h
Therefore, i
t
u
ring testing
e
sting is oft
e
o
f product ri
s
eye, attenti
o
to base err
o
a
ilures are c

o
y
sts, design
e
e
ll as in testi
n
e
ader need
g
d risks in a
c
a
n help the
m
y
later, and
r
b
lems may o
c
u
t defects. H
e
n testers an
d

g
y of Te
s

s
ting and re
v
d
evelopers
a
lly done to h
a
nd professi
o
.
c
e (avoiding
t
d
ependenc
e
a
ny defects i
o
w to high:
n(s) who wr
o
erson(s) (e.
g
s) from a dif
f
.
, usability o
r

s) from a dif
f
o
dy)
y
objectives
.
h
olders, for
e
t
is importan
may be per
c
e
n seen as a
s
ks. Looking
o
n to detail,
g
o
r guessing.
o
mmunicate
e
rs and deve
n
g.
g

ood interpe
r
c
onstructive
w
m
improve th
e
r
educe risks
.
c
cur, particu
owever, the
r
d
others:
Page 18 of
s
ting (K
v
iewing is dif
f
a
re able to t
e
elp focus ef
f
o
nal testing

r
t
he author bi
e
is not, how
e
n their own
c
o
te the soft
w
g
., from the
d
f
erent organ
i
r
performan
c
f
erent organ
i
.
People ten
d
e
xample, to
f
t to clearly s

c
eived as cri
destructive
a
for failures i
g
ood comm
u
d in a const
r
lopers can
b
r
sonal skills
w
ay. For th
e
e
ir skills. Def
e
.

larly if tester
r
e are sever
a
78
2)

f

erent from t
h
e
st their own
f
ort and prov
r
esources. I
n
as) often m
a
e
ver, a repla
c
c
ode. Sever
a
w
are under te
d
evelopmen
t
i
zational gro
u
c
e test speci
a
i
zation or co

m
d
to align th
e
f
ind defects
o
tate the obj
e
ticism again
s
a
ctivity, eve
n
n a system
r
u
nication wit
h
r
uctive way,
b
e avoided.
T
to communi
c
author of th
e
cts found a
s are seen

o
a
l ways to i
m
Q


h
at used wh
i
code, but s
e
ide addition
a
n
dependent
t
a
kes the test
e
c
ement for f
a
a
l levels of i
n
st (low level
t
team)
u

p (e.g., an
i
a
lists)
m
pany (i.e.,
e
ir plans with
o
r to confir
m
e
ctives of tes
s
t the produ
c
n
though it i
s
r
equires curi
o
h
developm
e
bad feelings
T
his applies
t
c

ate factual i
e software
o
nd fixed dur
i
o
nly as mess
m
prove com
m
Internatio
Software T
e
Q
ualification
s
31-M
a
25 minu
t
i
le developin
e
paration of
t
a
l benefits, s
u
t
esting may

b
e
r more effe
c
a
miliarity, a
n
n
dependenc
e
of independ
i
ndependen
t
outsourcing
the objectiv
m
that softwa
r
ting.
c
t and again
s
s
very constr
u
o
sity, profes
s
e

nt peers, an
between th
e
t
o defects fo
u
nformation
a
o
r document,
i
ng testing
w
engers of
m
unication a
n
nal
e
sting
s
Board
a
r-2011
t
es
g
t
his
u

ch as
b
e
c
tive
n
d
e
can
ence)
t
test
or
es set
r
e
s
t the
u
ctive
s
ional
d
e

u
nd
a
bout
w

ill
n
d
Certi
f
Found
a


Version
2
© Internation
a

o Star
t
qual
o Co
m
per
s
findi
o Try
t
o Con
f

f
ied Test
e

a
tion Level S
y
2
011
a
l Software Testing
Q
t
with collab
o
ity systems
m
municate fi
n
s
on who cre
a
ngs
t
o understan
f
irm that the
e
r
y
llabus

Q
ualifications Board

o
ration rathe
n
dings on th
e
a
ted it, for ex
d how the o
t
other perso
n

r than battle
s
e
product in
a
ample, write
t
her person
f
n
has under
s
Page 19 of
s
– remind
e
a
neutral, fa

c
objective a
n
f
eels and wh
s
tood what y
o
78
e
veryone of t
h
c
t-focused
w
n
d factual in
c
y they react
o
u have sai
d
Q


h
e common
w
ay without c
r

c
ident report
s
as they do
d
and vice v
e
Internatio
Software T
e
Q
ualification
s
31-M
a
goal of bett
e
r
iticizing the
s
and revie
w
e
rsa
nal
e
sting
s
Board
a

r-2011
e
r
w

Certi
f
Found
a


Version
2
© Internation
a

1.6

Involve
m
code of
e
inappro
p
followin
g

PUBLIC

CLIENT

of their
c

PRODU
C
and sys
t

JUDGM
E
judgme
n

MANAG
ethical
a

PROFE
S
consiste

COLLE
A
promote

SELF -
C
professi
o

Refer
e
1.1.5 Bl
1.2 Bei
z
1.3 Bei
z
1.4 Het
z
1.4.5 Bl
1.5 Bla
c
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
Code
o
m
ent in softw
e
thics is nec
p

riate use. R
e
g
code of eth
- Certified s
o
AND EMPL
O
c
lient and e
m
C
T - Certifie
d
t
ems they te
s
E
NT- Certifi
e
n
t
EMENT - C
e
a
pproach to t
S
SION - Ce
r
nt with the p

A
GUES - Ce
r
cooperatio
n
C
ertified soft
w
o
n and shall
e
nces
ack, 2001,
K
z
er, 1990, Bl
a
z
er, 1990, H
e
z
el, 1988
ack, 2001,
C
c
k, 2001, He
t
e
r
y

llabus

Q
ualifications Board
o
f Ethic
s
are testing
e
essary, am
o
e
cognizing t
h
ics:
o
ftware test
e
O
YER - Cer
t
m
ployer, con
s
d
software t
e
s
t) meet the
e

d software
t
e
rtified softw
a
he manage
m
r
tified softwa
r
ublic interes
t
r
tified softw
a
n
with softwa
w
are testers
promote an
K
aner, 2002
a
ck, 2001,
M
e
tzel, 1988,
M
C
raig, 2002

t
zel, 1988

s

e
nables indi
v
o
ng other re
a
h
e ACM an
d
e
rs shall act
t
ified softwa
r
s
istent with t
h
e
sters shall
e
highest prof
e
t
esters shall
a

re test ma
n
m
ent of soft
w
r
e testers sh
t

a
re testers s
h
re develope
r
shall partici
p
ethical appr
o
M
yers, 1979
M
yers, 1979
Page 20 of
v
iduals to lea
a
sons to ens
u
d
IEEE code

consistently
r
e testers sh
a
h
e public int
e
e
nsure that t
h
e
ssional sta
n
maintain int
e
n
agers and l
e
w
are testing
all advance
h
all be fair t
o
r
s
p
ate in lifelo
n
o

ach to the
p
78
rn confidenti
u
re that the i
of ethics for
with the pu
b
a
ll act in a
m
e
rest
h
e deliverab
n
dards possi
e
grity and in
d
e
aders shall
the integrity
and suppor
t
n
g learning
r
p

ractice of th
Q


al and privil
e
nformation i
s
engineers, t
h
b
lic interest
m
anner that i
s
les they pro
v
ble
d
ependence
subscribe to
and reputati
o
t
ive of their
c
r
egarding th
e
e professio

n
Internatio
Software T
e
Q
ualification
s
31-M
a
10 minu
t
e
ged inform
a
s
not put to
h
e ISTQB st
s
in the best
v
ide (on the
p
in their prof
e
and promot
on of the pr
o
c
olleagues,

a
e
practice of
n

nal
e
sting
s
Board
a
r-2011
t
es
a
tion. A
ates the
interests
p
roducts
e
ssional
e an
o
fession
a
nd
their
Certi
f

Found
a


Version
2
© Internation
a

2.
T
Cycl
e

Learn
i
The obj
e

2.1 So
f
LO-2.1.
1
LO-2.1.
2
LO-2.1.
3

2.2 Te
s

LO-2.2.
1

2.3 Te
s
LO-2.3.
1
LO-2.3.
2
LO-2.3.
3
LO-2.3.
4
LO-2.3.
5

2.4 Ma
LO-2.4.
1
LO-2.4.
2
LO-2.4.
3
f
ied Test
e
a
tion Level S
y
2

011
a
l Software Testing
Q
T
estin
g
e
(K2)
i
ng Obje
c
e
ctives identi
f
tware De
v
1
Explain
t
develop
m
2
Recogni
of proje
c
3
Recall c
h
s

t Levels
(
1
Compar
e
typical t
a
who tes
t
s
t Types (
1
Compar
e
related)
2
Recogni
3
Identify
a
(K2)
4
Identify
a
or archit
e
5
Describ
e
intenanc

e
1
Compar
e
with res
p
2
Recogni
(K1)
3
. Describ
e
e
r
y
llabus

Q
ualifications Board
g
Throu
g
c
tives fo
r

fy what you
v
elopme
n

t
he relations
m
ent life cy
c
ze the fact t
h
c
t and produ
c
h
aracteristic
s
(
K2)
e
the differe
n
a
rgets of tes
t
t
, types of d
e
K2)
e
four softw
a
by example
ze that func

t
a
nd describ
e
a
nd describ
e
e
cture (K2)
e
the purpos
e
e
Testing
(
e
maintenan
p
ect to test t
y
ze indicator
s
e
the role of
r

g
hout t
h
r

Testing
will be able
t
n
t Models
(
hip between
c
le, by giving
h
at software
c
t characteri
s
s
of good te
s
n
t levels of t
e
t
ing (e.g., fu
n
e
fects and fa
a
re test type
s
(K2)
t

ional and st
r
e
non-functi
o
e
test types
b
e
of confirm
a
(
K2)
ce testing (t
e
y
pes, trigger
s
for mainte
n
r
egression t
e
Page 21 of
h
e Soft
w
Through
o
t

o do followi
n
(
K2)
developme
n
examples u
s
developme
n
s
tics (K1)
s
ting that ar
e
e
sting: majo
r
n
ctional or s
t
ilures to be i
d
s
(functional
,
r
uctural test
s
o

nal test typ
e
b
ased on th
e
a
tion testing
e
sting an exi
s for testing
n
ance testin
g
e
sting and i
m
78
w
are Li
f
o
ut the
S
n
g the comp
l
n
t, test activi
t
s

ing project
a
n
t models m
u
e
applicable
t
r
objectives,
t
ructural) an
d
d
entified (K
2
,
non-functio
s
occur at an
e
s based on
n
e
analysis of
a
and regress
sting syste
m
and amount

g
(modificati
o
m
pact analys
Q


f
e
1
S
oftware
L
l
etion of eac
h
t
ies and wor
a
nd product
u
st be adapt
e
t
o any life c
y
typical obje
c
d

related wo
r
2
)
nal, structur
a
y test level (
n
on-function
a
software s
y
ion testing (
K
m
) to testing
a
of testing (
K
o
n, migration
is in mainte
n
Internatio
Software T
e
Q
ualification
s
31-M

a
1
15
min
L
ife Cycl
e
h
module.
k products i
n
types (K2)
e
d to the co
n
y
cle model (
K
c
ts of testing
,
r
k products,
a
l and chan
g
K1)
al requirem
e
y

stem’s stru
c
K
2)
a
new applic
K
2)
and retirem
n
ance (K2)
nal
e
sting
s
Board
a
r-2011
utes

e

n
the
n
text
K
1)
,

p
eople
g
e-
e
nts
c
ture
ation
ent)
Certi
f
Found
a


Version
2
© Internation
a

2.1

Terms
Comme
r
verificati

Backg
r

Testing
d
Differen
t
2.1.1
A
lthoug
h
corresp
o

The fou
r
o Co
m
o Inte
g
o Sys
t
o Acc
e

In practi
c
dependi
n
integrati
o

Softwar

e
design
d
more te
s
(CMMI)
o
test desi
2.1.2
Iterative
-
and test
i
Applicat
i
system
t
iteration
.
which s
h
first one
.
2.1.3
In any li
f
o For
e
o Eac
h

o The
dev
e
o Tes
t
dev
e

Test lev
e
architec
t
product
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
Softw
a
r
cial Off-The
-
on, V-model

r
ound
d
oes not exi
s
t
developme
n
V-model
h
variants of
o
nding to th
e
r
levels used
m
ponent (uni
t
g
ration testi
n
t
em testing
e
ptance test
i
c
e, a V-mod
e

n
g on the pr
o
o
n testing af
t
e
work prod
u
d
ocuments a
n
s
t levels. Re
f
o
r ‘Software
gn) can be
c
Iterative
-
-
incremental
i
ng a syste
m
i
on Develop
m
t

hat is produ
c
.

A
n increm
e
h
ould also b
e
.
Verification
Testing
w
f
e cycle mod
e
very devel
o
h
test level
h
analysis an
d
e
lopment ac
t
t
ers should
b

e
lopment life
e
ls can be c
o
t
ure. For ex
a
into a syste
m
e
r
y
llabus

Q
ualifications Board
a
re Dev
e
-
Shelf (COT
S
s
t in isolatio
n
n
t life cycle
m
(Sequent

the V-mode
l
e
four develo
p
in this sylla
b
t
) testing
n
g
i
ng
e
l may have
o
ject and th
e
t
er compon
e
u
cts (such a
s
n
d code) pr
o
f
erences for
g

life cycle pr
o
c
arried out d
u
-
increme
n
developme
n
m
in a series
o
m
ent (RAD),
c
ed using th
e
e
nt, added to
e
tested. Re
g
and validati
o
w
ithin a L
el, there are
o
pment activ

i
h
as test obje
c
d
design of t
e
t
ivity
b
e involved i
n
cycle
o
mbined or
r
a
mple, for th
e
m
, the purch
a

e
lopme
n
S
), iterative-
i
n

; test activit
i
m
odels nee
d
ial Devel
o
l
exist, a co
m
p
ment level
s
b
us are:
more, fewe
r
e
software p
r
e
nt testing, a
n
s
business s
c
o
duced durin
g
eneric wor

k
o
cesses’ (IE
E
u
ring the de
v
n
tal Devel
o
n
t is the pro
c
o
f short dev
e
Rational U
n
e
se models
m
others dev
e
g
ression test
o
n can be c
a
ife Cycle
M

several cha
i
ty there is a
c
tives specif
i
e
sts for a gi
v
n
reviewing
d
r
eorganized
d
e
integration
a
ser may pe
r
Page 22 of
n
t Model
i
ncremental
i
es are relat
e
d
different ap

o
pment M
o
m
mon type o
f
s
.
r
or different
r
oduct. For e
n
d system i
n
c
enarios or
u
g developm
e
k
products in
E
E/IEC 122
0
v
elopment o
f
o
pment M

c
ess of esta
b
e
lopment cy
c
n
ified Proces
s
m
ay be test
e
e
loped previ
o
ing is increa
s
a
rried out on
M
odel (K
2
racteristics
o
correspond
i
i
c to that lev
e
v

en test leve
l
d
ocuments
a
d
epending o
of a Comm
e
r
form integr
a
78
s (K2)

developmen
e
d to softwa
r
proaches to
o
del) (K2)
f
V-model u
s
levels of de
v
xample, the
r
n

tegration te
s
u
se cases, r
e
e
nt are often
clude Capa
b
0
7). Verificat
f
the softwar
e
odels (K2
b
lishing requ
i
c
les. Exampl
s
(RUP) and
e
d at several
o
usly, forms
a
s
ingly impor
t

each incre
m
2
)
o
f good testi
n
ng testing a
c
e
l
should beg
i
a
s soon as d
r
n the nature
e
rcial Off-Th
e
a
tion testing
a
Q


t model, vali
r
e developm
e

testing.
s
es four test
v
elopment a
n
r
e may be c
o
s
ting after s
y
e
quirements
s
the basis o
f
b
ility Maturit
y
ion and vali
d
e
work prod
u
)

i
rements, de
es are: prot

o
agile devel
o
test levels
d
a
growing p
a
t
ant on all it
e
m
ent.
n
g:
c
tivity
i
n during the
r
afts are ava
of the proje
c
e
-Shelf (CO
T
a
t the syste
m
Internatio

Software T
e
Q
ualification
s
31-M
a
20 minu
t
dation,
e
nt activities
levels,
n
d testing,
o
mponent
y
stem testin
g
specificatio
n
f
testing in o
n
y
Model Inte
g
d
ation (and

e
u
cts.
signing, buil
d
o
typing, Rap
o
pment mod
e
d
uring each
a
rtial system
e
rations afte
r
correspond
i
ilable in the
c
t or the sys
t
T
S) software
m
level (e.g.,
nal
e
sting

s
Board
a
r-2011
t
es
.
g
.
n
s,
n
e or
g
ration
e
arly
d
ing
id
e
ls. A
,
r
the
i
ng
t
em

Certi
f
Found
a


Version
2
© Internation
a

integrati
o
(functio
n
f
ied Test
e
a
tion Level S
y
2
011
a
l Software Testing
Q
o
n to the inf
r
n

al and/or n
o
e
r
y
llabus

Q
ualifications Board
r
as
t
ructure a
o
n-functional
,

nd other sys
,
and user a
n
Page 23 of
tems, or sy
s
n
d/or operati
78
s
tem deploy
m

onal testing
)
Q


m
ent) and a
c
)
.
Internatio
Software T
e
Q
ualification
s
31-M
a
c
ceptance te
s
nal
e
sting
s
Board
a
r-2011
s
ting

Certi
f
Found
a


Version
2
© Internation
a

2.2

Terms
A
lpha te
integrati
o
test envi

Backg
r
For eac
h
product(
being te
s
and spe
c

Testing
a
2.2.1
Test ba
s
o Co
m
o Det
a
o Cod
e

Typical
t
o Co
m
o Pro
g
o Dat
a
o Dat
a

Compo
n
verifies
t
testable
.
develop

m

Compo
n
such as
structur
a
specific
a

Typicall
y
develop
m
testing
u
they are

One ap
p
called a
based o
n
executin

f
ied Test
e
a
tion Level S

y
2
011
a
l Software Testing
Q
Test L
e
sting, beta t
e
o
n, integrati
o
ronment, te
s
r
ound
h
of the test l
s) being ref
e
s
ted), typica
l
c
ific approa
c
a
system’s c
Compon

s
is:
m
ponent req
u
a
iled design
e

t
est objects:
m
ponents
g
rams
a
conversion
a
base modul
n
ent testing (
a
t
he functioni
n
.
It may be d
o
m
ent life cyc

n
ent testing
m
resource-be
a
l testing (e.
g
a
tion of the c
y
, componen
m
ent enviro
n
u
sually invol
v
found, with
o
p
roach to co
m
test-first ap
p
n
cycles of d
g the comp
o
e
r

y
llabus

Q
ualifications Board
e
vels (
K
e
sting, com
p
o
n testing, n
o
s
t level, test-
d
evels, the f
o
e
renced for
d
l
defects an
d
c
hes and res
onfiguration
ent Testi
n

u
irements

/ migration
p
es
a
lso known
a
n
g of, softw
a
o
ne in isolat
i
le and the s
y
m
ay include
t
havior (e.g.,
g
., decision
c
omponent, t
h
t testing oc
c
n
ment, such

v
es the prog
r
o
ut formally
m
m
ponent tes
t
p
roach or te
s
eveloping t
e
o
nent tests c
o


K
2)

p
onent testin
g
o
n-functiona
l
d
riven devel

o
llowing can
b
d
eriving test
c
d
failures to
b
ponsibilities.
data shall b
e
n
g (K2)
p
rograms
a
s unit, mod
u
a
re modules,
i
on from the
y
stem. Stub
s
t
esting of fu
n
searching f

o
c
overage). T
e
h
e software
c
urs with acc
e
as a unit tes
r
ammer who
m
anaging th
e
t
ing is to pre
s
t-driven dev
e
e
st cases, th
e
o
rrecting an
y
Page 24 of
g
, driver, fiel
d

l
requireme
n
opment, us
e
b
e identified
c
ases (i.e., t
h
b
e found, te
s

e
considere
d
u
le or progr
a
programs,
o
rest of the s
y
s
, drivers an
d
n
ctionality a
n

o
r memory l
e
e
st cases ar
e
design or th
e
e
ss to the c
o
t framework
wrote the c
o
e
se defects.
pare and au
t
e
lopment. T
h
e
n building
a
y
issues and
78
d
testing, fu
n

n
t, robustnes
s
e
r acceptanc
e
: the generi
c
h
e test basi
s
s
t harness re
d
during test
a
m testing) s
o
bjects, clas
s
y
stem, depe
d
simulators
n
d specific n
o
e
aks) or rob
u

e
derived fr
o
e
data mode
o
de being te
s
or debuggin
o
de. Defects
t
omate test
c
h
is approac
h
nd integrati
n
iterating un
t
Q


n
ctional req
u
s
testing, st
u

e
testing
c
objectives,
t
s
), the test o
b
quirements
a
planning,
earches for
d
s
es, etc., tha
nding on th
e
may be use
d
o
n-functiona
l
u
stness testi
n
o
m work pro
d
l.
s

ted and wit
h
g tool. In pr
are typicall
y
c
ases befor
e
h
is highly ite
n
g small pie
c
t
il they pass.
Internatio
Software T
e
Q
ualification
s
31-M
a
40 minu
t
u
irement,
u
b, system t
e

t
he work
b
ject (i.e., w
h
a
nd tool sup
p
d
efects in, a
n
t are separa
t
e
context of t
d
.
l
characteris
t
n
g, as well a
s
d
ucts such a
s
h
the suppor
t
actice, com

p
y
fixed as so
o
e
coding. Thi
s
rative and i
s
c
es of code,
a

nal
e
sting
s
Board
a
r-2011
t
es
e
sting,
h
at is
p
ort,
n
d

t
ely
h
e
t
ics,
s

s
a
t
of a
p
onent
o
n as
s
is
s

a
nd
Certi
f
Found
a


Version
2

© Internation
a

2.2.2
Test ba
s
o Soft
w
o Arc
h
o Wor
o Use

Typical
t
o Sub
s
o Dat
a
o Infr
a
o Inte
r
o Sys
t

Integrati
o
system,

There m
varying
s
1. Co
m
afte
r
2. Sys
t
har
d
org
a
Busi
issu
e

The gre
a
compon
e

System
a
bottom-
u
or comp
o
be incre
m

Testing
o
testing
a

A
t each
are inte
g
the mod
u
testing.
B

Ideally,
t
tests ar
e
order re
q

f
ied Test
e
a
tion Level S
y
2
011

a
l Software Testing
Q
Integrati
o
s
is:
w
are and sy
s
h
itecture
kflows
cases
t
est objects:
s
ystems
a
base imple
m
a
structure
r
faces
t
em configur
a
o
n testing te

such as the
ay be more
t
s
ize as follo
w
m
ponent inte
g
r
component
t
em integrati
o
d
ware and s
o
a
nization ma
y
ness proce
s
e
s may be s
i
a
ter the sco
p
e
nt or syste

m
a
tic integrati
o
u
p), function
a
o
nen
t
s. In o
r
m
ental rath
e
o
f specific n
o
a
s well as fu
n
stage of int
e
g
rating mod
u
u
les, not the
B
oth functio

n
t
esters shoul
e
planned be
q
uired for m
o
e
r
y
llabus

Q
ualifications Board
o
n Testin
g

s
tem design

m
entation
a
tion and co
sts interface
operating s
y
t

han one le
v
w
s:
g
ration testi
n
testing
o
n testing te
o
ftware and
m
y
control onl
y
s
ses implem
e
i
gnificant.
p
e of integra
t
m
, which ma
y
o
n strategies
a

l tasks, tra
n
r
der to ease
e
r than “big b
o
n-functiona
l
n
ctional testi
n
e
gration, test
e
u
le A with m
o
functionalit
y
n
al and stru
c
d understan
d
fore compo
n
o
st efficient
t

g
(K2)
nfiguration
d
s between c
y
stem, file s
y
v
el of integra
t
n
g tests the i
n
sts the inter
a
m
ay be don
e
y
one side o
f
e
nted as wo
r
t
ion, the mor
y

lead to inc
r
may be ba
s
n
saction pro
c
fault isolatio
n
ang”.
l
characteris
t
n
g.
e
rs concent
r
o
dule B they
y
of the indiv
i
c
tural approa
d
the archit
e
n
ents or syst

e
t
esting.
Page 25 of
d
ata
omponents,
y
stem and h
a
t
ion testing
a
n
teractions
b
a
ctions betw
e
e
after syste
m
f
the interfa
c
r
kflows may
e difficult it
b
r

eased risk
a
s
ed on the s
y
c
essing seq
u
n
and detec
t
t
ics (e.g., pe
r
ate solely o
n
are interest
e
i
dual modul
e
ches may b
e
e
cture and in
f
e
ms are buil
78
interactions

a
rdware, and
a
nd it may b
e
b
etween soft
w
e
en differen
t
m
testing. In
e. This mig
h
involve a se
r
b
ecomes to i
s
a
nd addition
a
y
stem archit
e
u
ences, or s
o
t

defects ear
l
rformance)
m
n
the integra
t
e
d in testing
e
as that wa
s
e
used.
f
luence inte
g
t, those co
m
Q


with differe
n
interfaces
b
e
carried out
w
are comp

o
t
systems or
this case, th
h
t be consid
e
r
ies of syste
m
s
olate defec
t
a
l time for tr
o
e
cture (such
o
me other a
s
l
y, integratio
n
m
ay be inclu
d
t
ion itself. F
o

the commu
n
s
done durin
g
g
ration plan
n
m
ponents ca
n
Internatio
Software T
e
Q
ualification
s
31-M
a
n
t parts of a
b
etween sys
t
on test obje
c
o
nents and i
s
between

e developin
g
e
red as a ris
k
m
s. Cross-pl
t
s to a speci
f
o
ubleshootin
g
as top-dow
n
s
pect of the
s
n
should no
r
d
ed in integ
r
o
r example, i
f
n
ication bet
w

g
componen
t
n
ing. If integr
a
n
be built in t
h
nal
e
sting
s
Board
a
r-2011
t
ems.
c
ts of
s
done
g

k
.
atform
f
ic
g

.
n
and
s
ystem
r
mally
r
ation
f
they
w
een
t

a
tion
h
e