Integration Testing - Reading Assignment

[Cryptojunkie]

1. **Why do we write integration tests?

• In order to highlight any issues with the integration of components prior to deployment.

2. **What problems do integration tests solve?

• They can identify any problems between the interfaces and program components prior to execution

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

• Top Down approach would be a way of testing the program in its entirety before testing all the smaller components relating to the program. Where as Bottom Up approach tests every unit of code in its smallest form and works its way up through the modules or builds as they increase with size

[cincinnato]

1. Why do we write integration tests?

They ensure the single units will work properly once they will be integrated.

2. What problems do integration tests solve?

It solves the problems of interaction among the different units, that may work properly on single test, but not interact properly once integrated.

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

The top-down approach starts with testing the entire application and then the components. Finally it tests the single units.
The bottom-up approach goes in the opposite direction, starts with testing each individual unit, then each component the integrated application.

[Kingsman]

1. Why do we write integration tests?
   egration tests are necessary for testing individual units combined in group.
2. What problems do integration tests solve?
   Functional tests answer questions like, Does this feature work? or can the operator do this? Performance, stress or endurance tests are often used when exercising the system outside the bounds of standard situations or settings.
3. What are the differences between top-down and bottom-down approaches?
   The difference between bottom up and top down testing is bottom up starts by testing the smallest portions of the code working up to the more complex as with top down it starts with the most complex to the least.

[Ho11and]

1. To pin point any potential problems before program is executed in the real world.
2. They solve any problems by identifying the different ways the components of the program interact with each other.
3. Bottom-up integration testing begins with unit testing followed by higher-level combinations of units
   In top-down integration testing, the highest-level modules are tested first and progressively lower level units are tested after that.

[Monica]

1. Why do we write integration tests?
To be able to identify and solve any possible problem before running the program in the real world.

2. What problems do integration tests solve?
Problems with interfaces between program components.

3. What are the differences between top-down and bottom-down approaches?
The bottom-up integration approach consists of testing first with unit tests, unlike the top-down integration approach which begins by testing highest-level modules.

[SMDadli]

1. To make sure all units of the code are able to work with each other and execute the code without any errors.

2. Interoperability between systems, to expose problems with the interfaces among program components before they occur.

3. The bottom-up process starts with unit testing followed by progressively higher level tests of combinations of units otherwise known as modules or builds. Top-down integration tests the highest-level modules first and progressively lower-level modules are tested thereafter.

[hupro]

1. Why do we write integration tests?
   The integrated test is design to catch integration errors or broader system-level errors, thus we write them to test the interaction between software units (modules).

2. What problems do integration tests solve?
   It makes sure that the functional requirements of the whole system are met and that there was no error in the functional requirements of the units (unintended behavior of a system).

3. What are the differences between top-down and bottom-down approaches?
   – Bottom-up testing approach : lowest-level to higher level, i.e. from the smallest units (modules) to the whole program.
   – Top-down testing approach : highest-level to lower-level.

[ClapTrap]

1. Integration tests are used to test the different program units 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. 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.

[BlockRationale]

1. Why do we write integration tests?
   These tests are written 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?
   The bottom-up process starts with unit testing followed by progressively higher level tests of combinations of units otherwise known as modules or builds.
   In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested thereafter.

[Captaincrypto]

Why do we write integration tests?
Because the units all need to be tested as groups first, then as a whole to ensure that they can function as required.

What problems do integration tests solve?
Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.

What are the differences between top-down and bottom-down approaches?
With bottom up testing after unit testing the highest level modules are tested and withi top down testing the highest level modules are tested first and progressively lower level modules are tested after that.

[Toby_K]

@ivan

• Why do we write integration tests?
• What problems do integration tests solve?
• What are the differences between top-down and bottom-down approaches?

1. To expose issues with groups of program units before they occur in user execution.
2. IT find problems of interactions between program parts.
3. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are being tested thereafter. In bottom-up integration testing, first all units are tested separately, followed by tests of progressively higher-level combinations of units called modules or builds.

[tarekhlb]

1. Why do we write integration tests?

Integration testing can highlight glitches with the different interfaces within a program before it is rolled out to the public.

2. What problems do integration tests solve?

Interface problems.

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

The difference between the two is the starting point of the testing. Top down starts with high level and drills down to the lower level modules. Bottom-up works in the opposite direction.

[Tordek]

1. Why do we write integration tests?
Units are combined and tested as groups in multiple ways.
2. What problems do integration tests solve?
Expose 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?
The bottom-up approach is usually done first. It starts with unit testing and is followed by testing unit combinations called modules or builds. In the top-down approach is it opposite where it starts with testing the highest-level modules first and then the lower levels.

[BlockRationale]

Why do we write integration tests?
Because the units all need to be tested as groups first, then as a whole to ensure that they can function as required.

What problems do integration tests solve?
Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.

What are the differences between top-down and bottom-down approaches?
With bottom up testing after unit testing the highest level modules are tested and withi top down testing the highest level modules are tested first and progressively lower level modules are tested after that.

[Mr.D]

1. They are written to automate something that otherwise would take a lot more time.
2. Exposes defects in the system and in the interactions between different modules.
3. Bottom-up begins with unit testing and progresses with progressively higher levels of combinations of units, Top-down starts in the other end with the highest level modules and works down from there.

[Web2Hotel]

1
In order to spot bugs affecting the interaction between modules (more units together).

2
Interface problems among program components, for example.

3
Bottom-up begins with unit testing up,
Bottom down tests all the program and then every functionality.

[AF90]

1. The purpose of integration testing is to expose faults in the interaction between units.
2. Integration tests help identify any faults between different components working together.
3. Top-down approaches testing from a higher-level and works its way down to more individual units of code. Bottom-up starts at the bottom with unit testing and works its way up toward higher-level code using integration testing.

[Understated_Eddie]

@ivan

1. Why do we write integration tests?
2. What problems do integration tests solve?
3. What are the differences between top-down and bottom-down approaches?

1. Integration tests are written to check if units work together when combined to work as a group. The idea behind it is to check is integrated units will prove faulty.

2. They look to solve whether interfaces between components work when assembled.

3. The difference of approach is that bottom-up integration tests will test lower level units first and progressively adding more top level units, while a top-down approach with test for higher level units first and progressively add lower level units. I will depend on the development approach and missing units will be simulated.

[Nev]

1. Why do we write integration tests?
   To ensure that all pieces of app work well with each other and as such app itself works
2. What problems do integration tests solve?
   How well pieces of software work
3. What are the differences between top-down and bottom-down approaches?
   Top down take the thole app and then test downward to the smallest testable part. Bottom up starts with unit testing then moves up

[cryptopunk]

1)units are combined to a group and tested in different compositions
2) we can find problems within the interfaces among program components. and we can test, if those components work fine together
3) in top-down you start with the higher level modules and work your way down to the underlying units, for example in a car-test, you check first the while and subsequently followed by tire, rim, hub. bottom-up is the opposite direction