Beruflich Dokumente
Kultur Dokumente
33
Stages of Testing
Unit Testing
Program reviews.
Formal verification.
Testing the program itself.
black box and white box testing.
10
Regression Testing
Integration Testing
12
Main program used as a test driver and stubs are substitutes for
components directly subordinate to it.
Subordinate stubs are replaced one at a time with real components
(following the depth-first or breadth-first approach).
Tests are conducted as each component is integrated.
On completion of each set of tests and other stub is replaced with a
real component.
Regression testing may be used to ensure that new errors not
introduced.
13
13
14
14
Bottom - Up
Top - Down
Integration
Early
Early
Time to get
working
program
Late
Early
Late
Early
Drivers
Yes
No
Yes
Yes
Stub
No
Yes
Yes
Yes
Parallelism
Medium
Low
High
Medium
Test
specification
Easy
Hard
Easy
Medium
Product
control seq.
Easy
Hard
Easy
Hard
15
15
Big Bang
Sandwich
Early
Thread Testing
16
Smoke Testing
17
Validation Testing
18
Acceptance Testing
Making sure the software works correctly for intended
user in his or her normal work environment.
Alpha test
version of the complete software is tested by
customer under the supervision of the developer at
the developers site
Beta test
version of the complete software is tested by
customer at his or her own site without the developer
being present
19
Benchmark test.
Pilot testing.
Parallel testing.
20
20
System Testing
Recovery testing
checks systems ability to recover from failures
Security testing
verifies that system protection mechanism prevents improper
penetration or data alteration
Stress testing
program is checked to see how well it deals with abnormal
resource demands
Performance testing
tests the run-time performance of software
21
Performance Testing
Stress test.
Volume test.
Configuration test (hardware &
software).
Compatibility.
Regression tests.
Security tests.
22
Timing tests.
Environmental tests.
Quality tests.
Recovery tests.
Maintenance tests.
Documentation tests.
Human factors tests.
Testing Tools
Simulators.
Monitors.
Analyzers.
Test data generators.
24
Professional testers.
Analysts.
System designers.
Configuration management specialists.
Users.
25
25
26
26
Requirement tested.
Facet / feature / path tested.
Person & date.
Tools & code needed.
Test data & instructions.
Expected results.
Actual test results & analysis
Correction, schedule, and signoff.
27
27
27
Debugging
28
28
Debugging Approaches
Brute force
memory dumps and run-time traces are examined
for clues to error causes
Backtracking
source code is examined by looking backwards
from symptom to potential causes of errors
Cause elimination
uses binary partitioning to reduce the number of
locations potential where errors can exist
29
Thank you
30