Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
22Activity
0 of .
Results for:
No results containing your search query
P. 1
All in One Testing Documents

All in One Testing Documents

Ratings: (0)|Views: 635 |Likes:
Published by api-3772931

More info:

Published by: api-3772931 on Oct 17, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

Testing
Defect testing
\u2022
Testing programs to establish the presence of system defects
Objectives
\u2022
To understand testing techniques that are geared to discover program faults
\u2022
To introduce guidelines for interface testing
\u2022
To understand specific approaches to object-oriented testing
\u2022
To understand the principles of CASE tool support for testing
Topics covered
\u2022
Defect testing
\u2022
Integration testing
\u2022
Object-oriented testing
\u2022
Testing workbenches
The testing process
qComponent testing
\ue000Testing of individual program components
\ue000Usually the responsibility of the component developer (except sometimes for
critical systems)
\ue000Tests are derived from the developer\u2019s experience
qIntegration testing

\ue000Testing of groups of components integrated to create a system or sub-system
\ue000The responsibility of an independent testing team
\ue000Tests are based on a system specification

Testing phases
Component
testing
Integration
testing
Software developer
Independent testing team
Defect testing
qThe goal of defect testing is to discover defects in programs
qAsuccessful defect test is a test which causes a program to behave in an anomalous
way
qTests show the presence not the absence of defects
Testing priorities
qOnly exhaustive testing can show a program is free from defects. However, exhaustive
testing is impossible

qTests should exercise a system's capabilities rather than its components
qTesting old capabilities is more important than testing new capabilities
qTesting typical situations is more important than boundary value cases

Test data and test cases
qTest data Inputs which have been devised to test the system
1
Testing
qTest cases Inputs to test the system and the predicted outputs from these inputs if the
system operates according to its specification
The defect testing process
Design test
cases
Prepare test
data
Run program
with test data
Compare r esults
to test cases
Test
cases
Test
data
Test
results
Test
reports
Black-box testing

qAn approach to testing where the program is considered as a \u2018black-box\u2019
qThe program test cases are based on the system specification
qTest planning can begin early in the software process

Ie
Input test data
Oe
Output test results
System
Inputs causing
anomalous
b ehavio ur
Outputs which reveal
the presence of
defects
Equivalence partitioning
qInput data and output results often fall into different classes where all members of a
class are related
qEach of these classes is an equivalence partition where the program behaves in an
equivalent way for each class member
qTest cases should be chosen from each partition
2
Testing
Sy stem
Ou tput s
I nva li d in pu ts
Va li d in pu ts
qPartition system inputs and outputs into \u2018equivalence sets\u2019
\ue000If input is a 5-digit integer between 10,000 and 99,999, equivalence partitions are
<10,000, 10,000-99, 999 and > 10, 000
qChoose test cases at the boundary of these sets
\ue00000000,09999,10000, 99999, 10001
Between 10000 and99 99 9
Less than 100 00
More than99 99 9
9999
100 00
500 00
100 00 0
999 99
Input values
Between 4 and 10
Less than 4
More than 10
3
4
7
11
10
Number of input values
Search routine specification
procedure Search (Key : ELEM ; T: ELEM_ARRAY;
Found : in out BOOLEAN; L: in out ELEM_INDEX) ;
Pre-condition
-- the array has at least one element
T\u2019FIRST <= T\u2019LAST
Post-condition
-- the element is found and is referenced by L
( Found and T (L) = Key)
or
-- the element is not in the array
(not Found and not (exists i, T\u2019FIRST >= i <= T\u2019LAST, T (i) = Key ))
3

Activity (22)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
pravin216 liked this
scorpionking888 liked this
leelamanohark liked this
manu1234567778 liked this
me@scribd liked this
hindustan001 liked this
kprgroup liked this
kprgroup liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->