Integration Testing - Reading Assignment

[Lisalazuli]

1. Why do we write integration tests?
   It’s part of extreme programming to test for how the individual components of programs interface together. Every program is made of of smaller units then grouped into modules and we need to understand if they all work cohesively and deliver a desired result.
2. What problems do integration tests solve?. You can quickly decipher which components clash or do not interface correctly.
3. What are the differences between top-down and bottom-down approaches?. Bottom up is usually the first process and it involves testing the tiniest component program first, then the immediate interfaces of that program, then how various modules work together and eventually how the whole system held together. Top down is testing the end product as a whole and then working your way down so you finish by testing the smallest cogs in the system.

[Cr1ptoM]

@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 assure that all the components of an app or system works fine between each other
2.- Can expose problems with the interfaces and the communication inter layer
3.- Bottom up starts with the individual components and then test the hole solution.
Top down starts with higher level modules first, then to the lower level ones

[matty.t]

1. To identify any problems that arise before executing the program in the real world
2. Expose problems with the interfaces among program components before issues occurs in real world programming execution
3. Bottom down approaches starts from unit testing, followed by tests of progressively higher level combinations of units called modules or builds. Top-down is the opposite of the bottom down approach. It tests the highest level modules and works its way down to lower level modules.

[MSeeman]

1. In efforts to test the functionality of software prior to release

2. Exposing problems with the interfaces among program components before trouble occurs in real-world program execution

3. Top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that.

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

[Wade]

1. To expose problems with the program before it is used as an end product.
2. Generally they solve problems with interfaces between the units.
3. Top-down tests go from complex(modules) to basic(units) whereas Bottom-up goes from basic units to complex module testing.

[carmen1408]

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

2. They identify problems with the way different problem components interact with each other.

3. In top-down integration testing, the highest level modules are tested first and progressively lower-level modules are tested after that, while bottom-up integration testing begins with unit testing followed by tests of progressively higher-level of modules.

[Thijs.Smit]

1. Why do we write integration tests?

• Integration testing exposes possible problems with the interfaces among program components before trouble occurs in real-world program execution.

2. What problems do integration tests solve?

• problems with interfaces between units or actors in software

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

• in top down higher hierarchy is tested first and then lesser units. (Bottom up is reversed)

[Woodz]

1. So that we expose the potential bugs and errors among code’s components before a certain app/tool goes “live”.
2. Interface issues among program components.
3. Top-down approach implies testing higher modules of the code first gradually moving to the lower ones. Bottom-down approach is vice-versa - starting the integration testing with the lower unit-testing moving to the higher level combinations of units (modules or builds).

[Byron]

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

2. The main aim here is to test the interface between the modules.

• It makes sure that integrated modules work properly as intended
• The tester can start testing once the modules to be tested are available
• It detects errors related to the interface between modules
• Helps modules interact with API’s and other third-party tools
• Typically covers a large volume of the system, so more efficient
• Increases the test coverage and improves the reliability of tests

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.

[Sherms]

1. Why do we write integration tests?

To test multiple units in many different ways.

2. What problems do integration tests solve?

Integration test can expose problems in the interface before trouble occurs in real-world program execution.
3. What are the differences between top-down and bottom-down approaches?

The direction of the testing. Bottom-up starts with the unit then you scale up with testing. While top-down beings with the application then you scale down with testing.

[kath7lee]

@ivan

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

• Why do we write integration tests?
  Answer - we write integration tests to ensure that errors or bugs are captured at the interface level during testing before deploying the code base to production.

• What problems do integration tests solve?
  Answer - integration tests catch or solve any bugs when integrating components and when building combination of unit test cases.

• What are the differences between top-down and bottom-down approaches?
  Answer - top down is the process of testing higher level components and then testing the lower components or units next.
  bottom-down is the process of testing individual unit test cases first then combining the unit test cases together next.

[katarzynagr1]

1. Integration tests are designed to expose potential problems with interface among the application components. We run the tests to solve the problem before it occurs in real-world.

2. Integration test detects if integration of different units can create any problems/errors

3. In Top- down we test the highest level module firs and follow with lower level modules to the bottom. The bottom up is just the opposite - we test the lowest (simplest) modules first until we get to the top.

[monymike]

1- In order to see if the components work as expected when each is integrated and to find and fix early in the process any problems.
2- It can expose problems with the interfaces among program components before trouble appears in real world program use. It seemed the article had the best way of explaining this as I copied .
3-With top down integration testing we look at the highest level and gradually go down the to lower levels to see the intigration of the units work well or any problems that are identified can be fixed
Bottom up testing is done first, which only makes sense, is the unit testing , are all the units giving us the result we expect…And as mentioned before, the small problems get fixed first.

[stephenK]

• Why do we write integration tests?
  Integration testing is written because it can expose problems with the [interfaces] among program components before trouble occurs in real-world program execution.
• What problems do integration tests solve?
  They test the functionality of software.
• 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.

[Agnie]

1. Integration tests are written to test combined program units.
2. Integration testing solves the problem related to interfaces between program components.
3. Bottom up integration testing starts with testing of the individual units, and then testing of the combination of units (modules) at higher level. Whilst, the top down integration testing starts with the highest level module testing, and then testing modules and units on lower levels.

[ArtCenter1]

• Why do we write integration tests?
  To make sure all the components work together
• What problems do integration tests solve?
  To test to see if individual working unit works well together under real world cases.
• What are the differences between top-down and bottom-up approaches?
  Top-down method start with the higher level integration test first before unit testing Bottom-up method reverse that progressively.

[yositsitsu]

1. Why do we write integration tests?

We want to make sure, that the functional units are functional as a whole, when part of the true integrated eco system

2. What problems do integration tests solve?

Integration issues
Units might be completely functional by themselves, but once combined, suddenly things go wrong.
Those are the case, integration test strive to pinpoint and solve

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

In Top down, we start at the bigger components level (say, the whole app) and drill down to the smaller units

In Bottom up, we fo the other way - start at the unit level, and combine them into bigger and bigger components until the whole system is tested

[JBrewer]

Why do we write integration tests?
– to expose problems with the interfaces among program components

What problems do integration tests solve?
– to isolate issues before trouble occurs in real-world program execution

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.

[ghiasi12reza]

1. to test all programs combined and check the integration process in multiple ways

Functionality of the software

3. bottom up integration testing, you start with units and combine them in smaller modules and build up.
   top-down testing, you start testing the biggest modules first, and then work your way down to smaller and smaller modules.

[Nicksta]

1. To find problems with the interfaces among program components before trouble occurs in real-world program execution.

2. The integration of smaller units in the bigger software components

3. Top-down starts with testing the whole application how an enduser would use it and working the way down with testing the smaller units / components of the system. Bottom-up approach starts with smaller units / components testing untill you reach the highest level of the whole application.