Integration Testing - Reading Assignment

[PabloAAAJ]

Why do we write integration tests?

We write integration tests in order to find issues, bugs and problems with the application before implementing it on real world cases.

What problems do integration tests solve?

By performing an integration test we can find issues on any part of the process before implementing. It allows us to deliver a quality product to the customer (even though we might not find all bugs and feedback from the final user is always needed to solve all of them).

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

• Bottom-up approach starts testing the most granular level of the code or program (called unit), and then continues by testing higher level parts or modules
• Top-down approach is the opposite and starts testing higher modules first and continues testing the progressively lower modules.

[Lehigr2]

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 test the individual units as a whole to see if they will work together.
3. **What are the differences between top-down and bottom-down approaches?**In top down you test the highest level modules first and then work your way down. In bottom up you start with units and then work your way up with bigger and bigger combinations of units.

[Nathan_Burkiewicz]

1. Why do we write integration tests?
   We do integration tests in order to combine the indivudal components of an application and validate they work as expected and result in the desired behaviour.

2. What problems do integration tests solve?
   Integration tests help identify problems or potential bugs in an applications functionality before the code reaches the real-world application.

3. What are the differences between top-down and bottom-down approaches?
   The bottom-up approach starts with unit tests of the inidivudal application components before creating integration tests, while the top-down approach begins with integration testing of the sum of the indivudal units before moving on to unit tests.

[Jesse_Bowles]

1.it can expose problems with the interface before the user experience
2. If the code works with itself. Makes sure it runs completely
3. Bottom up starts with the last line of code and does a unit test back towards the start of the code making sure it all comply with itself. In the top down it takes the largest piece of code and then progressively tests smaller eices

[ibn5x]

1. We write integration test to check for proper functionality of software.

2. By running multiple test on the complete program designed to mimic what our software may encounter in the wild; clients, networks, systems or malicous actors. We can safe guard against exploits and identify any potential exploits in our software.

3. The difference between top-down and bottom-up approaches lye’s implemention. Top-down I&T we start by testing the highest level modules first, and proceed progressively lower. While in bottom-up I&T we begin with unit testing and proceed with progressivley high-level combinations of units called modules.

[charlesleonp]

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

2. What problems do integration tests solve? It makes sure program components work together without errors.

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 and top-down integration testing, starts with the highest-level modules and then tests progressively the lower-level modules.

[charlesleonp]

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

2. What problems do integration tests solve? It makes sure program components work together without bugs.

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 and top-down integration testing, starts with the highest-level modules and then tests progressively the lower-level modules.

[deniselbs]

1. Why do we write integration tests?
To test the combined components together, and then to see if they can also work together.

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?
Bottom-up integration testing begins with the lowest level and then continues with the higher level.
The top-down integration testing starts with the highest-level and then followed by the lower levels.

[godi]

1. Why do we write integration tests?
   To test and see if all the individual components will work today.

2. What problems do integration tests solve?
   To see if the application works in real life.

3. What are the differences between top-down and bottom-down approaches?
   Bottom-up approach starts with unit testing before integration tests whereas top-down is the opposite.

[Aida1]

Kindly asking for help, how i can open the article for this assignment?

[gregD]

1. We write integration tests to check the code works in real life situations, when different components are combined in actual use cases.

2. Integration tests solve problems with the interfaces between different components of the source code.

3. A top-down approach starts with testing the complete application and then testing smaller components afterwards. A bottom-down approach is the other way around.

[thecil]

Hey @Aida1, hope you are ok.

Did you mean this lesson? cuz it does not have any lecture, or it should be one?

https://academy.ivanontech.com/lessons/integration-testing

Carlos Z

[Kristian_Mitov]

1. Why do we write integration tests?
   It can show problems in real world before it happens
2. What problems do integration tests solve?
   Problems with the interfaces among program components
3. 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.

[Harold]

1. Integration tests are complex so have to be structured in order to be undertaken efficiently.
   2a) This testing makes sure that the integrated modules/components work properly.
   2b) It detects the errors related to the interface.
   3a) Bottom-up testing, as the name suggests starts from the lowest or the innermost unit of the application, and gradually moves up
   3b) This technique starts from the topmost module and gradually progress towards the lower modules. Only the top module is unit tested in isolation.

[C.Higbee]

1. Why do we write integration tests? to make sure the units can function together
2. What problems do integration tests solve? it will detect errors when the units work together
3. What are the differences between top-down and bottom-down approaches? top down starts testing high level components first then followed by the low level. Bottom-down is the opposite.

[Alex_13]

1. Why do we write integration tests?

Integration testing is used to test the compliance of logically integrated groups of software components with specified functional requirements. Integration testing comes after unit testing and tests whether the interaction between the individual software components within a group works properly. This means that the main focus is on testing the interface and the flow of data between the components that are grouped together. Subsequently, larger group of components are formed and their interaction is tested until the whole application is tested as a whole. This makes it possible to detect any bugs that occur when groups of components interact with each other.

2. What problems do integration tests solve?

Integration testing focuses on the interaction between individual software components of an application and is intended to solve any problems related to the data flow between those software components.

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

Top-down:
Software components are tested according to the control flow of the software system. Higher level components are tested first and subsequently lower-level modules are tested and integrated in order to test the functionality of an increasingly larger group of components.

Bottom-up:
Lower-level components are tested first and are then logically grouped together to form the next level of grouped components to be tested. This process continues until components at the top level have been successfully tested and can be integrated into the whole application.

[Damedius]

1)We write integration tests because they can expose problems with the interfaces among program components before trouble occurs in real world program execution.

2)They find problems before the software is integrated and used in the real world.

3)In top-down testing, the highest level combinations are tested first and then progressively lower levels. In bottom-up testing, you test individual units before progressively testing up.

[jude]

1. We write integration tests so that we could see how the individual components integrate with the overall software and to check for problems by mimicking the real use of it, before it goes for deployment.
2. Integration tests solve problems of coordination, workability of one piece with another in a software.
3. The difference between a top-down and bottom-up approaches is that top down tests the highest level modules first before the individual units, while the bottom-up is just doing exactly the opposite.

[kwaben]

1. Why do we write integration tests?
   To test if a given set of components in an application that have been unit tested, will behave together as expected.
2. What problems do integration tests solve?
   Inter-operability between components and interfaces.
3. What are the differences between top-down and bottom-down approaches?
   Bottom up starts with the smallest combination of units and progressively increase the number of components until the entire application is testeded in one go.
   Top down starts with the whole component and breaks them down progressively untill the least number of components is tested

[MrAndres]

1. Why do we write integration tests?
   We write integration testing because it can identify issues with interfaces between program components before problems happen. It is done after Unit Testing.

2. What problems do integration tests solve?
   Integration testing is carried to evaluate the compliance of a system or component with specified functional requirements.

3. What are the differences between top-down and bottom-down approaches?
   *In the Top-Down approach, Integration testing will check the highest-level modules first, following the lower-level modules, testing later the software functionality

The Bottom-Up approach will begin with Unit Testing and followed by the test of lower-level modules. These tested modules are then additionally used to facilitate the testing of higher-level modules. The process continues until all modules at the top level are tested.*