SOFTWARE TESTING SYLLABUS

Unit-I Unit-II Unit-III Unit-IV : Introduction & The Taxonomy of Bugs : Flowgraphs and Path Testing : Transaction-Flow Testing & Data Flow Testing : Domain Testing

Unit-V
Unit-VI

: Paths, Path Products and Regular Expressions

: Logic-Based Testing

Unit-VII : States, State-Graphs and Transition Testing

Unit-VIII : Graph Matrices and Applications
Data Flow Testing 1

SOFTWARE TESTING SYLLABUS

Unit-I Unit-II Unit-III Unit-IV : Introduction & The Taxonomy of Bugs : Flowgraphs and Path Testing : Transaction-Flow Testing & Data Flow Testing : Domain Testing

Unit-V
Unit-VI

: Paths, Path Products and Regular Expressions

: Logic-Based Testing

Unit-VII : States, State-Graphs and Transition Testing

Unit-VIII : Graph Matrices and Applications
Data Flow Testing 2

SOFTWARE TESTING SYLLABUS

Unit-I Unit-II Unit-III Unit-IV : Introduction & The Taxonomy of Bugs : Flowgraphs and Path Testing : Transaction-Flow Testing & Data Flow Testing : Domain Testing

Unit-V
Unit-VI

: Paths, Path Products and Regular Expressions

: Logic-Based Testing

Unit-VII : States, State-Graphs and Transition Testing

Unit-VIII : Graph Matrices and Applications
Data Flow Testing 3

SOFTWARE TESTING SYLLABUS

Unit-I Unit-II Unit-III Unit-IV : Introduction & The Taxonomy of Bugs : Flowgraphs and Path Testing : Transaction-Flow Testing & Data Flow Testing : Domain Testing

Unit-V
Unit-VI

: Paths, Path Products and Regular Expressions

: Logic-Based Testing

Unit-VII : States, State-Graphs and Transition Testing

Unit-VIII : Graph Matrices and Applications
Data Flow Testing 4

UNIT - III(b)
DATA-FLOW TESTING

Data Flow Testing

Unit-III : Data-flow testing

1) 2) 3) 4) 5)

Synopsis Data-Flow Testing Basics Data-Flow Testing Strategies Application, Tools, Effectiveness Summary
Transaction Flow Testing 6

(1)Synopsis

Data flow testing uses CFG unreasonable things happen to data.

to

explore

Testing path selection contains data flow anomalies, fill the gaps between Complete path, branch and Statement testing.

Comparisons of strategies, Tools, Effectiveness are the issues.

Data Flow Testing 7

(2)Data Flow Testing Basics

i. ii. iii.

Motivation & Assumptions

Data flow Graphs Data flow Models

Transaction Flow Testing

(i)Data Flow Testing Basics

Data flow testing is the name given to a family of test strategies based on selecting paths through the programs control flow in order to explore sequences of events related to the status of data objects. E.g.: Pick enough paths to assure that every data object has been initialized prior to use or that all defined objects have been used for something.

Data Flow Testing

(i)Motivation

One would not feel confident about a program without executing every statement in it as part of some test.

one should not feel confident about a program without having seen the effect of using the value produced by each and every computation.

Data Flow Testing

10

(i)Data Flow Machines

There are two types of data flow machines with different architectures.
Von Neumann Machines b) Multi-instruction, Multi-data (MIMD)
a)

Machines

Data Flow Testing

11

(a) Von Neumann Machine Architecture

Most computers today are Von-neumann machines. This architecture features interchangeable storage of instructions and data in the same memory units. The Von Neumann machine Architecture executes one instruction at a time in the following, micro instruction sequence:

Fetch instruction from memory Interpret instruction Fetch operands Process or Execute Store result Increment program counter GOTO 1

Data Flow Testing

12

(b)Multi-instruction, multi-data machines (MIMD) Architecture

These machines can fetch several instructions and objects in parallel. They can also do arithmetic and logical operations simultaneously on different data objects. The decision of how to sequence them depends on the compiler.

Data Flow Testing

13

