The document discusses dynamic testing techniques, including:
- Black box and white box testing approaches
- Common black box techniques like equivalence partitioning, boundary value analysis, and state transition testing
- White box techniques like control flow and data flow testing
- The advantages of using systematic techniques to make testing more effective and measurable.
The document discusses dynamic testing techniques, including:
- Black box and white box testing approaches
- Common black box techniques like equivalence partitioning, boundary value analysis, and state transition testing
- White box techniques like control flow and data flow testing
- The advantages of using systematic techniques to make testing more effective and measurable.
The document discusses dynamic testing techniques, including:
- Black box and white box testing approaches
- Common black box techniques like equivalence partitioning, boundary value analysis, and state transition testing
- White box techniques like control flow and data flow testing
- The advantages of using systematic techniques to make testing more effective and measurable.
The document discusses dynamic testing techniques, including:
- Black box and white box testing approaches
- Common black box techniques like equivalence partitioning, boundary value analysis, and state transition testing
- White box techniques like control flow and data flow testing
- The advantages of using systematic techniques to make testing more effective and measurable.
Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1/ 54
Software Testing
ISTQB / ISEB Foundation Exam Practice
1 Principles
2 Lifecycle
4 Dynamic test 5 Management techniques
Chapter 4
3 Static testing 6 Tools
Dynamic Testing Techniques
ISTQB / ISEB Foundation Exam Practice
Dynamic Testing Techniques
Contents What is a testing technique? Black and White box testing Black box test techniques White box test techniques Error Guessing
Why dynamic test techniques?
Exhaustive testing (use of all possible inputs
and conditions) is impractical - must use a subset of all possible test cases - must have high probability of detecting faults Need thought processes that help us select test cases more intelligently - test case design techniques are such thought processes
What is a testing technique?
a procedure for selecting or designing tests
based on a structural or functional model of the software successful at finding faults 'best' practice a way of deriving good test cases a way of objectively measuring a test effort Testing Testing should should be be rigorous, rigorous, thorough thorough and and systematic systematic
Advantages of techniques
Different people: similar probability find faults
- gain some independence of thought Effective testing: find more faults - focus attention on specific types of fault - know you're testing the right thing Efficient testing: find faults with less effort - avoid duplication - systematic techniques are measurable Using Using techniques techniques makes makes testing testing much much more more effective effective
Measurement
Objective assessment of thoroughness of
testing (with respect to use of each technique) - useful for comparison of one test effort to another E.g. Project A 60% Equivalence partitions 50% Boundaries 75% Branches
Project B 40% Equivalence partitions 45% Boundaries 60% Branches
ISTQB / ISEB Foundation Exam Practice
Dynamic Testing Techniques
Contents What is a testing technique? Black and White box testing Black box test techniques White box test techniques Error Guessing
Three types of systematic technique
Static (non-execution) examination of documentation, source code listings, etc. Functional (Black Box) based on behaviour / functionality of software Structural (White Box) based on structure of software
Some test techniques
Dynamic Dynamic
Static Static etc.
Reviews Inspection Walkthroughs
Structural Structural
Desk-checking
Symbolic Execution
Non-functional Non-functional
Functional Functional etc.
etc. Control Flow
Data Flow
etc.
Behavioural Behavioural
Static Analysis
Performance etc.
Statement Branch/Decision
Definition -Use
Branch Condition
Equivalence Partitioning
Usability
Arcs LCSAJ
Branch Condition Combination
Boundary Value Analysis Cause-Effect Graphing Random
State Transition
Black box versus white box?
Black box appropriate at all levels but dominates higher levels of testing White box used predominately at lower levels to compliment black box
Acceptance Acceptance
System System
Integration Integration
Component Component
ISTQB / ISEB Foundation Exam Practice
Dynamic Testing Techniques
Contents What is a testing technique? Black and White box testing Black box test techniques White box test techniques Error Guessing
Black Box test design and
measurement techniques
Techniques defined in BS 7925-2
- Equivalence partitioning Also a measurement - Boundary value analysis technique? - State transition testing = Yes = No - Cause-effect graphing - Syntax testing - Random testing Also defines how to specify other techniques
Equivalence partitioning (EP)
- divide (partition) the inputs, outputs, etc. into areas
which are the same (equivalent) - assumption: if one value works, all will work - one from each partition better than all from one invalid
valid 0
100
invalid 101
Boundary value analysis (BVA)
- faults tend to lurk near boundaries
- good place to look for faults - test values on both sides of boundaries invalid
valid 0
invalid 100 101
Example: Loan application Customer Name Account number Loan amount requested Term of loan Monthly repayment Term: Repayment: Interest rate: Total paid back:
2-64 chars. 6 digits, 1st non-zero 500 to 9000 1 to 30 years Minimum 10
If you do boundaries only, you have covered all the
partitions as well - technically correct and may be OK if everything works correctly! - if the test fails, is the whole partition wrong, or is a boundary in the wrong place - have to test mid-partition anyway - testing only extremes may not give confidence for typical use scenarios (especially for users) - boundaries may be harder (more costly) to set up
Test objectives? Condition
Valid Tag Invalid Tag Valid Partition Partition Boundary
Tag Invalid Boundary
Tag
For a thorough approach: VP, IP, VB, IB
Under time pressure, depends on your test objective - minimal user-confidence: VP only? - maximum fault finding: VB first (plus IB?)
Decision tables
explore combinations of inputs, situations or
events, it is very easy to overlook specific combinations of input start by expressing the input conditions of interest so that they are either TRUE or FALSE record found file exists code valid
policy expired account in credit due date > current date
Example: student access
A university computer system allows students an allocation of disc space depending on their projects. If they have used all their allotted space, they are only allowed restricted access, i.e. to delete files, not to create them. This is assuming they have logged on with a valid username and password. What What are are the the input input and and output output conditions? conditions?
List the input and output conditions
list the input conditions in the first column of the table list the output conditions under the input conditions
combination of input conditions. each entry in the table may be either T for true, F for false.
Input Conditions Valid username T T T T F F F Valid password T T F F T T F Account in credit T F T F T F T
F F F
Rationalise input combinations
some combinations may be impossible or not
of interest some combinations may be equivalent use a hyphen to denote dont care
Input Conditions Valid username F Valid password Account in credit -
T T T F T T - F T
Complete the table
determine the expected output conditions for
each combination of input conditions
Input Conditions Valid username F Valid password Account in credit Output Conditions Login accepted F Restricted access -
T T T F T T - F T F -
T T T F
Determine test case groups
each column is at least one test case
Input Conditions Valid username F Valid password Account in credit Output Conditions Login accepted F Restricted access Tags A
T T T F T T - F T F T T - T F B C D
Design test cases
usually one test case for each column but can
be none or several
Test Description 1 2 3 4 5
Username BrbU Username usernametoolong Username BobU Password abcd Valid user, no disc space Valid user with disc space
Expected Outcome
Tag
Invalid username Invalid username
A A
Invalid password
Restricted access
Unrestricted access
Rationalising outputs
if outputs or effects are mutually exclusive,
I.e. T occurs in only one place in each column, we can combine them for example: X
Y Z
F F
T F
F T
is equivalent to: Output
Rationalising dangers
rationalising is based on assumptions
assumptions may be wrong! assumptions should be stated assumptions may change over time be aware of the dangers - filling in the full table may find errors which will be missed if you rationalise - it is possible to rationalise too far
Extending decision tables
Entries can be more than just true or false
- completing table needs to be done carefully - rationalising becomes more important E.g.
Code = 1, 2, or 3 1 1 1 1 2 2 2 2 3 3 3 3 Exp.date < now T T F F T T F F T T F F Class A product T F T F T F T F T F T F
Decision Tables in relation to EP and
BVA Input value
Output value
FALSE TRUE
ISTQB / ISEB Foundation Exam Practice
Dynamic Testing Techniques
Contents What is a testing technique? Black and White box testing Black box test techniques White box test techniques Error Guessing
White Box test design and
measurement techniques
Techniques defined in BS 7925-2
- Statement testing Also a measurement technique? - Branch / Decision testing = Yes - Data flow testing = No - Branch condition testing - Branch condition combination testing - Modified condition decision testing - LCSAJ testing Also defines how to specify other techniques
Function Function exercised, exercised, insufficient insufficient structure structure Functional testedness
Structure Structure exercised, exercised, insufficient insufficient function function % Statement
% Decision
Structural testedness
100% 100% coverage coverage does does not not mean mean 100% 100% tested! tested!
% Condition Combination
Coverage Coverage isis not not Thoroughness Thoroughness
Statement coverage
Statement Statement coverage coverage is is normally normally measured measured by by aa software software tool. tool.
percentage of executable statements
exercised by a test suite number of statements exercised = total number of statements example: - program has 100 statements - tests exercise 87 statements - statement coverage = 87%
Typical Typical ad ad hoc hoc testing testing achieves achieves 60 60 -- 75% 75%
Example of statement coverage
1
read(a)
IF a > 6 THEN
b=a
ENDIF
print b
Statement numbers
Test case
Input
Expected output
As all 5 statements are covered by
this test case, we have achieved 100% statement coverage
Decision coverage (Branch coverage)
Decision Decision coverage coverage is is normally normally measured measured by by aa software software tool. tool.
percentage of decision outcomes
exercised by a test suite number of decisions outcomes exercised False ? = total number of decision outcomes True example: - program has 120 decision outcomes - tests exercise 60 decision outcomes - decision coverage = 50%
Typical Typical ad ad hoc hoc testing testing achieves achieves 40 40 -- 60% 60%
Paths through code
1234
12
12
123
? ?
Paths through code with loops
1 2 3 4 5 6 7 8 .
for as many times as it
is possible to go round the loop (this can be unlimited, i.e. infinite)
Example 1 Wait for card to be inserted IF card is a valid card THEN display Enter PIN number IF PIN is valid THEN select transaction ELSE (otherwise) display PIN invalid ELSE (otherwise) reject card End
Wait
Valid card?
Yes
Display Enter..
No
Reject card
Valid Yes PIN? No
Select trans...
Display PIN in..
End
Example 2 Read A IF A > 0 THEN IF A = 21 THEN Print Key ENDIF ENDIF
Print Note: there Read A Read B are 4 paths IF A < 0 THEN Yes B<0 Print Print A negative No ELSE Print A positive Print ENDIF IF B < 0 THEN End Print B negative ELSE 3 - Cyclomatic complexity: _____ Print B positive - Minimum tests to achieve: ENDIF 2 Statement coverage: ______ 2 Branch coverage: _____
Read
Example 5
A<0
Yes
Print
No
Read A Read B IF A < 0 THEN Print A negative ENDIF IF B < 0 THEN Print B negative ENDIF
Contents What is a testing technique? Black and White box testing Black box test techniques White box test techniques Error Guessing
Non-systematic test techniques
Trial and error / Ad hoc
Error guessing / Experience-driven User Testing Unscripted Testing
AAtesting testing approach approach that that isis only only rigorous, rigorous, thorough thorough and and systematic systematic isis incomplete incomplete
Error-Guessing
always worth including
after systematic techniques have been used can find some faults that systematic techniques can miss a mopping up approach supplements systematic techniques Not Not aa good good approach approach to to start start testing testing with with
Error Guessing: deriving test cases
Consider: - past failures - intuition - experience - brain storming - What is the craziest thing we can do?
ISTQB / ISEB Foundation Exam Practice
Dynamic Testing Techniques
Summary: Key Points
Test techniques are best practice: help to find faults Black Box techniques are based on behaviour White Box techniques are based on structure Error Guessing supplements systematic techniques
