Chapter 7

Exercise 4: Why should integration testing be performed? What types of errors can this phase of
testing reveal?
Answer: Integration Testing: When multiple software components are coupled, integration tests
are used to verify their efficacy and performance. Units or individual components of the software
are tested in a group during this testing. The integration testing level focuses on exposing faults
that occur during the interaction of integrated components or units.
Types of errors that can be occur in this phase of testing reveal are listed below:
 Construction
 Location of Functionality
 Changes in Functionality
 Added Functionality
 Violation of Data Constraints
 Coordination of Changes
 Initialization/Value Errors

Exercise 7: Using the module hierarchy given in Figure 7.13, show the orders of module
integration for the top-down and bottom-up integration approaches. Estimate the number of stubs
and drivers needed for each approach. Specify the integration testing activities that can be done
in parallel, assuming you have three SIT engineers. Based on the resource needs and the ability
to carry out concurrent SIT activities, which approach would you select for this system and why?
Answer: Top-down Testing: This method involves testing starting with the main module and
working down to the sub-modules. If the submodule is not developed, it is simulated using a
temporary program called STUB. It would take four STUBS to test all fourth-level modules.
Bottom-up testing: If the main module is not created, a temporary program named DRIVERS is
used to emulate the main module. From the ground up, three drivers would be required. Because
there are more STUBS than DRIVERS in this layout, I favor a Top-Down strategy.
STUBS are fake modules that are always identified as "called programs," or, to put it another
way, they are utilized in integration testing while subprograms are being built. STUBS are fake
modules that are always used to emulate low-level modules.
DRIVERS are also fake modules that are always identified as "calling program," which are
handled in bottom-up integration testing, and are only utilized when main programs are being
built. Drivers are fake modules that are constantly used to emulate high-level modules.
 Chapter 9
Exercise 7: Consider the triangle classification specification. The system reads in three positive
values from the standard input. The three values A, B, and C are interpreted as representing the
lengths of the sides of a triangle. The system then prints a message to the standard output saying
whether the triangle, if it can be formed, is scalene, isosceles, equilateral, or not a triangle.
Develop a decision table to generate test cases for this specification.
Answer:
Expected
Test Cases X Y Z Output
Equilateral
1 100 100 100 triangle
2 50 3 50 Isosceles triangle
Equilateral
3 40 50 40 triangle
4 3 4 5 Right-angled
triangles
Equilateral
5 10 10 10 triangle
6 2 2 5 Isosceles triangle
7 100 50 100 Scalene triangle
8 1 2 3 Non-triangles
9 2 3 4 Scalene triangle
10 1 3 1 Isosceles triangle