(i)Bug Assumption

Control Flow is generally correct and that something has gone wrong with the s/w so that the data objects are not available when they should be/silly things done to the data objects.

Data Flow Testing

14

(ii)Data Flow Graphs

The data flow graph is a graph consisting of nodes and directed links. Use a control graph to show what happens to data objects of interest at that moment. The objective is to expose deviations between the data flows we have and the data flows we want.

Data Flow Testing

15

Data Object State and Usage

Data objects can be created, killed and used. They can be used in two distinct ways:

In a calculation As a part of a control flow predicate d- defined, created, initialized, etc., k- killed, undefined, released. u- used for some thing. c- used in a calculation p- used in a predicate
Data Flow Testing 16

The following symbols denote these possibilities.

Defined (d)

An object is defined explicitly when it appears in a data declaration. Or implicitly when it appears on the left hand side of the assignment. It is also to be used to mean that a file has been opened. A dynamically allocated object has been allocated. Something is pushed on to the stack. A record written.
Data Flow Testing 17

Killed or Undefined (k)

An object is killed on undefined when it is released or otherwise made unavailable. When its contents are no longer known with certitude. Release of dynamically allocated objects back to the availability pool. Return of records and a file is closed The old top of the stack after it is popped. An assignment statement can kill and redefine immediately.
Data Flow Testing 18

Usage (u)

A variable is used for computation (c) when it appears on the right hand side of an assignment statement.

A file record is read or written.

It is used in a Predicate (p) when it appears directly in a predicate. (If A>B)
Data Flow Testing 19

Data Flow Anomalies

An anomaly is denoted by a two-character sequence of actions. Eg: ku - the object is killed & then used, dd - the object is defined twice without an intervening usage.

What is an anomaly is depend on the application.

Data Flow Testing 20

Data Flow Anomalies

There are 9 possible two-letter combinations for d, k and u. some are bugs, some are suspicious, and some are okay. dd- probably harmless but suspicious. Why define the object twice without an intervening usage. dk- probably a bug. Why define the object without using it. du- normal case. The object is defined and then used. kd- normal situation. An object is killed and then redefined. kk- harmless but probably buggy. Did you want to be sure it was really killed? ku- a bug. the object doesnt exist. ud- usually not a bug because the language permits reassignment at almost any time. uk- normal situation. uu- normal situation.
Data Flow Testing 21

Data Flow Anomalies

In addition to the two letter situations there are six single letter situations. Use a leading dash(-) to mean that nothing of interest (d,k,u) occurs prior to the action noted along the entry-exit path of interest. A trailing dash to mean that nothing happens after the point of interest to the exit.
Data Flow Testing 22

Data Flow Anomalies

-k: possibly anomalous, killing a variable that does not exist. (A) -d: okay. This is just the first definition along this path. (OK) -u: possibly anomalous. Not anomalous if the variable is global and has been previously defined. (A) k-: not anomalous. The last thing done on this path was to kill the variable. (NA) d-: possibly anomalous. The variable was defined and not used on this path. (A) u-: not anomalous. The variable was used but not killed on this path. (NA)
Data Flow Testing 23

Data-Flow Anomaly State Graph

Data flow anomaly model prescribes that an object can be in one of four distinct states:

K - undefined, previously killed, doesnt exist D - defined but not yet used for anything U - has been used for computation or in predicate A - Anomalous

These capital letters (K,D,U,A) denote the state of the variable and should not be confused with the program action, denoted by lower case letters.

Data Flow Testing

24

Unforgiving Data-Flow Anomaly State Graph

Unforgiving model, in which once a variable becomes anomalous, it can never return to a state of grace.
K u,k k d d u
Data Flow Testing 25

d,k

A k,u,d

Static Vs Dynamic Anomaly Detection

Static analysis is analysis done on source code without actually executing it.

Eg: source code syntax error detection is the static analysis result.

Dynamic analysis is done on the fly as the program is being executed and is based on intermediate values that result from the programs execution.

For example: a division by zero warning is the dynamic result.

Data Flow Testing

26

Static Vs Dynamic Anomaly Detection

