Assignment # 3
Integration Testing
Objective
To evaluate your understanding of integration testing by analyzing different integration
scenarios and designing relevant test cases.
Instructions
• Answer all questions.
• Provide detailed reasoning and sample test cases where applicable.
• Use diagrams or pseudocode if helpful.
• You may assume a system of your choice (e.g., e-commerce, ride-sharing, banking app,
library management system).
Q1. Define integration testing. How does it differ from unit testing and system testing?
Q2. Describe top-down, bottom-up, and big bang integration testing approaches. Give an
example of a suitable scenario for each.
Q3. What are stubs and drivers in integration testing? When are they used?
A3. Stubs are dummy modules used to simulate lower-level modules not yet integrated..
Q4. In a ride-sharing app, consider these modules:
User Authentication
Ride Matching
Payment Gateway
Notification System
Scenario: A user logs in, books a ride, completes the payment, and receives a
confirmation message.
Task:
a. Draw a high-level module interaction diagram.
b. Identify at least 3 integration points and describe how you would test them.
c. Mention any stubs or drivers you might need.
Q5. In an online bookstore system:
Module A: Shopping Cart
Module B: Inventory
Module C: Order Processing
Module D: Payment
Scenario: A user adds an item to the cart, and at checkout, the system checks
inventory, then processes the order and payment.
Task:
a. List the possible integration bugs that could occur.
b. Design at least 2 integration test cases, including input, expected output, and
involved modules.