Integration Testing - Reading Assignment

[skissane]

1. Integration tests are run to combine and test program units 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 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.

[guso]

1. Why do we write integration tests?
   To test if the units work when they interact with each other and not just in a vacuum.

2. What problems do integration tests solve?
   If the units work when they interact with each other.
   Can help fixing the issues before they appear on main code.

3. What are the differences between top-down and bottom-down approaches?
   Top-down breaks down core modules to small modules.
   Botton-up is analysis starting from small to core modules.

[sneakyturtle]

1. Why do we write integration tests?

To test is there are flaws in the different interactions of the units of the software. It could be that different units are written by different programmers. Both programmers might follow a different logic. An integration test is then needed to figure out if these units work together.

2. What problems do integration tests solve?

It checks it the logic of a developer works as expected and the integrated components of the software work properly. It can detect errors related to the interface. Integration tests increase coverage, make it easier to isolate failures and can find system level issues.

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

In the bottom up approach testing makes use of stub while in top down approaches drivers are used. In a top down approach top level units are tested first and testing moves down to lower levels step by step. In the bottom up approach testing starts with the lower level units and then moves up step by step.

[Nickpuna1]

1. Integration testing can expouse problems with the interfaces among program compounds before trouble occurs in real world program execution

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

3. Top-down : You start with main functions and create sub-functions
   Bottom-up : You start with moduls that you layer integrate with main functions

[WoolyBully]

1)To test larger modules (combined units)
2) it can expose problems with the interface among program components before trouble occurs in real world program execution
3) bottom up approach start with unit testing, top down start with highest-level modules

[Roel]

@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. these tests can expose problems with the interfaces among program components before trouble occurs in real-world program execution.
2. problems with the interfaces among program components
3. in bottom-UP approach the units are tested first, then modules, after testing all modules the whole program will be tested. Testing is up in hierarchy. Top-down will test from the whole program down to units.

[Dogge]

@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. Why do we write integration tests?
   To ensure that the system as a whole is operating as it should be.

2. 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

3. What are the differences between top-down and bottom-down approaches?
   Top down is from general to more specific function testing. Bottom up is gradually integrating more units of code.

[chakrit]

@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. To ensure that the entire source code written for a project works well together.
2. The interaction between different software modules which cannot be tested solely in unit tests.
3. The top-down integration testing, the highest-level modules are tested first and then progressively lower-level modules ones. The bottom-up process starts with unit testing followed by progressively higher level tests off combinations of units otherwise known as modules or builds.

[Dirk]

1. to ensure that all units work together and the overall result is correct
2. IT should check if the combination of all implementation parts work properly together and the final results are reached
3. top down approach begins with high level design and ends with low level development. Whereas, bottom up approach begins with low level design/development (units) and ends with high level design.

[manted]

1. Why do we write integration tests?
   So we can run tests and see if units are cooperating as expected.

2. What problems do integration tests solve?
   We can see if there are some unexpected interactions between units.

3. What are the differences between top-down and bottom-up approaches?
   top-down we are testing highest modules first and then smaller units.
   bottom-up we are testing smallest units first and going up to bigger modules

[coinarura]

1. Why do we write integration tests?
   Integration testing is done to test the modules/components when integrated to verify that they work as expected i.e. to test the modules which are working fine individually does not have issues when integrated.

2. What problems do integration tests solve?
   Performing integration testing offers a lot of benefits. Some of them are listed below:

• 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. What are the differences between top-down and bottom-down approaches?
   Top - down approach decomposes the large task into smaller subtasks whereas bottom - up approach first chooses to solve the different fundamental parts of the task directly then combine those parts into a whole program. Each submodule is separately processed in a top - down approach.

[Edward_Valencia]

1. Why do we write integration tests?
   To test the code as a whole and see all interfaces linking the components.

2. What problems do integration tests solve?
   Problems that arise when the entire application is being used. The application should be able to carry out individual along with dynamic functions without breaking. It should simulate a real-world working application for people to use.

3. What are the differences between top-down and bottom-down approaches?
   Top-down is when testing starts at the higher level and works its way down. Unit testing is a for of bottom-down testing where individual functions are tested. Top-down should be implemented last when developers are confident that all functions work together as well as apart.

[travis_bazile]

1. We write integration test to test out all the codes on the application are working. As well as checking the interface linkage codes to ensure there are no bugs in the system.
2. integration test locate errors on the complete use of an application. they also run multiple sub test within the application to check in its entirety that everything is working fine.
3. as the name suggest. bottom-down refers to starting from ground level and working your way up to test all the code. top-down starts with the most difficult and works its way down.

[thecil]

Excellent answer sir! really well documented! keep it like that please!

Carlos Z.

[massam78]

1. Why do we write integration tests?
   Integration tests are written and executed for functional interactions which typically crosses boundaries, to expose problems with the interfaces among program components.
2. What problems do integration tests solve?
   Interoperability between systems, to expose problems with the interfaces among program components before they occur.
3. What are the differences between top-down and bottom-down approaches?
   Top-down starts high level functional test cases, or user scenarios. Bottom-up integration testing begins with unit testing, followed by tests of of progressively higher-level combinations of units called modules or builds.

[odesseus011]

1. Why do we write integration tests?
   To combine program units and test as a whole.

2. What problems do integration tests solve?
   To expose problems with interfaces before problems occur in real world usage.

3. What are the differences between top-down and bottom-down approaches?
   Top-Down - High level components or units tested first.
   Bottom-Up - Low level components or units tested first.

[Tristan01]

1. To ensure that the different components can work together
2. these tests help to prevent unpredictable and unacceptable reactions of the system at all levels
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. The bottom-up testing is usually done first, followed by top-down testing

[DFig]

1. To expose problems with intefaces among program components before hitting production.

2. The test exposes problems that may occur with interactions between systems

3. Top-Down - High level components or units tested first and then followed by low level components.
   Bottom-Up - Low level components or units tested first and then followed by high level components.

[Ed1]

• **Why do we write integration tests?
  To test the end to end process between all involved components.

• What problems do integration tests solve?
  It makes possible issues visible between different components in the process frontend, middleware and backend for example.

• **What are the differences between top-down and bottom-down approaches?
  Top-down the highest module are tested first before going to the lower levels.
  Botton-down first lower level modules before going up.

[HexagonalView]

1. Why do we write integration tests?
   The scope of integration tests is to identify issues with the communication between different software components, before the end-to-end tests are run.
2. What problems do integration tests solve?
   It helps refine the integration between components.
3. What are the differences between top-down and bottom-down approaches?
   In the top down approach the high level modules are tested initially and then and progressively lower-level modules. Bottom-up integration testing starts unit testing and then followed by tests of higher-level combinations of units (also named modules).