Integration Testing - Reading Assignment

[Mesiah]

1. Why do we write integration tests?
   A: To help fin problems in the program’s interface while making the project

2. What problems do integration tests solve?
   A: It finds any issues between the systems that are integrating with each other

3. What are the differences between top-down and bottom-down approaches?
   A: top down is a high level test of modules first to identify problems between the system and user bottom down works it way up to higher levels of test with module builds

[CryptoRealNews]

1. We write integration tests to see if all the individual modules (that passed their individual unit testing) actually work together as required.

2. Integration testing picks up any bugs or incompatibilities when all modules run together even though individually the modules work fine.

3. Top-Down - starts with the global high level view and works down to the lower level unit level.
   Bottom-Up - Is the exact reverse approach, starting with Low level detail view, typically from where incoming data first enters.

[Yesyes21]

1- To ensure that all the code that makes up the application and also all the interfaces linking all the components together.
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 unit testing individual functions and work upward.

[aryakrishna]

1. to evaluate the compliance of a system or component with specified functional requirements
2. the difficulty of finding hidden problem when the programs are already running
3. the bottom up look from the most fragile command down in the bottom up to the stronger function of programs, while the top down to the other way around.

[Neeraj_Nerlekar]

1. Integration Testing is a meticulous approach to building a product employing continual testing and revision.
2. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.
3. In 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 progressively higher-level combinations of units called modules or builds.

[Crypto_Mofo]

1. Why do we write integration tests? To ensure at the system components work well together
2. What problems do integration tests solve? It demonstrate the system component works in a real world test.
3. What are the differences between top-down and bottom-down approaches?
   Top-down approach: Starts at the simplest form and analyzed the components to its detailed form.
   Bottom-Up approach: Starting at the complex form / low level (Hardware,Bit,Code) analyze to the simplest form.

[Calle_Jansson]

1. To expose potential errors with the interfaces before any problems occur in real-time execution.

2. They solve the functionality of the software, and they solve the potential exposure of errors with the interfaces in the program components.

3. The top-down approach take the testing from the top and continues down through the components until it has tested the individual units of code.
   The bottom-up is the opposite to the top-down approach. It tests the units of code from the bottom to the top, individually.

[SatoshiOkoto]

• Why do we write integration tests?
  To see if all components also work simultaneously.
• What problems do integration tests solve?
  It tries to solve the way systems are interacting with each other.
• What are the differences between top-down and bottom-down approaches?
  With the top down approach you start with the biggest most complex code and work your way to the smallest units and with the bottom down approach you work the other way around.

[NetworkP]

1 Why do we write integration tests?
We write integration tests as this provides us more of a complete and continual testing procedure compared to unit testing. Unit/modules are grouped and tested in multiple ways within the Integration testing process.

2 What problems do integration tests solve?
Integration tests solve problems such as interface and program component issues. It’s to mimic the experience of the customer’s experience.

3 What are the differences between top-down and bottom-down approaches?
Bottom-up tests for higher level of combination module testing after the unit testing whilst Top-down tests for higher level combination first and lower modules after resulting in continual testing of the complete application.

[timtim]

1. Integration tests are being written to check that components that work well individually work as well when they are integrated.

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

3. Bottom-up approach starts with unit testing, and then progressively moves from low-level to higher-level combinations of units. Top-down approach starts progressively from higher-level towards low-level.

[Fabiana]

1. Integration tests is useful to test all the complete software and make sure that there are not bugs.

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

3. Bottom-up approach starts with unit testing first and later it moves on to the higher level combinations while the top-down approach tests the higher level combinations first and later it moves on to the lower level after.

[pepemadrid]

1. We write integration tests, because you can put together the different components and see if they work correctly.
2. They solve problems that have to do with the interaction of the different modules and components.
3. Yo start with the main functions and go the into details in top-down. In bottom-up you go from the smaller componentes to the bigger ones.

[harry]

@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. Writing integration tests allow all individual modules with their data transfer to be tested thoroughly in order to make sure all components are in sync.
2. The problems integration solve are real world use case such as balance module and transfer that bank use or exchanges. When transfer are made then the balance should be updated and so forth and check if any error involved.
3. The different between top-down and bottom-up approaches is that the former start testing from the top level first and then step by step after that, also creating stub module to simulate component that are not ready during the process. For the bottom-up approach usually starts testing first from the bottom and step by step up as well as creating driver module to do simulation, minimizing time consuming projects.

[Christophe_H]

1. We write integration test to know how individual units of code behave when run together
2. Module level testing
3. Top-down approach may require studs and bottom-down approach may require driver when the software is not fully written. The approaches also:

• Detect different types flaws
• are efficient at different moment of the life cycle

[blue]

1.Why do we write integration tests?
so problems can be identified with the interaction with other program components before it is sent out into the real world
2.What problems do integration tests solve?
ensures that all the units and modules work together as a whole
3. What are the differences between top-down and bottom-down approaches?
Bottom up testing begins with unit testing followed by test of progressively higher level combinations of units; usually done first followed by top down testing.
Top down testing begins testing the highest level modules and then progressively lower level after that

[Maximus]

@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. Test are written and used to test the interface or code is working perfectly. This can be done in sections or on a larger scale ,like integration. The goal is to fix bugs and errors before launching or continuing with the next section of the code. If it is left the bugs and error can affect other sections or functions,can be harder to find.

2. They identify bug,errors and the way interaction of different program components interacts with each other.

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, followed by tests of of progressively higher-level combinations of units called modules or builds.

[jdbarrancs]

1. We write integration test so that we make sure everything can run simultaneously.

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

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

[CSquared]

• Why do we write integration tests?
  It is the testing approach where all groups of overall development are tested together. Depending on the complexity of the project it can consist of different software layer e.g. Back End, Front End, Client Interface, Networks, Middle ware etc. It enables us to see how the smaller (unit) components interact as a whole and how it would perform in a real - world scenario

• What problems do integration tests solve?
  It enables one to proactively determine challenges as well as errors, performance related issues etc that will or will likely occur due to the interaction of the various smaller components or group of smaller components.

• What are the differences between top-down and bottom-down approaches?
  Top-Down starts with testing the highest overall level(s) of integration down to the individual testable unit components while Bottom-Up is the reverse and starts from unit testing upwards to the overall integration level

[Bunbo_Hue]

1. Why do we write integration tests?

Integration tests are important because they allow us to ensure that individual units are interfacing together correctly, before real world problems occur regarding the integration between two units/modules (is there a difference between units and modules?)

2. What problems do integration tests solve?

Problems between different systems interacting with each other. This will ultimately ensure that the program can work as a whole by eliminating integration issues between units.

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

Top down starts with the highest level modules being tested first, working its way down to the individual units.

Unit testing makes it so that each unit is tested individually before working up to the higher level modules.

[stonedakilla]

• Why do we write integration tests?
  to test the complete application in all its processes including all the implemented elements and modules
• What problems do integration tests solve?
  Unexpected interactions between programming funcitons/procedures in the implemented processes
• What are the differences between top-down and bottom-down approaches?
  Bottom-up approach >> testing units first then proceed to higher-level combinations of units called modules or builds.
  Top-down approach >> testing highest-level modules first followed by lower-level modules.