Professional Documents
Culture Documents
Istqb - Chapter I - II
Istqb - Chapter I - II
Main Contents
Why is Testing
ecessary!
What is Testing! Se"en Testing #rinciples Fundamental Test
#rocess
defects
$ole of Testing in
)nough!
*mista.e,
#roduces a defect *fault&
/ug,
Causes a failure in an
operation
user interface,
%ocumentation
*$e0uirements and design specifications in all electronic and hard document, When the
Time pressure
*%eadlines,
Comple1ity of
$e0uirement3Technology
4ac. of e1perience3s.ill 4ac. of information Fre0uent changes
in operation
Impro"e the 0uality of
software system
re0uirements
Industry+specific
6789+8:177:; Software Component Testing :87:177:; Standard for Software Test %ocumentation
I)))
found
run
The percentage of
chance to impro"e 0uality <= Impro"e and gi"e confidence software 0uality
Functional and on+ functional software re0uirements and characteristics *relia/ility& usa/ility& efficiency& maintaina/ility and porta/ility,
good manufacturing processes and meet defined re0uirements e1pectation of time& money and effort aspects used efficiently and effecti"ely the feelings of an indi"idual;
Quality includes
Quality depended on
%epends on le"el of
$IS>
$is. of missing important
faults
$is. of incurring failure
costs
$is. of releasing
window
$is. of o"er+testing&
ineffecti"e testing
What is Testing
Common o/5ecti"es of
Testing
%ifferentiate Testing
from %e/ugging
for decision+ma.ing
#re"enting defects
Anit3Component Test
Find /ugs in the
indi"idual pieces of the system under test /efore the pieces are fully integrated into the system Integration Test
Find /ugs in the
relationships and interfaces /etween pairs and groups of components in the system under test as the pieces come together System Test
and particular /eha"iors& functions& and responses of the system under test as a whole -cceptance3#ilot Test
%emonstrate that the
product is ready for deployment3release or to assess 0uality and gi"e information on the ris. of deployment3release Maintenance Test
Chec. for errors
'perational Test
-ssess non+functional
%e/ugging:
/ugs
$epair the code Chec. that the code is
e1ecuted as e1pected
#rogrammer de/ugs
Testing #rinciples
Testing shows presence
of defects
)1hausti"e testing is
impossi/le
Testing is conte1t
dependent
-/sence of errors
fallacy
Control
Test -nalysis and
%esign
Test Implementation
and )1ecution
and $eporting
Test Closure -cti"ities
-pproach
resources
and design
Schedule
criteria Control
Measure and analy?er
Testing
Initiate correcti"e
actions
Ma.e decisions
test data /ased on analysis of test items& its specification& /eha"ior and structure
Design
Select specific
com/inations of test data& actions& and e1pected results to co"er the test /asis <= test case& test procedure
)"aluate testa/ility of
en"ironment
test cases& create test data& write and prioriti?e test procedures
#repare test harnesses
Execution
)1ecute test suites and
"ersion of the software under test& test tools and the test ware
Compare actual and
e1pected results
$eport and analy?e
incidents
$epeat corrected and3or
updated tests
)1ecute confirmation
Closing
incident reports or raising change records for any that remain open the acceptance of the system and archi"ing test ware& the test en"ironment and the test infrastructure for later reuse
%ocumenting
Finali?ing
(anding
o"er the test ware to the maintenance organi?ation lessons learned to determine changes needed for future releases and pro5ects the information gathered to impro"e test maturity
-naly?ing
Asing
*$e+Testing,
)1ecuting test cases that
repeata/le
Asing the same inputs&
Models
Test 4e"els Test Types Maintenance Testing
B+Model Incremental
%e"elopment Model
%e"elopment *$-%,
$ational Anified #rocess
*$A#,
-gile de"elopment
of good testing:
of tests for a gi"en test le"el should /egin during the corresponding de"elopment acti"ity
Testers should /e
in"ol"ed in re"iewing documents as soon as drafts are a"aila/le in the de"elopment cycle;
Test 4e"els
Key Contents
Component Testing Integration Testing System Testing -cceptance Testing
Component3Anit Testing
/ugs in the indi"idual pieces of the system under test prior to system integration
Test
asis: Component re0uirements& detailed design& code Components& #rograms& %ata con"ersion3Migration programs& %ata/ase module
Test Objects:
#rogrammer
Integration Testing
Test Objective: Find
/ugs in the relationships and interfaces /etween pairs and group of components in the system under test as the pieces come together
Test
asis: Software and System %esign& -rchitecture& Wor.flow and Ase+cases Su/system data/ase implementation& Infrastructure& Interfaces
Test Objects:
performance
!esponsibility: Ideally
System Testing
/ugs in the o"erall and particular /eha"iors& functions& and responses of the system under test as a whole
Test
asis: System and software re0uirement specification& Ase cases& Functional specification& $is. analysis reports; user and operation manuals& System configuration
Test Types:
-cceptance Testing
Test Objective:
)sta/lish confidence in the system& parts of the system or specific non+ functional characteristics of the system
asis: Aser re0uirements& System re0uirements& Ase cases& Business processes& $is. analysis reports processes on fully integrated system& 'perational and maintenance processes& Aser procedures& Forms& $eports
acceptance testing& 'perational acceptance testing& Contract and regulation acceptance testing& -lpha and Beta testing;
!esponsibility: the
Test Types
Key Contents:
Functional Testing
$egression Testing
Functional Testing
Testing /ased on an
analysis of the specification of the functionality of a component or system; $eferred to /lac. /o1 testing and /y Tester
%ocuments: Functional
testing
on+Functional Testing
Testing 0uality
4e"els
on+Functional Testing
Structural Testing
Testing /ased on an
analysis of the internal structure of the component or system *while /o1 testing, thoroughness of testing through the co"erage of a set of structural elements or co"erage items
Measure the
Co"erage techni0ues:
Maintenance Testing
Key contents:
$easons for
maintenance testing
Maintenance testing
$ole of regression
addresses the change itself and what wasnFt changed and shouldnFt change
The maintenance of
e1isting software can account for o"er GH percent of all de"elopment effort
6HI of the cost of
Compare /etween Maintenance testing and new application testing $ole of regression testing and impact analysis
Software change impact
analysis is the acti"ity of the software maintenance process that determines possi/le effects of proposed software changes
This acti"ity is
necessary to /e aware of unintentional+effects caused /y the change and record them so that nothing is o"erloo.ed
- change has not only
impact on the source code& /ut also on the other related software artifacts& such as re0uirements& design& and test
that the rest of the system has not /een affected /y the maintenance wor.;