If a problem, such as a data flow anomaly, can be detected by static analysis methods, then it doesnt belongs in testing- it belongs in the language processor. There is actually a lot more static analysis for data flow analysis for data flow anomalies going on in current language processors. For example, language processors which force variable declarations can detect (u) and (ku) anomalies. But still there are many things for which current notions of static analysis are inadequate.
Data Flow Testing 27

Why isnt static analysis enough?

There are many things for which current notions of static analysis are inadequate they are: Dead Variables. Arrays. Records and Pointers. Dynamic subroutine or function name in a call. False anomalies. Recoverable anomalies and alternate state graphs. Concurrency, interrupts, system issues.

Although static analysis methods have limits, they are worth using and a continuing trend in language processor design has been better static analysis methods for data flow anomaly detection.
Data Flow Testing 28

(iii)The Data Flow Model

The data flow model is based on the programs control flow graph. Each link is rendered by with symbols or sequences of symbols that denote the sequence of data operations on that link with respect to the variable of interest. Such annotations are called link weights. The control flow graph structure is same for every variable: it is the weights that change.

Data Flow Testing

29

Components of the Model

The modeling rules: To every statement there is a node, whose name is unique. Every node has at least one outlink and at least one inlink except for exit nodes and entry nodes. Exit nodes are dummy nodes placed at the outgoing arrowheads of exit statements to complete the graph. The entry nodes are dummy nodes placed at entry statements for the same reason. The outlink of simple statements are weighted by the proper sequence of data flow actions for that statement. Predicate nodes are weighted with the p- use on every outlink, appropriate to that outlink.
Data Flow Testing 30

Components of the Model

Every sequence of simple statements can be replaced by a pair of nodes that has, as weights on the link between them, the concatenation of link weights. If there are several data flow actions on a given link for a given variable, then the weight of the link is denoted by the sequence of actions on that link for that variable. Conversely, a link with several data flow actions on it can be replaced by a succession of equivalent links, each of which has at most one data flow action for any variable.
Data Flow Testing 31

Data Flow Graph-Example

CODE (PDL) Z:=Z-1 1 INPUT X,Y IF Z=0 GOTO ELL8 Z:=X+Y1 U:=U+1 V:=X-Y1 NEXT U9 IF Z>=0 GOTO SAM3 V(U-1) :=V(U+1)+U(V-1) JOE: Z:=Z-14 ELL: V(U+U(V)) :=U+V10 5 SAM: Z:=Z+V IF U=V GOTO JOE11 6 FOR U=0 TO Z IF U>V THEN U:=Z12 V(U),U(V) :=(Z+V)*U Z:=U 13 7 IF V(U)=0 GOTO JOE END
Flowgraphs & Path Testing 32

(a)Unannotated Control Flow Graph

begin 1 3 z>0? 4 joe Sam 5 loop 6
V(u)=0?

Ell 2 end 13 YY 12 U>V? 11 U=V? 10

U=Z? 9

Z=0?

Data Flow Testing

33

(b) Control Flow Graph Annotated for X and Y Data Flows

begin 1 dcc 3 z>0? 4 joe Sam 5 loop 6
V(u)=0?

ell 2 end 13 YY 12 U>v? 11 U=v? 10

U=z? 9

8 Z=0?

Data Flow Testing

34

(c) Control Flow Graph Annotated for Z Data Flow

Begin 1 d p 3 p z>0 joe 4 cd Sam 5 cd loop 6 p 2 End c 13 YY 12 c U>v 11 U=v 10 ell p U=z 9 p 8 Z=0 cc V(u)=0 7 cd

Data Flow Testing

35

(3)Data Flow Testing Strategies

a) b)

General
Terminology

c)
d)

The Strategies
Slicing, Dicing, Data-flow, Debugging

Transaction Flow Testing

36

(a) General

Data Flow Testing Strategies are structural strategies. Data Flow Testing Strategies require data flow link weights. Data Flow Testing Strategies are based on selecting test path segments (sub paths) that satisfy some characteristic of data flows for all data objects. Eg: All sub paths that contain a d,u,k,du,dk.

