Integration Testing - Reading Assignment

[Valdis]

1. Why do we write integration tests?
   To check if the units of the program still work when integrated in the whole.
2. What problems do integration tests solve?
   They allow to pick up higher (than unit) level problems that might occur between units when in use.
3. What are the differences between top-down and bottom-down approaches?
   The top-down, it just occurred to me that it could be called ‘feeling lucky’, starts with an integration test and assuming that all the units are perfect could save time. In real life though there are always bugs and bottom-up is mostly used where you start with testing the units and only afterwards run the integration test. If the project is huge and complex the hybrid method would make more sense where you just test the code blocks affected by changes and then try the integration test.

[Goosie]

1. Why do we write integration tests?
   because we want test not only the components. We want test all the components together as well.

2. What problems do integration tests solve?
   The problems which occur when all the components are merged together.

3. What are the differences between top-down and bottom-down approaches?
   top-down: the test will be done on the software as a whole, it following the first big user lines.
   bottom-up: it will test the functions and the components first before the software is tested a whole.

[Jonny]

1. Why do we write integration tests?

• To test if the software works correctly on multiple levels of decomposition into smaller units

2. What problems do integration tests solve?

• Creating the correct interaction between units which have already been tested themselves

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

• The bottom-up approach starts with testing the smallest testable parts of the application and then test how they interact to form larger units and so on until you are testing the whole application. Top-down starts with the highest level and its testing move increasingly closer to the smallest parts.

[davidnachman]

1. Why do we write integration tests?
   We write integration tests to check if all smaller components function together as a whole.
2. What problems do integration tests solve?
   Integration testing can expose problems with the interfaces between program components before trouble occurs in a 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 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.

[paschkka86]

1. We write integration tests, because we want to test the unit first before integrate it into the module.

2. With integration testing, its possible to expose problems between units in a safe environment before they make trouble in the real-world.

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

   • Bottom-up, starts the test with the smallest part (unit) and than move up to the next level and checks the combined units, move up to a bigger combined module…
   • The top-down approaches starts with the complete module and than moves down into more and more detail and also smaller testing code

[DKSA]

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

Bottom-Up - Unit testing to identify problems in the smallest unit first
Top-Down - Following unit testing, to test complete application in scenarios designed mimic encounters in customer computers, systems and networks.

[dave-dave]

*Why do we write integration tests?
To make sure that different components of the code work together.

*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?
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.

[AliasFresh]

1. Why do we write integration tests?

while the unit test is about individual code the integration test is about modular interaction and functionality of complete builds.

2. What problems do integration tests solve?

A change in a single unit can affect how a module and or the entire system behaves. Integration tests specifically help identify and solve errors/glitches (if any) that arise when two or more modules Interact.

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

The top down Approach starts with the highest level complexity of code and works back to the smallest unit looking for errors

the bottom down Approach should read Bottom up approach and that meathod starts with individual units of code and then moves up the ladder of complexity to modules and eventually complete builds.

[crackingcrypto]

1. Why do we write integration tests?

Try and expose problems within larger groups of code before they’re published to the public.

2. What problems do integration tests solve?

Problems within interfaces and programming components that may otherwise work fine on their own.

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

Bottom-down is usually done first. Starts with smallest bits first so that you can more easily isolate potential issues. Top-down is more so after you’ve done bottom-up. This way you can test both when components are isolated and joined together. From both directions.

[tanja]

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

2
Integration tests and unit tests both test the functionality of software, check for errors in the code, application, interoperability, …

3
Bottom-up integration testing begins with unit testing (from low to high), followed by tests of progressively higher-level combinations of units called modules or builds. Traditionally, this is done first.

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

[mkhuang]

1. Why do we write integration tests?
   a process which program units are combined and tested as groups in multiple ways.
2. What problems do integration tests solve?
   It 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?
   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.

[Thaddeus19]

1-Why do we write integration tests?
To be able to test all the complete software since it is a good practice to test units but we do nothing but know if joining all the modules will respond the same.

2-What problems solve the integration tests?
That by joining the different modules (set of units) we can see the response and how they work together and identify faults or poor performance when joining them and thus be able to correct them.

3-What are the differences between top-down and bottom-down approaches?
to-down is tested from the macro (modules) to the specific (each unit). On the other hand, in bootn-down we start testing from the units until we reach the modules and the complete interfaces.

[cryptokaritz]

1. Integration testing is done to solve problems that appear when multiple system units are working together. Tests are written to standardize testing, automate testing, make testing more efficient, and enable continual testing and revision.
2. Integration testing can find interaction errors between component interfaces and errors on multiple levels in the program.
3. Top-down integration testing starts at the highest level of the system and becomes more granular as the testing progresses to individual components. Bottom-up integration testing starts at the unit level and expands in scope as the testing progresses.

[Ray]

1 With integration test we can test all the components of program and make sure there is no bugs left.
2 They help to prevent bugs and mistakes, before program ready to go live.
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.
In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested thereafter.

[laketravisgirl]

1. We write integration tests to make sure combinations of sections of code work together properly.
2. Integration tests exposes any problems when certain combinations of sections of code do not work together properly.
3. Top-down is to test the larger sections/modules first then smaller individual units. Bottom-up is to test the individual units first before larger sections/modules.

[Chantal]

1. We write integration tests in order to check that the different components can work together.

2. Integration tests solve the need to identify bugs who don’t affect one precise function but affect a group of functions or a process.

3. In bottom-up testing we begin with unit testing and then we test combinations more and more complex. In top-down testing we test the more compex combinations (complete processis and interfaces) and then we test less and less complex combinations of functionalities. We can do both : bottom-up and then top-down testing, and then we lastly do the complete scenario in order to mimic the real customers’ experience.

[lbjenious]

1. Why do we write integration tests?

• To create a development process which program units are combined and tested as groups in multiple ways.

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.

1. What are the differences between top-down and bottom-up 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.

[Fairway]

1. Mostly to test the interfaces between the units and modules.
2. Unexpected interactions between programming functions/procedures from a real life situation.
3. Top down is from general to more specific function testing. Bottom up is gradually integrating more units of code.

[sponur]

1. Intergartion testing is a software way in which a series of unit tests are combined and tested as groups in multiple ways

2. Intergartion testing can show problems in the interfaces and how it performs with the program components

3. Bottom up testing means the most basic code functions are unit tested first and then the more progressively complex code tested
   Top down the more high level modules are tested first, with lower level modules tested after that

[Jonathan19]

1. We write integration tests to expose problems among program units before trouble occurs in real-world program execution.

2. Integration testing solves problems that occur in interactions between individual units of the code.

3. Top-down testing tests the code against real world use cases to ensure that the program as a whole works properly. Bottom-up testing first tests units of the code to make sure they work properly before testing against real world scenarios.