Professional Documents
Culture Documents
ASSURANCE –TESTING
1
TESTING OVERVIEW [9.1]
testing is the process of finding differences between the specified
(expected) and the observed (existing) system behavior
Goal:
Goal:design
designtests
teststhat
thatwill
willsystematically
systematicallyfind
finddefects
defects
èè aim
aimis
isto
tobreak
breakthe
thesystem
system(make
(makeititfail)
fail)
3
COMP 211 TESTING3
TESTING — VERIFICATION & VALIDATION
verification is the process of making sure that we have built the
product right (i.e., it meets its stated requirements)
è most of the testing workflow is targeted at doing verification
X
Test
Model
Test
Case
TestX Test Test
Procedure Plan Evaluation
Test
Component
X
Defect
module
to be
tested
results
software
engineer
test cases
11
Integration Testing
Strategies
Options:
• the “big bang” approach
• an incremental construction strategy
12
g) Regression Testing
Bugs which been fixed once should not turn up again in subsequent
program versions.
13
Stress Testing
Test the system under extreme conditions (i.e., beyond the limits of
normal use)
Get real users to sit down and use the software to perform some
tasks
Ex: Can Word 12.0 load files created with Word 11.0?
Ex: "Save As… Word, Word Perfect, PDF, HTML, Plain Text"
Test
COMP 211 all compatibility requirements TESTING18
Documentation Testing
Test all instructions given in the documentation to ensure their
completeness and accuracy
Important Points:
Test automation has to be learned.
Testing tools are no replacement for testing staff.
Not everything can be tested, even with automation tools.
Automated tests must be continuously updated.
Automating tests cost time & money.
30