Академический Документы
Профессиональный Документы
Культура Документы
Version 2.3
EDS EDS specific information available – used where an EDS exceptions exist.
If this appears top right, it means animation applies to the slide. It will also appear
bottom right after the final animation mouse click. For Tutor’s use only.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 2 • EDS Internal
Other Symbols
EDS ISTQB Testing Foundation Course Version 2.3 Slide 3 • EDS Internal
Objectives
EDS ISTQB Testing Foundation Course Version 2.3 Slide 4 • EDS Internal
Areas covered
Fundamentals of testing
Testing Throughout the Software Lifecycle
Static Techniques
Test Design Techniques
Test Management
Tool Support for Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 5 • EDS Internal
03-23-05
Version 2.3
Fundamentals of Testing
Areas Covered
EDS ISTQB Testing Foundation Course Version 2.3 Slide 7 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 8 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 9 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 10 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 11 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 12 • EDS Internal
Why Testing is Necessary
Can manifest as
A flaw in a component or
Defect system that can cause the
component or system to fail to
perform its required function
May result in
EDS ISTQB Testing Foundation Course Version 2.3 Slide 13 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 14 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 15 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 16 • EDS Internal
Testing Terminology
EDS ISTQB Testing Foundation Course Version 2.3 Slide 17 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 18 • EDS Internal
Testing Terminology
EDS ISTQB Testing Foundation Course Version 2.3 Slide 19 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 20 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 21 • EDS Internal
Why Testing is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 22 • EDS Internal
Why Testing Is Necessary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 23 • EDS Internal
What is Testing?
EDS ISTQB Testing Foundation Course Version 2.3 Slide 24 • EDS Internal
What is Testing?
EDS ISTQB Testing Foundation Course Version 2.3 Slide 25 • EDS Internal
Why Testing is necessary
Hetzel 1998
EDS ISTQB Testing Foundation Course Version 2.3 Slide 26 • EDS Internal
What is Testing?
Test Objectives
• There are different test objectives:
– To find defects
– To gain confidence about the level of quality and to provide information
– To prevent defects
• Both dynamic testing and static testing can be used as a means for
achieving these objectives
• They provide information in order to improve:
– The system to be tested
– The development and testing processes
– Live operations (e.g. how long it takes for a process to run)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 27 • EDS Internal
What is Testing?
Test Objectives
• By designing tests early in the project life cycle it can help to prevent
defects from being introduced into code
• Reviews of documents throughout the lifecycle (e.g. requirements and
design) also help to prevent defects appearing in the code. More
about this when we cover Static techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 28 • EDS Internal
What is Testing?
Test Objectives – cost of fault correction
100
90
80
70
60
Relative 50
Cost
Multiples 40
30
20
10
0
Reqs Des Code Unit Accept Use
EDS ISTQB Testing Foundation Course Version 2.3 Slide 29 • EDS Internal
What is Testing?
Test Objectives
• The Objectives of testing can vary depending on the stage of testing
being conducted. E.g.:
EDS ISTQB Testing Foundation Course Version 2.3 Slide 30 • EDS Internal
What is Testing?
Test Objectives
EDS ISTQB Testing Foundation Course Version 2.3 Slide 31 • EDS Internal
Testing Terminology
EDS ISTQB Testing Foundation Course Version 2.3 Slide 32 • EDS Internal
What is Testing?
Testing v Debugging
• Debugging and testing are different:
– Testing can show failures that are caused by
defects
– Debugging identifies the cause of a defect,
repairs the code and checks that the defect
has been fixed correctly
• Testing then ensures that the fix does
indeed resolve the failure
• The responsibility for each activity is very
different, i.e.
– Testers test
– Developers debug
EDS ISTQB Testing Foundation Course Version 2.3 Slide 33 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 34 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 35 • EDS Internal
Why Testing is necessary
Myers 2004
EDS ISTQB Testing Foundation Course Version 2.3 Slide 36 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 37 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 38 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 39 • EDS Internal
General Testing Principles
• N.B It's called the "pesticide paradox" after the agricultural phenomenon, where bugs such as the
boll weevil build up tolerance to pesticides, leaving you with the choice of ever-more powerful
pesticides followed by ever-more powerful bugs or an altogether different approach.’ – Beizer 1995
EDS ISTQB Testing Foundation Course Version 2.3 Slide 40 • EDS Internal
General Testing Principles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 41 • EDS Internal
General Testing Principles
• If we build a system and, in doing so, find and fix defects ....
It doesn’t make it a good system
• Even after defects have been resolved it may still be unusable and/or
does not fulfil the users’ needs and expectations
EDS ISTQB Testing Foundation Course Version 2.3 Slide 42 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 43 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 44 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 45 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 46 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 47 • EDS Internal
Fundamental Test Process
• Tests should be designed using the test design techniques selected in the
test planning activity
• Major tasks are:
– Review the test basis
– From Analysis of test items, identify Test Conditions/Requirements and
required Test Data
– Design the tests (note – the detail, in the form of a Test Case, is developed in
the next stage)
– Evaluate testability of the requirements and system
– Design the test environment set-up
– Identify any required infrastructure and tools
EDS ISTQB Testing Foundation Course Version 2.3 Slide 48 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 49 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 50 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 51 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 52 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 53 • EDS Internal
Fundamental Test Process
Myers - 2004
Ref: Myers, The Art of Software Testing, J Wiley and Sons, 1979
EDS ISTQB Testing Foundation Course Version 2.3 Slide 54 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 55 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 56 • EDS Internal
Fundamental Test Process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 57 • EDS Internal
Psychology of Testing
• Historically testing was viewed as showing the system meets its requirements
• This has evolved to a stage where testing is performed with the primary aim
of finding faults rather than proving correctness. It is perceived as a
destructive process
• Seeking to find failures (the right mindset) can be viewed as criticism of the
product and/or its author
• But looking for failures is constructive!
– Time can be saved
– Risks reduced
– Costs reduced
– Skills improved
EDS ISTQB Testing Foundation Course Version 2.3 Slide 58 • EDS Internal
Psychology of Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 59 • EDS Internal
Psychology of Testing
Myers - 1979
EDS ISTQB Testing Foundation Course Version 2.3 Slide 60 • EDS Internal
Psychology of Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 61 • EDS Internal
Psychology of Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 62 • EDS Internal
Psychology of Testing
Independent testing
• The right mindset could enable Developers to test the code
• However, passing this responsibility to trained and professional
testing resources has many benefits (such as higher defect find
rates)
• Authors tend to bring across assumptions they have made when
developing the software. They are less likely to write tests to show
faults in their own software (human nature)
• With testing performed by independent testers, testing effort is
focused and not compromised by development effort and bias
• It is generally believed that objective independent testing is more
effective
EDS ISTQB Testing Foundation Course Version 2.3 Slide 63 • EDS Internal
Psychology of Testing
Independent testing
• There are several levels of Independence (from Low to High)
– Tests designed by the person(s) who wrote the software under
test
– Tests designed by another person(s) (e.g. from the
development team).
– Tests designed by a person(s) from a different organizational
group (e.g. an independent test team).
– Tests designed by a person(s) from a different organization or
company (e.g. outsourcing to an in-house or external test
specialist organisation)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 64 • EDS Internal
Fundamentals of Testing - Summary
• We learned why you can’t test everything and when to stop testing
– through Risk Analysis, Prioritisation and use of Exit Criteria
EDS ISTQB Testing Foundation Course Version 2.3 Slide 65 • EDS Internal
Fundamentals of Testing - Summary
• We learned about Testing:
– its main Objectives, i.e. to find and prevent defects and to gain confidence in
system Quality
– How we meet these Objectives
– How they can vary by Test Level
– That it is conducted before and after the code is delivered
– What activities it comprises
– That Debugging and Testing are different
EDS ISTQB Testing Foundation Course Version 2.3 Slide 66 • EDS Internal
Fundamentals of Testing - Summary
• We learned the Fundamental Test process:
– The Stages:
• Test Planning and Control
• Test Analysis and Design
• Test Implementation and Execution
• Evaluating Exit Criteria and Reporting
• Test Closure Activities
– And the main tasks for each stage of the process
EDS ISTQB Testing Foundation Course Version 2.3 Slide 67 • EDS Internal
03-23-05
Version 2.3
EDS ISTQB Testing Foundation Course Version 2.3 Slide 69 • EDS Internal
Software Development Models
The V-Model
EDS ISTQB Testing Foundation Course Version 2.3 Slide 70 • EDS Internal
V-Model
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 71 • EDS Internal
V-Model
EDS ISTQB Testing Foundation Course Version 2.3 Slide 72 • EDS Internal
V-Model
EDS ISTQB Testing Foundation Course Version 2.3 Slide 73 • EDS Internal
V Model
Watkins - 2001
EDS ISTQB Testing Foundation Course Version 2.3 Slide 74 • EDS Internal
Iterative Development Models
EDS ISTQB Testing Foundation Course Version 2.3 Slide 75 • EDS Internal
Iterative Development Models
User
Requirements
Code
Acceptance
Test
EDS ISTQB Testing Foundation Course Version 2.3 Slide 76 • EDS Internal
Testing within a Lifecycle Model
Test Levels should be adapted depending on Project nature. May be better to combine Test Levels, e.g. with COTS testing.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 77 • EDS Internal
Test Levels
Component Testing
Integration Testing
System testing
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 78 • EDS Internal
Component Testing
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 79 • EDS Internal
Component Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 80 • EDS Internal
Component Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 81 • EDS Internal
Integration Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 82 • EDS Internal
Integration Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 83 • EDS Internal
Component Integration Testing
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 84 • EDS Internal
Component Integration Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 85 • EDS Internal
Component Integration Testing
Test Planning
• To consider - should the integration testing approach:
EDS ISTQB Testing Foundation Course Version 2.3 Slide 86 • EDS Internal
Component Integration Testing
Top-down testing
Component
under test
P
Q R
S T U V
Stubs
EDS ISTQB Testing Foundation Course Version 2.3 Slide 87 • EDS Internal
Component Integration Testing
Top-down testing
Pro’s Con’s
• provides a limited working system • stubs only provide limited
early in the design process simulations of lower level
• depth first integration demonstrates components and could influence
end-to-end functions early in the spurious results
development process • breadth first means that higher
• early detection of design errors levels of the system must be
through early implementation of the artificially forced to generate
design structure output for test observations
• early testing of major control or
decision points
EDS ISTQB Testing Foundation Course Version 2.3 Slide 88 • EDS Internal
Component Integration Testing
Bottom-up testing
Component under test
P
P is the driver
for components
Q and R
Same for Q
and R
Q R driving their
components
S T U V
EDS ISTQB Testing Foundation Course Version 2.3 Slide 89 • EDS Internal
Component Integration Testing
Bottom-up testing
Pro´s Con´s
• using drivers instead of upper • unavailability of a demonstrable
level modules to simulate the system until late in the
environment for lower level development process
modules
• late detection of system
• necessary for critical, low level
system components structure errors
EDS ISTQB Testing Foundation Course Version 2.3 Slide 90 • EDS Internal
Component Integration Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 91 • EDS Internal
Component Integration Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 92 • EDS Internal
System Integration Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 93 • EDS Internal
System Testing
Context
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 94 • EDS Internal
System Testing
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 95 • EDS Internal
System Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 96 • EDS Internal
Functional System Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 97 • EDS Internal
Functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 98 • EDS Internal
Functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 99 • EDS Internal
Functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 100 • EDS Internal
Functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 101 • EDS Internal
Functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 102 • EDS Internal
Functional System Testing
Myers - 2004
EDS ISTQB Testing Foundation Course Version 2.3 Slide 103 • EDS Internal
Non-functional System Testing
Definition
Non-functional requirements
EDS ISTQB Testing Foundation Course Version 2.3 Slide 104 • EDS Internal
Non-functional System Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 105 • EDS Internal
Non-functional System Testing
Non-functional requirements
• * Note that ISTQB treats this as a Functional test. From the syllabus:
– ‘Security Testing A type of functional testing, security testing, investigates
the functions (e.g. a firewall) relating to detection of threats, such as viruses,
from malicious outsiders.’
EDS ISTQB Testing Foundation Course Version 2.3 Slide 106 • EDS Internal
Non-functional System Testing
Non-functional requirements
• The non-functional aspects of a system are all the attributes other than
business functionality, and are as important as the functional aspects.
These include:
– the look and feel and ease of use of the system
– how quickly the system performs
– how much the system can do for the user
• It is also about:
– how easy and quick the system is to install
– how robust it is
– how quickly the system can recover from a crash
EDS ISTQB Testing Foundation Course Version 2.3 Slide 107 • EDS Internal
Non-functional System Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 108 • EDS Internal
System Testing
Good Practices for System testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 109 • EDS Internal
System Integration Testing
Context
Definition
Objectives
EDS ISTQB Testing Foundation Course Version 2.3 Slide 110 • EDS Internal
System Integration Testing
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 111 • EDS Internal
System Integration Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 112 • EDS Internal
System Integration Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 113 • EDS Internal
System Integration Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 114 • EDS Internal
Acceptance Testing
Context
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 115 • EDS Internal
Acceptance Testing
Integration Integration
Technical
Test Plan
Test
Specification
Coding
EDS ISTQB Testing Foundation Course Version 2.3 Slide 116 • EDS Internal
Acceptance Testing
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 117 • EDS Internal
Acceptance Testing
Definition
• Usually the responsibility of the Customer/End user, though other
stakeholders may be involved. Customer may sub-contract the Acceptance
test to a third party
• Goal is to establish confidence in the system/part-system or specific non-
functional characteristics (e.g. performance)
• Usually for ensuring the system is ready for deployment into production
• May also occur at other stages, e.g.
– Acceptance testing of a COTS product before System Testing commences
– Acceptance testing a component’s usability during Component testing
– Acceptance testing a new significant functional enhancement/middleware release
prior to deployment into System Test environment.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 118 • EDS Internal
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 119 • EDS Internal
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 120 • EDS Internal
Acceptance Testing
User Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 121 • EDS Internal
Acceptance Testing
• ‘The objective of OAT is to confirm that the Application Under Test (AUT)
meets its operational requirements, and to provide confidence that the
system works correctly and is usable before it is formally "handed over" to
the operation user. OAT is conducted by one or more Operations
Representatives with the assistance of the Test Team’ 1 –Watkins 2001
EDS ISTQB Testing Foundation Course Version 2.3 Slide 122 • EDS Internal
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 123 • EDS Internal
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 124 • EDS Internal
Acceptance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 125 • EDS Internal
Acceptance Testing
• Both address acceptance testing for systems that are tested before and
after being moved to a customer’s site
EDS ISTQB Testing Foundation Course Version 2.3 Slide 126 • EDS Internal
Test Types – The Targets of Testing
Definitions
Functional Testing
Non-Functional Testing
Structural Testing
Confirmation & Regression Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 127 • EDS Internal
Test Types – The Targets of Testing
Definitions
EDS ISTQB Testing Foundation Course Version 2.3 Slide 128 • EDS Internal
Test Types – The Targets of Testing
Definitions
EDS ISTQB Testing Foundation Course Version 2.3 Slide 129 • EDS Internal
Functional Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 130 • EDS Internal
Non-Functional Testing
• May be performed at all Test levels (not just Non Functional Systems
Testing)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 131 • EDS Internal
Structural Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 132 • EDS Internal
Confirmation (Re-Testing) and Regression Testing
Re-testing: Testing that runs test cases that failed the last time
they were run, in order to verify the success of corrective
actions
EDS ISTQB Testing Foundation Course Version 2.3 Slide 133 • EDS Internal
Confirmation Testing (Re-Testing)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 134 • EDS Internal
Regression Testing
• If the test is re-run and passes you cannot necessarily say the fault
has been resolved because ..
• You also need to ensure that the modifications have not caused
unintended side-effects elsewhere and that the modified system still
meets its requirements – Regression Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 135 • EDS Internal
Regression Testing
• Selecting suitable tests involves :-
– knowledge of the bug fixes and how they affect the system
– understanding the areas that have frequent faults
– understanding which areas of the system have undergone the most
recent changes
– understanding the areas of the system which are most critical to the
user
– understanding the core features of the system which must function
correctly.
• The effectiveness of a regression test suite can diminish over time
for a number of reasons :-
– tests are added for short term goals but not removed
– tests become redundant due to functionality changes
– test suite is not updated when major functionality changes are
implemented
– execution time becomes prohibitively high
– maintenance of the test suite becomes prohibitively high.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 136 • EDS Internal
Regression Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 137 • EDS Internal
Regression Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 138 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 139 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 140 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 141 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 142 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 143 • EDS Internal
Maintenance Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 144 • EDS Internal
Testing throughout the Software Lifecycle
Summary
• Firstly we looked at Software Development Models:
– The V-Model – identifying the stages of testing, their relationship to the
Development stages and the type of work products involved
– Iterative Development Models, as used in RAD, RUP and Agile
developments
– Also the characteristics that make for good testing in ANY life cycle model
– And that development models must be adapted to the context of project
and product characteristics
EDS ISTQB Testing Foundation Course Version 2.3 Slide 146 • EDS Internal
Testing throughout the Software Lifecycle
Summary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 147 • EDS Internal
03-23-05
Version 2.3
Static Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 149 • EDS Internal
Static Techniques
Static Testing – a Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 150 • EDS Internal
Reviews and the Test Process
Topics
Why Review
When and What to review
What do Reviews find
Benefits of reviews
EDS ISTQB Testing Foundation Course Version 2.3 Slide 151 • EDS Internal
Reviews and the Test Process
Why Review
• Find errors early in the development • Education and training of
lifecycle (more cost effective to fix) developers and other project staff
More than 60% of the errors in a • Determine the root causes of
component can be detected using defects and measures for
informal inspections (1) preventing recurrence
• Reduce the errors in delivered systems • Test and improve standards and
procedures
• Learning experience in standards and
techniques • To assess the early stages of
development for progress and
• Team building and motivation completeness
• Improve the specification, design and
code
EDS ISTQB Testing Foundation Course Version 2.3 Slide 152 • EDS Internal
Reviews and the Test Process
Why Review - The cost of errors
100
90
80
70
60
Relative 50
Cost
Multiples 40
30
20
10
0
Reqs Des Code Unit Accept Use
EDS ISTQB Testing Foundation Course Version 2.3 Slide 153 • EDS Internal
Reviews and the Test Process
Why Review - Error/Fault Propagation
Requirement
Errors
Design
Errors
Coding
Errors
(Faults)
correct
correct
correct
EDS ISTQB Testing Foundation Course Version 2.3 Slide 154 • EDS Internal
Reviews and the Test Process
30%
25%
20%
15%
Errors
10%
5%
0%
Reqs Funct Logical Code Other
Des Des
EDS ISTQB Testing Foundation Course Version 2.3 Slide 155 • EDS Internal
Reviews and the Test Process
Why Review
EDS ISTQB Testing Foundation Course Version 2.3 Slide 156 • EDS Internal
Reviews and the Test Process
When and What to Review?
EDS ISTQB Testing Foundation Course Version 2.3 Slide 157 • EDS Internal
Reviews and the Test Process
• Typical defects that are easier to find in reviews than in dynamic testing
are:
– deviations from standards
– requirement defects
– design defects
– insufficient maintainability
– incorrect interface specifications.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 158 • EDS Internal
Reviews and the Test Process
Benefits
• Detect faults as they are introduced –i.e. early detection and correction
• Reduce the risk of error propagation
• Detect errors that Dynamic test execution unlikely to find, e.g.
requirement spec errors
• Shorten development timescales
• Reduce fault levels in delivered software
• Lower cost and shorten testing timeframes
• Lower cost over the life of the software
• Create development productivity improvements
• Reliably evaluates progress and capability (1)
• Educates and trains participants (1)
• Improve communication between project teams
EDS ISTQB Testing Foundation Course Version 2.3 Slide 159 • EDS Internal
Review Process
Topics
Informal Reviews
Formal Review Types
Formal Review Process
Formal Review Roles and Responsibilities
Other Review Types
Key Success factors
EDS ISTQB Testing Foundation Course Version 2.3 Slide 160 • EDS Internal
Review Process
Informal Review
• No Formal Review Process employed
• “Desk checking”, looking for possible problems
• The author of material checking his or her own material, possibly
with one other peer (pair programming)
• Possibly a technical lead reviewing design and code
• Usually undocumented but useful, cheap and widely used
• This technique may be applied in low risk situations
• No metrics kept, review findings are not configured items
• Weaknesses – do not find as many faults as formal reviews
EDS ISTQB Testing Foundation Course Version 2.3 Slide 161 • EDS Internal
Review Process
Formal Review Types – Walkthroughs
EDS ISTQB Testing Foundation Course Version 2.3 Slide 162 • EDS Internal
Review Process
Formal Review Types – Technical Reviews
• May be performed as Peer Reviews without management participation
• Preferably lead by a trained moderator (not the author)
• Pre-Meeting preparation is required
• Primary purpose is to:
– Discuss
– make decisions
– evaluate alternatives
– find defects
– solve technical problems and check conformance to specifications and standards
EDS ISTQB Testing Foundation Course Version 2.3 Slide 163 • EDS Internal
Review Process
Formal Review Types – Inspections
EDS ISTQB Testing Foundation Course Version 2.3 Slide 164 • EDS Internal
Formal Review Process
Planning
Kick-off
Review Overview – optional
Preparation
Review Meeting
Rework
Follow-up
Repeat Review - optional
EDS ISTQB Testing Foundation Course Version 2.3 Slide 165 • EDS Internal
Formal Review Process
Planning
EDS ISTQB Testing Foundation Course Version 2.3 Slide 166 • EDS Internal
Formal Review Process
Kick Off
EDS ISTQB Testing Foundation Course Version 2.3 Slide 167 • EDS Internal
Formal Review Process
Review Overview (Optional)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 168 • EDS Internal
Formal Review Process
Preparation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 169 • EDS Internal
Formal Review Process
Review Meeting
• The material is read to the participants by the
reader
• Defects are raised by the participants and
recorded by the recorder
• Participants may make decisions about
categorising and even handling the defects –
though usually avoid ‘solutionising’
• Deliverables may include meeting minutes
• For Inspections - Pass or fail and repeat
review decisions are usually made by the
moderator
• The preparation time and the actual time may
be recorded
EDS ISTQB Testing Foundation Course Version 2.3 Slide 170 • EDS Internal
Formal Review Process
Rework
• The author must resolve all defects found during the review by reworking
the material as recommended by the review report
• Note, the cost of rework is NOT included in the cost of reviews
EDS ISTQB Testing Foundation Course Version 2.3 Slide 171 • EDS Internal
Formal Review Process
Follow-up
• Check the corrections to the material and account for all recorded defects
• If necessary, schedule a repeat review for the corrected material
• Inform management of the status of the corrected material
• Add the error data from the review to the project statistics database –
enables process improvement!
• Complete and sign the review report and forms (Inspections)
• Ensure exit criteria met
EDS ISTQB Testing Foundation Course Version 2.3 Slide 172 • EDS Internal
Formal Review Process
Repeat Review (optional)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 173 • EDS Internal
Review Process
Formal Review Roles and Responsibilities
Moderator the person who leads, plans and runs the review
May mediate between the various points of view and is often the
person upon whom the success of the review rests
Author the writer or person with chief responsibility for the document(s)
to be reviewed
EDS ISTQB Testing Foundation Course Version 2.3 Slide 174 • EDS Internal
Review Process
Other Review Types
EDS ISTQB Testing Foundation Course Version 2.3 Slide 175 • EDS Internal
Review Process
Key Success Factors
– Each review has a clear predefined objective
– The right people are involved
– Defects found are welcomed (Authors must leave their ego
at the door!)
– Defects are expressed objectively – no cornering the author
– make it a positive experience!
– Review techniques are applied suitable to the review
– Checklists used if appropriate – focus the review effort
– Roles pre-defined – avoid duplication and increase
effectiveness
– Training is given in review techniques- especially for
Inspections
– Management buy in – schedule in review activities and
effort
– There is an emphasis on learning and process improvement
EDS ISTQB Testing Foundation Course Version 2.3 Slide 176 • EDS Internal
Static Analysis
Topics
Definition
Description
Value
Types of Defects found
Use of Tools
EDS ISTQB Testing Foundation Course Version 2.3 Slide 177 • EDS Internal
Static Analysis
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 178 • EDS Internal
Static Analysis
Description
• Objective - to find defects in software source code and software
models
EDS ISTQB Testing Foundation Course Version 2.3 Slide 179 • EDS Internal
Static Analysis
Value
• Early detection of defects prior to test execution
• Early warning about suspicious aspects of the code or design
• Calculation of metrics such as a high complexity measure
• Identification of defects not easily found by dynamic testing
• Detecting dependencies and inconsistencies in software models, such
as links
• Improved maintainability of code and design
• Prevention of defects, if lessons are learned in development
• Cost effective – problems found earlier are cheaper to fix
• Static analysis is more effective and less expensive than dynamic
testing (1)
• Static analysis is demonstrated to find 45% of expected errors before
testing actually starts
EDS ISTQB Testing Foundation Course Version 2.3 Slide 180 • EDS Internal
Static Analysis
EDS ISTQB Testing Foundation Course Version 2.3 Slide 181 • EDS Internal
Static Analysis
Types of Defects found
EDS ISTQB Testing Foundation Course Version 2.3 Slide 182 • EDS Internal
Static Analysis
Use of Tools
• Static analysis tools are typically used by developers
• Used mainly before and during Component and Component Integration
testing
• The tools check against predefined rules or programming standards
• Also by designers during software modelling
• Static analysis tools may produce a large number of warning messages
• Hence the need to use the tools effectively (or can’t see the wood for
the trees!)
• Compilers may offer some support for static analysis, including the
calculation of metrics
EDS ISTQB Testing Foundation Course Version 2.3 Slide 183 • EDS Internal
Static Techniques
Summary
• We learned that Static Testing techniques involve examining
documentation and software products without executing them
• That Static Testing covers both Reviews and Static Analysis
EDS ISTQB Testing Foundation Course Version 2.3 Slide 184 • EDS Internal
Static Techniques
Summary
• And we learned about Static Analysis
EDS ISTQB Testing Foundation Course Version 2.3 Slide 185 • EDS Internal
03-23-05
Version 2.3
EDS ISTQB Testing Foundation Course Version 2.3 Slide 187 • EDS Internal
Identifying Test Conditions and Designing
Test Cases
EDS ISTQB Testing Foundation Course Version 2.3 Slide 188 • EDS Internal
Identifying Test Conditions and Designing
Test Cases
Test Conditions
• Test Conditions are binary statements which determine a system’s fitness for purpose
• Defines what must be tested
• Sometimes referred to as a Test Item
• Grouped by Test Object or system function/process
• Test Requirement (Test basis ) documentation is analysed to determine the Test
Conditions
• Test Conditions are then cross referenced to one or more test cases for execution
• Not all Test Conditions are as important as others so each Test Condition is assigned a
risk
• Test Conditions should be linked back to their source documents from which they are
derived. This helps for two reasons:
– Impact Analysis
– Traceability
EDS ISTQB Testing Foundation Course Version 2.3 Slide 189 • EDS Internal
Identifying Test Conditions and Designing
Test Cases
Test Cases
• A Test Case defines how the system should be tested
• They typically contain
– Input values
– Execution pre conditions
– Expected results (output, changes in state etc)
– Post conditions
– Cross referenced test conditions
• Remember expected results must be defined before execution
• There can be many Test Cases developed to test a single Test Condition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 190 • EDS Internal
Expected Results
Myers - 1979
EDS ISTQB Testing Foundation Course Version 2.3 Slide 191 • EDS Internal
Identifying Test Conditions and Designing
Test Cases
Test Procedures
• The Test Procedures Specification specifies the sequence of actions for a
test, i.e. one or more Test Cases
• It is also known as a Test Script
• The Test Script can be manual or automated
• Contents of a Test Procedure are:
– Test procedure specification identifier
– Purpose
– Special requirements
– Procedure steps
EDS ISTQB Testing Foundation Course Version 2.3 Slide 192 • EDS Internal
Identifying Test Conditions and Designing
Test Cases
Test Execution Schedule
• The Test Procedure Specifications (i.e. Test Scripts) are subsequently
included in a Test Execution Schedule
• This schedule defines the order in which the test scripts are executed, when
they are to be carried out and by whom
• The Execution schedule will also need to take account of:
– Regression Tests
– Prioritisation
– And technical and logical dependencies
EDS ISTQB Testing Foundation Course Version 2.3 Slide 193 • EDS Internal
Test Conditions, Cases, Procedures and Schedule
Test Test
Procedure Execution
Sourced Documentation
Specification Schedule
Manual Test
Test Script Test
Test Test Procedure
Cases
Condition Cases or Specifications
Automated
Priority Test Script
EDS ISTQB Testing Foundation Course Version 2.3 Slide 194 • EDS Internal
Categories of Test Design Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 195 • EDS Internal
Black and White Box Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 196 • EDS Internal
Black and White Box Testing
Input Output
EDS ISTQB Testing Foundation Course Version 2.3 Slide 198 • EDS Internal
Black and White Box Testing
Input Output
EDS ISTQB Testing Foundation Course Version 2.3 Slide 199 • EDS Internal
Black, White and Experienced based
•Based on requirements
Black •From the requirements, tests are created
(Specification •Specification Models can be used for systematic test case design
Based) Techniques
•Equivalence Partitioning
•Boundary Value Analysis
•Decision Tables
•State Transition Testing
•Use Case Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 200 • EDS Internal
Black and White Box Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 201 • EDS Internal
Specification based or Black Box Techniques
Equivalence Partitioning
Boundary Value Analysis
Decision Table Testing
State Transition Testing
Use Case Testing
Other black box test techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 202 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
EDS ISTQB Testing Foundation Course Version 2.3 Slide 203 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
0 101
37 65 99
1 100
-1 19 53
48 87 1000
OUT OF OUT OF
RANGE IN RANGE RANGE
EDS ISTQB Testing Foundation Course Version 2.3 Slide 204 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
• the numbers fall into a partition where each would have the same, or
equivalent, result i.e. an Equivalence Partition (EP) or Equivalence Class
• EP says that by testing just one value we have tested the partition
(typically a mid-point value is used). It assumes that:
EDS ISTQB Testing Foundation Course Version 2.3 Slide 205 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
• in EP we must identify Valid Equivalence partitions and Invalid
Equivalence partitions where applicable (typically in range tests)
• the Valid partition is bounded by the values 1 and 100
• plus there are 2 Invalid partitions
EDS ISTQB Testing Foundation Course Version 2.3 Slide 206 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
IF Value >= 1 AND Value <= 100 THEN ….
0 101
37 65 99
1 100
-1 19 53
48 87 1000
‘VALID’ PARTITION
‘INVALID’ ‘INVALID’
PARTITION
EDS PARTITION
ISTQB Testing Foundation Course Version 2.3 Slide 207 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
• Time would be wasted by specifying test cases that covered a range of
values within each of the three partitions, unless the code was designed in
an unusual way
• There are more effective techniques that can be used to find bugs in such
circumstances (such as code inspection)
• EP can help reduce the number of tests from a list of all possible inputs to a
minimum set that would still test each partition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 208 • EDS Internal
Black Box Test Techniques
Equivalence Partitioning
• If the tester chooses the right partitions, the testing will be accurate and
efficient
• If the tester mistakenly thinks of two partitions as equivalent and they are
not, a test situation will be missed
• Or on the other hand, if the tester thinks two objects are different and they
are not, the tests will be redundant
EDS ISTQB Testing Foundation Course Version 2.3 Slide 209 • EDS Internal
Black Box Test Techniques
• BVA operates on the basis that experience shows us that errors are most
likely to exist at the boundaries between partitions and in doing so
incorporates a degree of negative testing into the test design
• BVA Test cases are designed to exercise the software on and at either side
of boundary values
EDS ISTQB Testing Foundation Course Version 2.3 Slide 210 • EDS Internal
Black Box Test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 211 • EDS Internal
Black Box Test Techniques
• find the boundary and then test one value above and below it
• ALWAYS results in two test cases per boundary for valid inputs and
three tests cases per boundary for all inputs
• inputs should be in the smallest significant values for the boundary
(e.g. Boundary of ‘a > 10.0’ should result in test values of 10.0,
10.1 & 10.2)
• only applicable for numeric (and date) fields
EDS ISTQB Testing Foundation Course Version 2.3 Slide 212 • EDS Internal
Black Box Test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 213 • EDS Internal
Black Box Test Techniques
Decision Table Structure
Response 1 Y Y N
Output /
Response Response 2 Y N Y
Response 3 N Y N
Each column of the table corresponds to a business rule that defines a unique
combination of conditions that result in the execution of the actions associated
with that rule
EDS ISTQB Testing Foundation Course Version 2.3 Slide 214 • EDS Internal
Black Box Test Techniques
Decision Table Example
Test 1 Test 2 Test 3
> 55 yrs old F T T
Smoker F T F
Exercises 3 times a week + T F T
History of Heart Attacks F T F
Insure Y N Y
Offer 10% Discount N N Y
Offer 30% Discount Y N N
Kevin is 62 year old non smoker who swims twice a week and plays tennis. He
has no history of heart attacks in his family
EDS ISTQB Testing Foundation Course Version 2.3 Slide 215 • EDS Internal
Black Box Test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 216 • EDS Internal
Black Box Test Techniques
Transition Between
Event/Action etc start and end states
End State
EDS ISTQB Testing Foundation Course Version 2.3 Slide 217 • EDS Internal
Black Box Test Techniques
State Transition Example Simplified Car Gears
Change Down/
Move Back
Neutral Reverse
Change Up/
Change Up/ Change Down/ Accelerate
Accelerate Decelerate
1st Gear
Change Up/ Change Down/
Accelerate Decelerate
2nd Gear
Change Up/ Change Down/
Accelerate Decelerate
3rd Gear
EDS ISTQB Testing Foundation Course Version 2.3 Slide 218 • EDS Internal
Black Box Test Techniques
State Transition - Switch Coverage
EDS ISTQB Testing Foundation Course Version 2.3 Slide 219 • EDS Internal
Black Box Test Techniques
State Transition - State Table
• While Switch testing helps determine the valid tests, we also need to look
for the invalid tests.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 220 • EDS Internal
Black Box Test Techniques
State Transition – Another example
for a Theatre Show reservation
Request Choose Reserve
Show Show Show
Options
Show
Show Options
Show selected Reservation
provided
Made
Pay for
Change Show
Mind/
Cancel
Return to
reservation
Options
Show
Reservation
Paid For
Cancelled Issue
Cancel reservation/
Reservation Issue Refund Ticket
Ticket
Cancel reservation
(return ticket)/Issue Received
Refund
EDS ISTQB Testing Foundation Course Version 2.3 Slide 221 • EDS Internal
Black Box Test Techniques
Current Event/ Event/ Next Event/ Next Event/ Next Event/ Next Event/ Next
State Next State State State State State State
A B C D E F
SS 1
1 2
2 1 3
3 4
4 ES
ES
EDS ISTQB Testing Foundation Course Version 2.3 Slide 222 • EDS Internal
Black Box Test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 223 • EDS Internal
Other Black Box Test Techniques
• Syntax testing
— test cases are prepared to exercise the rule governing the format of
data in a system (e.g. a Zip or Postal Code, a telephone number)
• Random testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 224 • EDS Internal
Structure Based or White Box Test Techniques
Statement Testing
Decision Testing
Assessing Completeness (Coverage)
Other White Box test techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 225 • EDS Internal
White Box Test Techniques
Statement Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 226 • EDS Internal
White Box Test Techniques
Statement Testing
1 Control
Example 1 Flow Graph
2
1. Read vehicle
3
2. Read colour
4
3. If vehicle = ‘Car’ Then
4. If colour = ‘Red’ Then 5
5. Print “Fast”
6
6. End If
7. End If 7
EDS ISTQB Testing Foundation Course Version 2.3 Slide 227 • EDS Internal
White Box Test Techniques
Statement Testing 1
Example 2 2
1. Read A 3
2. If A > 40 Then
4
3. A=A*2
5
4. End If
5. If A > 100 Then 6
6. A = A – 10
7
7. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 228 • EDS Internal
White Box Test Techniques
Statement Testing 1
Example 3
1. Read bread 2
2. Read filling
3. If bread = ‘Roll’ Then 3/9
4. If filling = ‘Tuna’ Then
4/6
5. Price = 1.50
6. Else 7 5
7. Price = 1.00 10
8. End If 8
9. Else
10. Price = 0.75 11
11. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 229 • EDS Internal
White Box Test Techniques
Decision Testing
– Aim is to demonstrate that all Decisions have been run at least once
– Coverage measurement is:
EDS ISTQB Testing Foundation Course Version 2.3 Slide 230 • EDS Internal
White Box Test Techniques
Decision Testing 1
Example 1 2
1. Read vehicle 3
2. Read colour 4
3. If vehicle = ‘Car’ Then
5
4. If colour = ‘Red’ Then
5. Print “Fast” 6
6. End If
7
7. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 231 • EDS Internal
White Box Test Techniques
Decision Testing 1
Example 2 2
1. Read A
3
2. If A > 40 Then
4
3. A=A*2
4. End If 5
5. If A > 100 Then
6
6. A = A – 10
7. End IfC 7
EDS ISTQB Testing Foundation Course Version 2.3 Slide 232 • EDS Internal
White Box Test Techniques
Decision Testing 1
Example 3
1. Read bread
2
2. Read filling
3. If bread = ‘Roll’ Then 3/9
4. If filling = ‘Tuna’ Then
4/6
5. Price = 1.50
6. Else
7 5
7. Price = 1.00
10
8. End If 8
9. Else
10. Price = 0.75 11
11. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 233 • EDS Internal
White Box Test Techniques
Statement and Decision Testing
The pseudo-code can be expressed in Flow-chart format
1. Read A
2. If A > 40 Then
3. A=A*2
4. End If
5. If A > 100 Then
6. A = A – 10
7. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 234 • EDS Internal
White Box Test Techniques
Assessing Completeness (Coverage)
1. Read bread
2. Read filling We already know:
Statement Coverage = 3
3. If bread = ‘Roll’ Then
Decision Coverage = 3
4. If filling = ‘Tuna’ Then
Number of executable Statements = 7
5. Price = 1.50
Number of Branches = 4 (T and F of
6. Else each IF)
7. Price = 1.00
8. End If
9. Else
10. Price = 0.75
11. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 235 • EDS Internal
White Box Test Techniques
Assessing Completeness (Coverage)
1. Read bread
2. Read filling • Based on the following test set:
Roll Tuna
4. If filling = ‘Tuna’ Then
Sandwich Ham
5. Price = 1.50
6. Else • What is the test Statement
Coverage and Decision Coverage?
7. Price = 1.00
8. End If
9. Else
10. Price = 0.75
11. End If
EDS ISTQB Testing Foundation Course Version 2.3 Slide 236 • EDS Internal
White Box Test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 237 • EDS Internal
Experience Based Techniques
Definition
Error Guessing
Exploratory Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 238 • EDS Internal
Experienced Based Techniques
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 239 • EDS Internal
Experience Based Techniques
Definition
EDS ISTQB Testing Foundation Course Version 2.3 Slide 240 • EDS Internal
Experience Based Techniques
Error Guessing
• Using experience to postulate errors
EDS ISTQB Testing Foundation Course Version 2.3 Slide 241 • EDS Internal
Experience Based Techniques
Error Guessing
• Error Guessing tests may include
EDS ISTQB Testing Foundation Course Version 2.3 Slide 242 • EDS Internal
Experience Based Techniques
Exploratory testing
• Exploratory testing is a concurrent process where
– Test design, execution and logging happen simultaneously
– Testing is often not recorded
– Makes use of experience, heuristics and test patterns
– Testing is based on a test charter that may include
• Scope of the testing (in and out)
• Why? - what is the focus of your testing
• A brief description of how tests will be performed
• Expected problems
– Is carried out in time boxed intervals
• More structured than Error guessing
Exploratory
Risk Analysis Charter Debriefing
Sessions
Notes
EDS ISTQB Testing Foundation Course Version 2.3 Slide 243 • EDS Internal
Choosing test Techniques
EDS ISTQB Testing Foundation Course Version 2.3 Slide 244 • EDS Internal
Test Design Techniques - Summary
• We learned about
– Identifying Test Conditions
– Designing Test Cases from the Test Conditions
– Creating Test Procedure Specifications to sequence our Test Cases
– Creating Test Execution schedules to define the order in which the test scripts
are executed, when they are to be carried out and by whom
– The importance of traceability to requirements and specification of expected
results
• We learned about the difference between Black and White Box testing
– White Box (Structure-based) Testing is based upon the structure of the program
code
– Black Box (Specification Based) Testing is without reference the internal working
of the program code
– The reasons why both are useful
EDS ISTQB Testing Foundation Course Version 2.3 Slide 245 • EDS Internal
Test Design Techniques - Summary
– Statement Testing
– Decision Testing
• For all Black and White box techniques we learned why they are of use
and for which test levels they are typically applied
EDS ISTQB Testing Foundation Course Version 2.3 Slide 246 • EDS Internal
03-23-05
Version 2.3
Test Management
Test Organisation
Test Planning and Estimation
Test Progress Monitoring and Control
Configuration Management
Risk and Testing
Incident Management
Summary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 248 • EDS Internal
Test Organisation
Test Independence
Testing Roles Within the Team
The Test Leader
The Tester
EDS ISTQB Testing Foundation Course Version 2.3 Slide 249 • EDS Internal
Test Independence
Levels of Independence
• More effective for someone other than the developer to test the system
– More impartial
– No preconceived ideas about what requires testing
– No bias or emotional attachment
EDS ISTQB Testing Foundation Course Version 2.3 Slide 250 • EDS Internal
Test Independence
• Most test projects require multiple levels of testing where some of the
testing is carried out by independent testers.
Acceptance
Testing
System Independent
Integration
Testing Testers
System Testing
Developers
Component Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 251 • EDS Internal
Test Independence
Benefits
• Independent testers see other and different defects, and are unbiased
• An independent tester can verify assumptions people made during
specification and implementation of the system
• Usually a Cost saving
– Better skills = more effective testing and fewer defects getting into production
– For Third Party test outsourcing, ‘better to rent than to own’
Drawbacks
• Isolation from the development team (if treated as totally independent).
• Independent testers may be the bottleneck as the last checkpoint
• Developers lose a sense of responsibility for quality
• Can be a greater cost – need to consider viability
• For Third Party test outsourcing, the project carries the risk
EDS ISTQB Testing Foundation Course Version 2.3 Slide 252 • EDS Internal
Testing Roles within the Team
EDS ISTQB Testing Foundation Course Version 2.3 Slide 253 • EDS Internal
The Test Leader
EDS ISTQB Testing Foundation Course Version 2.3 Slide 254 • EDS Internal
The Test Leader
EDS ISTQB Testing Foundation Course Version 2.3 Slide 255 • EDS Internal
The Tester
EDS ISTQB Testing Foundation Course Version 2.3 Slide 256 • EDS Internal
The Tester
EDS ISTQB Testing Foundation Course Version 2.3 Slide 257 • EDS Internal
Test Planning and Estimation
Test Planning
Test Planning Activities
Exit Criteria
Test Estimation
Test Approaches
EDS ISTQB Testing Foundation Course Version 2.3 Slide 258 • EDS Internal
Test Planning
• All projects require a set of plans and strategies which define how the
testing will be conducted.
• There are number of levels at which these are defined:
EDS ISTQB Testing Foundation Course Version 2.3 Slide 259 • EDS Internal
Test Planning
EDS ISTQB Testing Foundation Course Version 2.3 Slide 260 • EDS Internal
Test Planning
Test Plan Contents (IEEE 829)
1. Test Plan Identifier
2. Introduction
3. Test Items
4. Features to be Tested
5. Features not to be Tested
6. Approach
7. Item Pass/Fail Criteria
8. Suspension Criteria and Resumption Requirements
9. Test Deliverables
10. Testing Tasks
11. Environmental Needs
12. Staffing and Training Needs
13. Responsibilities
14. Schedule
15. Planning Risks and Contingencies
16. Approvals
EDS ISTQB Testing Foundation Course Version 2.3 Slide 261 • EDS Internal
Test Planning Activities
• Approach - Defining the overall approach of testing (the test strategy), including the
definition of the test levels and entry and exit criteria.
• Integrating and coordinating the testing activities into the software life cycle
activities: acquisition, supply, development, operation and maintenance.
• Making decisions about:
– what to test
– who – i.e. what roles will perform the test activities
– when and how the test activities should be done and when they should be stopped (exit
criteria – see next slides)
– how the test results will be evaluated
• Assigning resources for the different tasks defined.
• Testware definition- Defining the amount, level of detail, structure and templates
for the test documentation.
• Selecting metrics for monitoring and controlling test preparation and execution,
defect resolution and risk issues.
• Process - Setting the level of detail for test procedures in order to provide enough
information to support reproducible test preparation and execution.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 262 • EDS Internal
Exit Criteria
The business
Run out of tells you it went
time? live last night!
Boss says
Run out of stop?
budget?
EDS ISTQB Testing Foundation Course Version 2.3 Slide 263 • EDS Internal
Exit Criteria
EDS ISTQB Testing Foundation Course Version 2.3 Slide 264 • EDS Internal
Test Estimation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 265 • EDS Internal
Test Estimation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 266 • EDS Internal
Test Estimation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 267 • EDS Internal
Test Estimation
Estimation - Factors
• The testing effort can depend on:
– Characteristics of the product:
• the quality of the specification
• the size of the product
• the complexity of the problem domain
– Characteristics of the development process:
• the stability of the organization
• tools used
• test process
• skills of the people involved
• time pressure
– The outcome of testing
• the number of defects
• the amount of rework required.
• Once estimation is complete the resource requirements and projects
schedules can be finalised
EDS ISTQB Testing Foundation Course Version 2.3 Slide 268 • EDS Internal
Test Estimation
Black - 2002
EDS ISTQB Testing Foundation Course Version 2.3 Slide 269 • EDS Internal
Test Approaches
• One method of classifying the way testing is done is by looking at when the
bulk of testing is carried out
Preventative Reactive
EDS ISTQB Testing Foundation Course Version 2.3 Slide 270 • EDS Internal
Test Approaches
More Approaches
• Analytical approaches, such as risk-based testing where testing is directed to
areas of greatest risk.
• Model-based approaches, such as stochastic testing using statistical information
about failure rates (such as reliability growth models) or usage (such as operational
profiles).
• Methodical approaches, such as failure based (including error guessing and fault-
attacks), check-list based, and quality characteristic based.
• Process- or standard-compliant approaches, such as those specified by industry-
specific standards or the various agile methodologies.
• Dynamic and heuristic approaches, such as exploratory testing where testing is
more reactive to events than pre-planned, and where execution and evaluation are
concurrent tasks.
• Consultative approaches, such as those where test coverage is driven primarily by
the advice and guidance of technology and/or business domain experts outside the
test team.
• Regression-averse approaches, such as those that include reuse of existing test
material, extensive automation of functional regression tests and standard test suites.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 271 • EDS Internal
Test Approaches
Approaches Combined
EDS ISTQB Testing Foundation Course Version 2.3 Slide 272 • EDS Internal
Test Approaches
EDS ISTQB Testing Foundation Course Version 2.3 Slide 273 • EDS Internal
Test Progress Monitoring and Control
EDS ISTQB Testing Foundation Course Version 2.3 Slide 274 • EDS Internal
Test Progress Monitoring
• Need to know the status of the testing project at any given point in time
• Need to provide visibility on the status of testing to other stake holders
• Need to be able to measure your testing against your defined exit criteria
• Need to be able to assess progress against
– Planned schedule
– Measure how you are tracking against your defined budget
EDS ISTQB Testing Foundation Course Version 2.3 Slide 275 • EDS Internal
Test Progress Monitoring
EDS ISTQB Testing Foundation Course Version 2.3 Slide 276 • EDS Internal
Test Reporting
EDS ISTQB Testing Foundation Course Version 2.3 Slide 277 • EDS Internal
Test Reporting
EDS ISTQB Testing Foundation Course Version 2.3 Slide 278 • EDS Internal
Reporting and Interpreting Metrics
• Metrics should be collected during and at the end of a test level in order to
assess:
– The adequacy of the test objectives for that test level.
– The adequacy of the test approaches taken.
– The effectiveness of the testing with respect to its objectives.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 279 • EDS Internal
Reporting and Interpreting Metrics
Interpreting Metrics – testing progress
Not Tested • On the face of it things look good
• Can we go live?
Failed • What else would we need to know?
• However…
• What are the risks of the parts that
have failed
• Does this chart account for all the
testing scheduled – is there more to
come?
Pass
EDS ISTQB Testing Foundation Course Version 2.3 Slide 280 • EDS Internal
Reporting and Interpreting Metrics
Interpreting Metrics – Defect reporting
160
140
Gap between = number of
120 Incidents still outstanding
100
No. Defects
found
80
fixed
60
40
20
0
d1 d2 d3 d4 d5 d6
Time
EDS ISTQB Testing Foundation Course Version 2.3 Slide 281 • EDS Internal
Reporting and Interpreting Metrics
EDS ISTQB Testing Foundation Course Version 2.3 Slide 282 • EDS Internal
Test Control
EDS ISTQB Testing Foundation Course Version 2.3 Slide 283 • EDS Internal
Configuration Management
Symptoms of Poor CM
Configuration Items and their control
EDS ISTQB Testing Foundation Course Version 2.3 Slide 284 • EDS Internal
Symptoms of poor CM
EDS ISTQB Testing Foundation Course Version 2.3 Slide 285 • EDS Internal
Configuration Items and their control
EDS ISTQB Testing Foundation Course Version 2.3 Slide 286 • EDS Internal
Configuration Items and their control
EDS ISTQB Testing Foundation Course Version 2.3 Slide 287 • EDS Internal
Risk and Testing
EDS ISTQB Testing Foundation Course Version 2.3 Slide 288 • EDS Internal
Testing and Risk
EDS ISTQB Testing Foundation Course Version 2.3 Slide 289 • EDS Internal
Project Risk
• Project Risk: A risk related to management and control of the (test) project.
• Supplier Issues
– Contractual Issues
– Third party goes in liquidation or fails to deliver
• Organisational Issues
– Skills and Staff shortages
– Training and support issues
– Communication/Political Issues, e.g. between testers and other project teams
• Technical
– No or poor requirements
– Quality of the design or code
– Architectural solution under question
EDS ISTQB Testing Foundation Course Version 2.3 Slide 290 • EDS Internal
Product Risk
EDS ISTQB Testing Foundation Course Version 2.3 Slide 291 • EDS Internal
Risk Based Testing in Practice
• Risks can help decide where we should start testing or where we may need to more
testing
• Risks also help us analyse our current state and through test monitoring we can
determine if a system is ready to be implemented
• Risks can also drive the number of test levels and determine the techniques to use
EDS ISTQB Testing Foundation Course Version 2.3 Slide 292 • EDS Internal
Risk Based Testing in Practice
Weymouth
2006
EDS ISTQB Testing Foundation Course Version 2.3 Slide 293 • EDS Internal
Risk Based Testing in Practice
• Testing can support the identification of new risks – identified during test
planning
• Testing is used to reduce the risk of an adverse effect occurring, or to
reduce its impact
• Testing provides feedback about the residual risk- through measuring the
effectiveness of critical defect removal and contingency plans
• In analysing, recording and managing the Product and Project risks the Test
Manager is following well defined project management principles
• In a risk-based approach we can not only determine our test prioritisation
but also the test techniques to use
EDS ISTQB Testing Foundation Course Version 2.3 Slide 294 • EDS Internal
Measuring Risk
Likelihood
Low
Low Impact High
EDS ISTQB Testing Foundation Course Version 2.3 Slide 295 • EDS Internal
Risk Based Testing in Practice
C A
Won’t Test Should Test
Informal Test specification Formal Test Specification
Error Guessing Statement Coverage
100%
D B
Impact Impact
EDS ISTQB Testing Foundation Course Version 2.3 Slide 296 • EDS Internal
Incident Management
Definition
Basic principles
Benefits
Attributes of an Incident
Tracking and Analysis
Writing Good Incident Reports
EDS ISTQB Testing Foundation Course Version 2.3 Slide 297 • EDS Internal
Definition
=
expected actual!
EDS ISTQB Testing Foundation Course Version 2.3 Slide 298 • EDS Internal
Basic Principals
EDS ISTQB Testing Foundation Course Version 2.3 Slide 299 • EDS Internal
Benefits
• Incidents:
– Provide developers and other parties with feedback about the problem to enable
identification, isolation and correction as necessary
– Provide test leaders a means of tracking the quality of the system under test
and the progress of the testing
– Provide ideas for test process improvement
EDS ISTQB Testing Foundation Course Version 2.3 Slide 300 • EDS Internal
Attributes of an Incident
EDS ISTQB Testing Foundation Course Version 2.3 Slide 301 • EDS Internal
Attributes of an Incident
EDS ISTQB Testing Foundation Course Version 2.3 Slide 302 • EDS Internal
Tracking and Analysis
EDS ISTQB Testing Foundation Course Version 2.3 Slide 303 • EDS Internal
Tracking and Analysis
EDS ISTQB Testing Foundation Course Version 2.3 Slide 304 • EDS Internal
Writing Good Incident Reports
EDS ISTQB Testing Foundation Course Version 2.3 Slide 305 • EDS Internal
Writing Good Incident Reports
• Summary
– one or two lines which provide an overview of the incident and its severity and
impact. Be sharp and to the point.
• Steps to reproduce
– provide the exact steps that were undertaken to create the incident. Be as
concise as possible, but make sure you add EVERY step
– get these steps right makes it easier for the developers to reproduce. – it
reduces the “it works on my machine” phenomenon
• Isolation
– is the incident repeatable, what particular factors effect the ability to reproduce
the incident, For example – “I observed the error on the following platforms IE5,
NS7”
EDS ISTQB Testing Foundation Course Version 2.3 Slide 306 • EDS Internal
Writing Good Incident Reports
Bad Example
Summary
There were a number or errors on the add customer screen
Steps to reproduce
1. Opened the add customer screen
2. Entered a new customer
3. Pressed add
4. Got error message
Isolation
I tried on a few different branches and it worked on most of them
EDS ISTQB Testing Foundation Course Version 2.3 Slide 307 • EDS Internal
Writing Good Incident Reports
Good Example
Summary
Error “cannot find object” (see attached screen shot) message was displayed when
trying to add a new customer to the system using screen ADD_CUST.
Steps to reproduce
1.Opened the add customer screen using the menu
2.Entered a new customer (details are attached in spreadsheet)
3.Selected customer as “corporate”
4.Added to branch “Littleton”
5.Pressed add
6.Got error message “cannot find object”
Isolation
I tried on a few different branches and the system worked without issue when the
branch was classified as open. The Incident only occurred when the branch was
classified as closed
EDS ISTQB Testing Foundation Course Version 2.3 Slide 308 • EDS Internal
Test Management - Summary
We learned about the Test organization
• The importance of independent testing
• The types of Independent test organisations
• The benefits and drawbacks of independent testing within an organization
• The different team members to be considered for the creation of a test team
• The tasks of typical Test Leader and Tester
EDS ISTQB Testing Foundation Course Version 2.3 Slide 309 • EDS Internal
Test Management - Summary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 310 • EDS Internal
Test Management - Summary
EDS ISTQB Testing Foundation Course Version 2.3 Slide 311 • EDS Internal
03-23-05
Version 2.3
EDS ISTQB Testing Foundation Course Version 2.3 Slide 313 • EDS Internal
Types of Test Tools
EDS ISTQB Testing Foundation Course Version 2.3 Slide 314 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 315 • EDS Internal
Types of Test Tool
– For example, some tools that measure the performance of a piece of code may insert
code to count or time instructions – though very detailed information can be obtained,
the timings will be affected simply because of the extra code
• Some tools offer greater support to developers rather than testers e.g., Static
Analysers are more commonly used by developers
• Some tools offer greater support for different parts of the software development
lifecycle (e.g. Unit Testing, System Testing)
• Computer Aided Software Test Tools (CAST Tools) is a common term used in
testing circles
EDS ISTQB Testing Foundation Course Version 2.3 Slide 316 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 317 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 318 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 319 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 320 • EDS Internal
Types of Test Tool
• Test Teams should review requirements early in the lifecycle to check for
consistency, testability and to allow test cases to be constructed
EDS ISTQB Testing Foundation Course Version 2.3 Slide 321 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 322 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 323 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 324 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 325 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 326 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 327 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 328 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 329 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 330 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 331 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 332 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 333 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 334 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 335 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 336 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 337 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 338 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 339 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 340 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 341 • EDS Internal
Types of Test Tool
EDS ISTQB Testing Foundation Course Version 2.3 Slide 342 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 343 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 345 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 346 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 347 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 348 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 349 • EDS Internal
Effective Use of Tools – benefits and risks
EDS ISTQB Testing Foundation Course Version 2.3 Slide 350 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 351 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 352 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 353 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 354 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 355 • EDS Internal
Introducing a Tool into an Organisation
• Adapt processes
– Processes may benefit from changes because of the tool
– For example, when and how regression testing is done (with automation), how test
cases are developed and recorded, etc.
• Training
– To avoid tools becoming shelfware new users will need local training and support
– Some users will be easily deterred by new tools
EDS ISTQB Testing Foundation Course Version 2.3 Slide 356 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 357 • EDS Internal
Introducing a Tool into an Organisation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 358 • EDS Internal
EDS Application Engineering Toolkit (AET)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 359 • EDS Internal
Collateral on Tools
EDS ISTQB Testing Foundation Course Version 2.3 Slide 360 • EDS Internal
Tool Support for Testing
Summary (1)
EDS ISTQB Testing Foundation Course Version 2.3 Slide 361 • EDS Internal
Tool Support for Testing
Summary (2)
Test management tools Test management Requirements management
Incident management Configuration management
Static testing tools Static analysis Review process support
Modelling
Test specification tools Test design Test data preparation
EDS ISTQB Testing Foundation Course Version 2.3 Slide 362 • EDS Internal
Tool Support for Testing
Summary (3)
• Then we looked at the effective use of tools:
– Benefits of tools:
• Save time, thorough testing, reduce repetitive tasks, etc.
– And the risks:
• Underestimating time and effort, Over-reliance, etc.
– Special considerations for:
• Test execution tools, performance tools, static analysis tools and
test management tools
• And finally, we looked at how to introduce a tool:
– Main principles (evaluation, assessments, etc.)
– Pilot project objectives
– Success factors
EDS ISTQB Testing Foundation Course Version 2.3 Slide 363 • EDS Internal
Index
The following slides provides a quick reference guide to some of the key terms used in the course, to aid revision. Each term is hyperlinked and has slide numbers plus associated ISQTB Syllabus section numbers. Remember to use the Glossary of terms for exact definitions.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 364 • EDS Internal
Index
Term Slide(s) Topic Syllabus reference
Exploratory Testing 241 Test Design Techniques 4.5
Failure 12 Fundamentals of Testing 1.1.2
Fault 10 Fundamentals of Testing 1.1.2
Formal Review Process 166 Static Techniques 3.2.1
Functional Testing 131 Testing Throughout the S/W Lifecycle 2.3.1
Fundamental Test process 44 Fundamentals of Testing 1.4
General Principles of Testing 34 Fundamentals of Testing 1.3
Incident Management 295 Test Management 5.6
Independent Testing 248 Test Management 5.1.1
Informal Review 162 Static Techniques 3.2.3
Inspection 165 Static Techniques 3.2.3
Maintenance Testing 140 Testing Throughout the S/W Lifecycle 2.4
Non- Functional Testing 132 Testing Throughout the S/W Lifecycle 2.3.2
Product Risk 289 Test Management 5.5.2
Project Risk 288 Testing Throughout the S/W Lifecycle 5.5.1
Regression Testing 136 Testing Throughout the S/W Lifecycle 2.3.4
Re-testing (Confirmation) 135 Testing Throughout the S/W Lifecycle 2.3.4
EDS ISTQB Testing Foundation Course Version 2.3 Slide 365 • EDS Internal
Index
Term Slide(s) Topic Syllabus reference
EDS ISTQB Testing Foundation Course Version 2.3 Slide 366 • EDS Internal
Index
Term Slide(s) Topic Syllabus reference
EDS ISTQB Testing Foundation Course Version 2.3 Slide 367 • EDS Internal
Statement of Confidentiality
EDS is a registered mark and the EDS logo is a trademark of Electronic Data Systems
Corporation.
EDS is an equal opportunity employer and values the diversity of its people.
Copyright 2006 Electronic Data Systems Corporation. All rights reserved.
EDS ISTQB Testing Foundation Course Version 2.3 Slide 368 • EDS Internal
30
Version
Sept 2005
2.3
Presentation and Course owner Paul Weymouth, UKIA Testing ADU Paul.Weymouth@eds.com
Presentation and Course contributors:
•Paul Weymouth, Testing Architect UKIA Testing ADU
•Mark Otter, Senior Test Consultant Australia South ADU
•Dave Broughton, Testing Architect UKIA Testing ADU
EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS is an equal opportunity employer
and values the diversity of its people. © 2005 Electronic Data Systems Corporation. All rights reserved.