BENGAL COLLEGE OF ENGINEERING AND TECHNOLOGY

A REPORT ON
Top Down Approach For Testing

Submitted by
NIRAJ KUMAR

University roll no.- 12500221073

College roll No.:-214078299

Subject:-software Engineering

Dept. Of Information Technology 3rd Year

Under the guidance of

Mr. Biplabh palye

( HOD OF IT Department)
 ACKNOWLEGMENT

On the very outset of this report, I would like to extend my

sincere & heartfelt obligation towards all the personages who
have helped me in this endeavour. Without their active
guidance, help, cooperation, I would not have made headway
in the project .I am ineffably indebted to Sir for conscientious
guidance and encouragement to accomplishment this report I
am extremely thankful and pay my gratitude to my faculty Mr.
Biplabh palye for his valuable guidance and support on
completion of this report writing in its presently
 TABLE OF CONTENT

 ABSTRACT

 INTRODUCTION

 METHODOLOGY

 DISCUSSION

 CONCLUSION

 APPLICATION

 BIBLIOGRAPHY
 ABSTRACT

The top down integration testing method is an incremental approach that

involves joining two or more logically related modules. The process
involves using dummy programs called Stubs and Drivers to stimulate the
behavior of unintegrated lower-level modules.

This technique follows the control flow or architectural structure to test it

from top to bottom. Unit testing is performed on the top module alone,
followed by integration of the lower modules. In this way, all the modules
are integrated and tested simultaneously.

Stubs are temporary replacements for modules and produce the same output
as the actual products. In addition to the main module serving as a test
driver, stubs are substituted for all components directly under the main
control. Further, the stubs are replaced with actual components one by one.
 INTRODUCTION
A top-down approach to software testing is a systematic methodology used
to verify the functionality and quality of a software application or system. It
is a widely adopted testing strategy that begins with a high-level perspective
and progressively drills down into the finer details. In this approach, testing
starts with the most comprehensive components or modules of the system
and gradually moves towards testing individual units or components. Let's
delve into the key aspects of the top-down approach to testing.

1. High-Level Testing: The top-down approach starts by testing the

higher-level modules or components of the software system. These are
typically the ones that interact with the user interface or are
responsible for coordinating various functionalities. This phase
focuses on verifying the overall functionality and integration of these
modules.

2. Stubs and Drivers: To simulate lower-level components that have not

yet been developed, stubs and drivers are used. Stubs are dummy
modules that stand in for lower-level modules, while drivers mimic the
behavior of higher-level modules. This allows testing to progress even
when certain components are incomplete.

3. Progressive Refinement: As testing moves down the hierarchy of

components, the level of detail and granularity increases. This means
that, as each high-level module is deemed stable and functioning
correctly, testing shifts to the lower-level modules within that module.
This iterative process continues until individual units are thoroughly
tested.
4. Identification of Issues: The top-down approach often helps in early
identification of critical issues or defects at the higher levels of the
software, such as architectural problems or integration issues. This
early detection can save time and resources in the long run as issues
can be addressed before they propagate through the entire system.

5. Integration Testing: Integration testing is a crucial part of the top-

down approach. It ensures that the interactions and interfaces between
various modules and components are working as expected. Problems
at this level are addressed before moving on to unit testing.
 METHODOLOGY

A top-down approach to software testing is a systematic method that starts

with the high-level components of a system and progressively works down
to test the lower-level modules or units. This approach helps identify and
address critical issues early in the development process. Here's a step-by-step
methodology for conducting top-down testing:

1. Understanding Requirements:
 Begin by thoroughly understanding the project requirements,

specifications, and design documents. This will help you identify

the major components and their interactions.


2. Test Planning:
 Develop a test plan that outlines the scope, objectives, test cases,

and resources needed for the testing process.

 Identify the high-level modules or components to be tested first,

typically those that form the core functionality of the system.



3. Test Strategy:
 Define the testing strategy, including the types of testing to be

performed (e.g., functional, integration, system, or acceptance

testing).
 Determine the order in which components will be tested based on

their dependencies and criticality.



4. Stubs and Drivers:

 Create stubs or drivers for components that are not yet developed

or available. Stubs simulate lower-level components, while drivers

simulate higher-level components.
5. High-Level Testing:
 Begin testing the top-level components of the system, such as the

main application or the primary functionality.

 Focus on testing the interfaces between these components and