Data Flow Testing

37

(b) Terminology

A Definition Clear Path Segment with respect to a variable X is a connected sequence of links such that X is defined on the first link and not redefined or killed on any sub sequent link of that path segment. The fact that there is a definition clear sub path between two nodes does not imply that all sub paths between those nodes are definition clear. [(1,3,4,5) path in figure-4]
Data Flow Testing 38

Loop Free & Simple Path Segment

A loop free path segment is a path segment for which every node is visited at most once.
A simple path segment is a path segment in which at most one node is visited twice.

Data Flow Testing

39

A du path

A du path from node i to k is a path segment such that if the last link has a computational use of X, then the path is simple and definition clear; if the penultimate node is j-that is, the path is (i.p,q,r,s,t,j,k) and link (j,k)has a predicate use- then the path from i to j is both loop free and definition clear.

Data Flow Testing

40

(c)The data flow testing strategies

Various types of data flow testing strategies in decreasing order of their effectiveness are: All du paths Strategy All uses Strategy All p-uses/some c-uses Strategy All c-uses/some p-uses Strategy All definitions Strategy All predicates uses, all computational uses Strategies Ordering the strategies
Data Flow Testing 41

(i)All du paths Strategy (ADUP)

The all du path (ADUP) strategy is the strongest data flow testing strategy. It requires that every du path from every definition of every variable to every use of that definition be exercised under some test.

Data Flow Testing

42

(ii)All Uses Strategy (AU)

The all uses strategy is that at least one definition clear path from every definition of every variable to every use of that definition be exercised under some test.

Data Flow Testing

43

(iii)All p-uses/some c-uses Strategy

All p-uses/some c-uses (APU+C) strategy is defined as follows: for every variable and every definition of that variable, include at least one definition free path from the definition to every predicate use; if there are definitions of the variables that are not covered by the above prescription, then add computational use test cases as required to cover every definition.
Data Flow Testing 44

(iv)All C-uses/some p-uses Strategy

The all c-uses/some p-uses strategy (ACU+P) is to first ensure coverage by computational use cases and if any definition is not covered by the previously selected paths, add such predicate use cases as are needed to assure that every definition is included in some test.

Data Flow Testing

45

(v)All Definitions Strategy(AD)

The all definitions strategy asks only every definition of every variable be covered by at least one use of that variable, be that use a computational use or a predicate use.

Data Flow Testing

46

(vi)All predicate-uses(APU), All Computational uses(ACU) Strategies

The all predicate uses strategy is derived from APU+C strategy by dropping the requirement that we include a c-use for the variable if there are no p-uses for the variable.
The all computational uses strategy is derived from ACU+P strategy by dropping the requirement that we include a p-use for the variable if there are no c-uses for the variable.
Data Flow Testing 47

(vii) Ordering the Strategies

All paths All du paths All uses

All c/some p
all defs All c uses

all p/some c

All p uses Branch statement

Data Flow Testing 48

(d) Slicing and Dicing

A program slice is a part of a program defined with respect to a given variable X and a statement i: it is the set of all statements that could affect the value of X at statement i- where the influence of a faulty statement could result from an improper computational use or predicate use of some other variable at prior statements. If X is incorrect at statement i, it follows that the bug must be in the program slice for X with respect to i. A program dice is a part of a slice in which all statements which are known to be correct have been removed.
Data Flow Testing 49

(d) Slicing and Dicing

A dice is obtained from a slice by incorporating the info. From testing/debugging. Debugging ends when the dice has been reduced to one faulty statement. Dynamic slicing is a refinement of static slicing where statements on achievable paths are included.

Data Flow Testing

50

Summary

Data are as important as code. Data integrity is as imp as code integrity. Data flow anomaly is peculiar to the application. Use all available tools to detect anomalies statically. Data flow testing strategies fill the gap b/w path and Branch testing. Dont restrict your notion of data flow anomaly to obvious. i.e. the symbols d,k,u and anomalies are interpreted by file opening and closing etc.

Data Flow Testing

51