Integration Testing - Reading Assignment

[RayUtik]

1. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.
2. Integration test identifies bugs in early stages and solves system level issues such as a broken database schema, mistaken cache integration, etc
3. While the top-down approach focuses on breaking down a big problem into smaller and understandable chunks, the bottom-up approach first focuses on solving the smaller problems at the fundamental level and then integrating them into a whole and complete solution.

[AndyEken]

1. Why do we write integration tests?
   To find problems between different modules before the program is run at a higher level.
2. What problems do integration tests solve?
   Interoperability problems between components on different levels and complexity.
3. What are the differences between top-down and bottom-down approaches?
   Top-down starts at the highest level in the code base and test its way downwards, where bottom-up does the opposite; starts at the lowest level and test upwards. A combination of the two methods may be used to get guidance on where to look for possible errors.

[enzinointhesky]

1. Why do we write integration tests?
   Because we want to test that all the units of an application can work together

2. What problems do integration tests solve?
   It solves the problem that a complete use of the units of an application while used together can bring.

3. What are the differences between top-down and bottom-up approaches?
   Top down first tests the complete use of the application units together while bottom up tests the units singularly first

[rom]

1. Why do we write integration tests?
   To make sure program units work when combined together .

2. What problems do integration tests solve?
   It exposes problems with the interfaces among program components before trouble occurs in real-world program execution.

3. What are the differences between top-down and bottom-down approaches?
   Bottom-up integration testing begins with unit testing followed by tests of of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that.

[CryptoKnight84]

1. To test whether the units of the program work together as intended.
2. Interface issues of the components.
3. The difference is whether the unit test are done first followed by higher organizational components or the other way around. It seems to me that in the end all levels are tested. The meaningful difference is in design philosophy: Do we design and test high level functionality first and then get granular, or do we need to draw out a complete organizational design of the entire software (component), before we can test and build anything?

[Alex_L]

1) Why do we write integration tests?
This helps assist in exposing interface problems before they occur in the released version of the program.

2) What problems do integration tests solve?
This method helps solve various errors for different angles and reviews functions and procedural, from smaller to larger and larger to smaller programming units of integration.

3) What are the differences between top-down and bottom-down approaches?
The differences are how the units are broken up. Top to bottom tests larger units of integrated components and breaks them down as errors occur, bottom to top is reversed and tests smaller units that are integrated to works its way up to the complete procedure or function step.

[c1cag1b3]

1. To expose problems with the interface among program components.
2. Detect interoperability between different system components.
3. Bottom up starts with unit testing and progressively goes to higher level testing of modules, where Top down does it opposite - from module level to units.

[jfots]

Why do we write integration tests?
To combine the modules from the unit testing an run them together in test drivers and test stubs. This way interface defects can be detected.

What problems do integration tests solve?
Interoperability between systems, to expose problems with the interfaces among program components before they occur.

What are the differences between top-down and bottom-down approaches?
Start with main functions and create sub-functions.
Second with module that you later integrate with main functions.

[jelle_van_der_meer]

1. Why do we write integration tests?
   With integrations tests you can test different components of a group in an app.

2. What problems do integration tests solve?
   Unexpected interactions between programming functions/procedures.

3. What are the differences between top-down and bottom-up approaches?
   Top-down testing is that you begin with little components and build your way up to bigger components within a app/dapp. And bottom-up testing means that you first test the biggest components and work your way down to the smallest component in your app/ dapp.

[Zinar6]

1. To test different combinations of units as groups.
2. It can expose bugs in program components before execution.
3. Buttom up, you start with units and then on to higher level of combinations in groups called modules. In top and bottom, the higher level module is tested first.

[Chapin]

1. Because integration testing can expose problems with the interfaces among program components.
2. Problems with the interfaces among programs.
3. Bottom-up begins with unit testing, while top-down begins with modules tested first and progressively lower-level modules testes

[Alichia]

Reading Assignment: Integration Testing

Why do we write integration tests?

To expose problems with the interface among program components before trouble occurs in real-world program execution.

What problems do integration test solve?

Issues regarding how components are integrated and interact in the entire application.

What are the differences between top-down and bottom-down approach?

Bottom-up integration testing begins with unit testing, followed by tests progressively higher-level combination of units called modules or builds

Top-down integration testing, the highest-level modules are tested first

[asvpxroland]

1. is a software development process which program units are combined and tested as groups in multiple ways.

2. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.

3. Top-down refers to testing higher-level combinations of units called modules or builds, followed by progressively lower-leveled models. Bottom-up does the complete opposite.

[jerre]

1. *Why do we write integration tests?

to test the entire code as a whole or several units as a whole

2. What problems do integration tests solve?
   To expose any errors in interaction between units of code, “are they interfacing correctly?”

3. What are the differences between top-down and bottom-up approaches?

bottom up tests individual units for flaws.
top down tests grouped units for flaws

[MichaelW]

1. Why do we write integration tests?
   To expose problems with the interfaces among program components before trouble occurs in real-world program execution.
2. What problems do integration tests solve?
   They identify problems with the way different program components interact with each other.
3. What are the differences between top-down and bottom-up approaches?
   Bottom-up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that.

[Acex13]

1. Why do we write integration tests? It allows us to test various components of the application when used in conjunction with others, to see if one effects a negative outcome with another.

2. What problems do integration tests solve? “Integration testing exposes problems with the interfaces among program components before trouble occurs in a real-world program execution.”

3. What are the differences between top-down and bottom-up approaches? Bottom-up integration testing begins with unit testing and then follows with tests of higher level combinations of units called modules or builds, where top-down integration testing tests the highest-level modules first and lower-level modules, after.

[Lennart_Lucas]

1. Unit tests ensure that the smallest possible units work, however when combined with other units do they still function. This is where integration testing comes in. To see wether units are successfully integrated within the whole.
2. It exposes issues with interections between units.
3. Bottom-up starts with units and then integrates them into a greater overlying system.
   Top-down does the opposite, starting with a higher laying system, then progressing to the units.

[theosebagh]

Integration Testing – Questions

1. Why do we write integration tests?

Integration tests are written to detect problems with an interface among program components before any issue may occur after a program’s execution into the real world.

2. What problems do integration tests solve?

Integration tests detect errors that may occur while an application is being used as a whole (not just specific parts/components of it). They test whether all the subsystems and interfaces are working individually AND together, without producing any errors.

Integration testing is meant to simulate the behavior/outputs of an application in the real world and resolve any interoperabilities issues between different systems (should they occur).

3. What are the differences between top-down and bottom-down approaches?

Bottom-up integration testing begins with unit testing followed by tests of higher level combinations of units called modules or builds, whereas top-down integration testing tests the highest-level modules first and lower-level modules afterwards.

[Jules]

1. To expose problems before the occur in the real-world.
2. They can find issues with the application as a whole.
3. The difference is bottom-up begins with unit testing and moves up, while top-down begins wit the highest-level modules and then moves to the lower ones.

[zozaa]

1. We write and use integration tests because rarely there is a system that is used in isolation from other systems, external data sources, various forms of the system itself (mobile, web, desktop versions etc.). So not only does one component or module/ functionality has to work, but it has to work in response to other modules or functions of other sytems. This is what integration testing provides.

2. They solve probles that occur in touching points or interactions of different systems or modules within a system.

3. Bottom up testing approach starts from basic and initial functions, smaller modules, building up the complexity and additional features. Top down testing means the main module is the first one to test, continuing the testing with modules lower in the IS architecture.