their expected behavior.

6. Integration Testing:
 Gradually work your way down to the lower-level components,

performing integration testing as you go.

 Test the interactions between modules and verify that data flows

correctly between them.

7. Regression Testing:
 After each round of testing, perform regression testing to ensure

that new changes or fixes haven't introduced new issues.

8. Incremental Testing:
 Continue testing lower-level components incrementally, building

upon the tests you've already conducted.

 Pay close attention to boundary conditions, error handling, and

edge cases.

9. Defect Reporting and Tracking:

 Record and report any defects or issues discovered during testing.

 Use a defect tracking system to prioritize and monitor the

resolution of these issues.

10. Performance and Load Testing:

 As you progress down the hierarchy, consider conducting
performance and load testing to ensure the system meets
performance requirements.

11. User Acceptance Testing (UAT):

 Once the core functionality is thoroughly tested, involve end-users
or stakeholders in UAT to validate that the system meets their
needs and expectations.
12. Documentation:
 Maintain detailed documentation of test cases, test results, and any
changes made during the testing process.

13. Test Completion:

 Continue testing until all components have been thoroughly tested,
and the system meets the defined criteria for acceptance.

14. Test Reporting:

 Prepare a test summary report that outlines the testing process,
results, and any outstanding issues.
 Share the report with relevant stakeholders for review
 DISCUSSION

The top-down approach to testing is a widely used methodology in software

testing, and it offers several advantages and considerations for effective
testing throughout the software development lifecycle. Here's a discussion
of the key points related to the top-down approach:
1. Early Identification of Critical Issues: One of the primary benefits
of the top-down approach is that it starts testing from the highest level
of the system, focusing on the most critical and visible functionalities.
This allows for the early identification and resolution of major issues,
which is essential for project success.

2. Better Test Coverage: By beginning with high-level components and

gradually moving down to lower-level modules, this approach ensures
that the overall system architecture is tested thoroughly. It helps verify
that different parts of the system interact correctly and that data flows
as expected between components.

3. Progressive Refinement: Top-down testing enables progressive

refinement of testing activities. Testers can concentrate on testing the
most important aspects of the software first, providing stakeholders
with a sense of confidence in the core functionality before delving into
the details.
4. Parallel Testing: Because top-down testing begins with higher-level
components, it allows for parallel testing efforts. Testers can work on
testing different parts of the system simultaneously, which can
expedite the testing process and accelerate bug discovery.

5. Stubs and Drivers: In cases where lower-level components are not

yet available, stubs and drivers can be created to simulate their
behavior. This allows testing to proceed even when some components
are still under development.

6. Ease of Debugging: If an issue is detected at the higher levels of the

system, it is typically easier to debug and isolate the problem since
there are fewer variables to consider. This can save time and effort
during the debugging process.

7. Risk Mitigation: By focusing on critical functionalities first, the top-

down approach helps mitigate risks associated with core system
components. If major issues are discovered early, there is more time to
address them before they become costly to fix.

8. Client/Stakeholder Involvement: This approach encourages early

involvement of clients or stakeholders in the testing process, as high-
level functionalities are often the most visible and critical to them.
Their feedback can influence the direction of testing efforts.
 CONCULSION

In conclusion, the top-down approach to testing is a systematic and effective

methodology for ensuring the quality and reliability of software systems. It
provides a structured way to prioritize testing efforts, identify critical issues
early, and progressively refine testing activities throughout the development
process.
However, it should be applied thoughtfully, taking into consideration the
project's specific requirements and dependencies to maximize its benefits.
 BIBLIOGRAPHY

 CLASS NOTES
 WEBSITE
www.google.com

1. Here is a bibliography of books and articles related to the top-

down approach for software testing:

2. Beizer, Boris. (1990). "Software Testing Techniques." Van

Nostrand Reinhold.
3. This classic book provides an in-depth overview of various
software testing techniques, including top-down testing.
4. Kaner, Cem, Falk, Jack, and Nguyen, Hung Quoc. (2017).
"Testing Computer Software." Wiley.
5. This book offers practical insights into software testing methods,
including a discussion of top-down testing strategies.
6. Myers, Glenford J. (2004). "The Art of Software Testing."
Wiley.
7. Glenford Myers' book is a valuable resource for software testers
and covers different testing techniques, including top-down
testing.