 DATA FLOW TESTING;

Data Flow Testing is a structural testing method that examines how

variables are defined and used throughout a program. It uses control flow
graphs to identify paths where variables are defined and then utilized,
aiming to uncover anomalies such as unused variables or incorrect
definitions. By focusing on the flow of data, it helps ensure that variables
are properly handled and used in the code.

Data flow testing (DFT) is a white-box testing technique that focuses on the
flow of data within a software program. It aims to identify and eliminate
potential anomalies that could disrupt the flow of data, leading to program
malfunctions or erroneous outputs. Here are some key strategies used in data
flow testing:

1. Static Data Flow Testing: This involves analyzing the source code
without executing the program. It constructs a control flow graph,
representing the various paths of execution through the code. This graph
is then analyzed to identify potential data flow anomalies, such as:
o Definition-Use Anomalies: A variable is defined but never used,
or vice versa.
o Redundant Definitions: A variable is defined multiple times
before being used.
o Uninitialized Use: A variable is used before it has been assigned a
value.
2. Dynamic Data Flow Testing: This involves executing the program and
monitoring the actual flow of data values through variables. It can detect
anomalies related to:
o Data Corruption: A variable’s value is modified unexpectedly,
leading to incorrect program behavior.
o Memory Leaks: Unnecessary memory allocations are not properly
released, causing memory consumption to grow uncontrollably.
o Invalid Data Manipulation: Data is manipulated in an unintended
manner, resulting in erroneous calculations or outputs.
3. Def-Use Pair Testing: This strategy focuses on the definitions and uses
of variables within the code. Each test objective is commonly referred to
as a "def-use pair." The primary aim is to select test data meticulously,
guided by various test adequacy criteria, often termed data-flow coverage
criteria. These criteria help ensure thorough exercise of each def-use pair
within the program's code.

25 February 2025
 4. Path Selection: This involves carefully selecting paths within a
program's control flow to systematically investigate the sequences of
events that pertain to the state of variables or data objects within the
program. This approach is particularly attentive to when variables are
assigned values and when these assigned values are subsequently utilized.

By employing these strategies, data flow testing helps uncover potential

related to variable usage, such as uninitialized variables or variables that are
used before they are assigned a value. This method is instrumental in
identifying critical points within the program where data may be mishandled,
leading to bugs, errors, or unexpected program behavior.
1. Domains and Paths: INTRODUCTION:  Domain:In mathematics, domain is a set of possible
values of an independant variable or the variables of a function.  Programs as input data
classifiers: domain testing attempts to determine whether the classification is or is not
correct.  Domain testing can be based on specifications or equivalent implementation
information.  If domain testing is based on specifications, it is a functional test technique. 
If domain testing is based implementation details, it is a structural test technique.  For
example, you're doing domain testing when you check extreme values of an input variable.
All inputs to a program can be considered as if they are numbers. For example, a character
string can be treated as a number by concatenating bits and looking at them as if they were
a binary integer. This is the view in domain testing, which is why this strategy has a
mathematical flavor. THE MODEL: The following figure is a schematic representation of
domain testing

25 February 2025
Domain and interface testing are important aspects of software testing, focusing on ensuring
that both the business logic (domain) and communication mechanisms (interfaces) of an
application function as expected.

Domain Testing

Domain testing, also known as boundary testing or input domain testing, is focused on
validating the business logic and the correctness of data input and output within the
application. It ensures that the software handles various types of input, including valid,
invalid, boundary, and edge cases correctly.

Key Aspects of Domain Testing:

1. Input Validation: Check if the application properly handles valid inputs, invalid inputs, and
edge cases (boundary values).
2. Business Logic: Verify that the logic aligns with the intended business rules and constraints.
3. Error Handling: Ensure the system catches and manages errors appropriately when invalid
inputs are provided.
4. Data Processing: Check how data is manipulated and processed within the system. For
example, verifying calculations, transformations, or filtering of data.

Example:

For a login system, testing the domain might involve verifying:

 Whether the system handles correct usernames and passwords.

 Whether it catches invalid usernames or passwords.
 Boundary conditions, such as the maximum length of username or password.

Interface Testing

Interface testing focuses on ensuring that the interactions between different software
components (e.g., between the application and external systems, between modules, or
between client and server) work as expected. It validates communication protocols, data
formats, and the interaction between different systems.

Key Aspects of Interface Testing:

1. API Testing: If the system interacts with other software via APIs, testing ensures that the API
requests, responses, and behavior align with the expected behavior.

25 February 2025
 2. User Interface Testing (UI Testing): This focuses on ensuring that the interface between the
user and the application is intuitive, functional, and free of bugs.
3. Protocol/Communication Testing: Ensuring that the communication protocols (like HTTP,
TCP, etc.) between systems are functioning as expected.
4. Data Exchange Validation: Ensuring that the data sent between systems is formatted
correctly, and no data corruption occurs during the transmission.

Example:

For an e-commerce platform, testing the interface might involve:

 Ensuring that the checkout API works as expected, sending correct data between the
frontend (user interface) and backend (server).
 Validating that the payment gateway interface works correctly by sending the payment data
and getting an appropriate response.

Comparison:

 Domain Testing focuses on the business logic and data correctness within the application.
 Interface Testing focuses on communication and interaction between systems or software
components.

Both are essential for ensuring a robust, reliable, and user-friendly application.

25 February 2025