Integration Testing - Reading Assignment

[Paultier]

Integration Testing - Reading Assignment

1. Why do we write integration tests?

• testing a group of units in multiple ways

2. What problems do integration tests solve?

• expose problems with the interfaces among program components

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

• Bottum-up integration testing: begin with unit testing followed by testing higyer level unit groups and modules and builds
• top-down integration testing: highest level of module is tested first and the lowest unit at least.

[KamilK]

1. Integration tests are necessary for testing individual units combined in groups…
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.

[rkindle]

1. Why do we write integration tests?
   To expose issues of interfaces between the components or units of a program. They are used to test multiple units in their combination, so called modules.

2. What problems do integration tests solve?
   They allow to test how units and modules are working together and expose incompatibilities and errors in the interfaces in between them.

3. What are the differences between top-down and bottom-down approaches?
   The top-down approach does test first the higher level modules and work its way down to the individual units whilst the bottom-up approach works the opposite way round. Usually the bottom-up approach is done first.

[Adam]

To test all the components of a programme.
The ensure that components (units) work together.
Bottom up begins with units then modules, top down begins with the programme and works down.

[moragarcia75]

1. Why do we write integration tests?
   To make sure the program works as intended.
2. What problems do integration tests solve?
   To find errors.
3. What are the differences between top-down and bottom-down approaches?
   top-down - Goes from highest level of the application to the lower level modules.
   bottom-down - Goes from unit testing and continues to the highest module of the application.

[BlogChain_Charles]

To verify the integration of modules or units of software, if links between them respond accordingly, to prof usability of the interface, to avoid bigger issues down the line.
2.
Solve problems in a still early stage of development, such as mal-communication between components of the software, the bad linkage between modules, poor integration, interface errors.
3.
Top-down testing allows verifications of proper execution of components ready in the admin/driver level while awaiting completion of bottom level parts, using a scrub dummy as lower-level part to interact with during testings; A bottom-up approach uses of a dummy drive to start testing of the bottom parts components, while still awaits the bottom-up part to be finished.

[Cryptotherapy]

Integration tests see if the code involved in interoperability works and if not, reveals where the bugs are. Integration tests find errors in the running of the application from start to finish. Bottom up testing starts at the most basic unit of code. Top down tests the more complex units of code. Start with the bottom up approach to optimize testing.

[CryptoLee6]

1. To make sure that different components/units of the code work together.
2. Integration tests help determine if the unit works with the rest of the program or code.
3. Top-down starts by testing of main functions and modules, and works downward
   Bottom-up starts with unit testing individual functions, and works upward

[biffen96]

Why do we write integration tests?
To combine program units and test them as groups in multiple ways.
What problems do integration tests solve?
Expose problems with interfaces among programs components before trouble occurs in real-world execution.
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.

[TIMMSY1]

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?
   To expose any bugs that may occur on a live system before they occur.
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.

[thecil]

1. Why do we write integration tests?
   To determine a component behave when is executed with other(s) component(s). This will give us an idea of what kind of issues might appear to fix them before deploying it in the main code.

2. What problems do integration tests solve?

• Successfully verified integration with other components.
• Designed environments to review a component behave.
• Efficient method to solve issues before they appear on main code.

3. What are the differences between top-down and bottom-down approaches?
   Top-down: Analysis starting from core modules to small modules.
   Botton-down: The opposite of top-down, start from small to core modules.

Example:

TOP-DOWN:

1. Core Modules
2. Interface Modules
3. Calculation Modules
4. API Modules

BOTTON-DOWN

1. API Modules
2. Calculation Modules
3. Interface Modules
4. Core Modules

[CryptoVic]

1. Why do we write integration tests? “Intergration testing is conducted to evaluate the compliance of a system or component with specified functional requirements.” -wikipedia
2. What problems do integration tests solve? “Functional tests answer questions like, Does this feature work? or can the operator do this? Performance, stress or endurance tests are often used when exercising the system outside the bounds of standard situations or settings.” - IDT
3. What are the differences between top-down and bottom-down approaches? In bottom-up testing the “lowest level components are tested first, then used to facilitate the testing of higher level components. In top-down approach is where the top integrated modules are tested and the branch of the module is tested step by step until the end of the related module.” - wikipedia

• P.S. The phrase in question #3 “bottom-down” should be “top-down”.
  Also, FYI, the link:https://searchsoftwarequality.techtarget.com/definition/integration-testing did not allow reading of the article, “What is integration testing?” without a corporate address and registration. I consulted other sources to answer the questions.

[crusader2]

1. Integration tests is for the purpose of testing the program with user interface or program with another program to ensure all scenarios are working properly.

2. Integration tests can resolve user interface, program components, computers, systems and network issues.

3. Top-down approach tests the highest-level modules first and follows by the lower-level modules.
   Bottom-up approach tests the lowest-level modules first and follows by the higher-level modules.

[Dejan]

1. Why do we write integration tests?
   • To test the working of a collection of units that make up a larger part of the application (if not the entire application).
2. What problems do integration tests solve?
   • The functioning of the application consisting of a sequence of units.
3. What are the differences between top-down and bottom-down approaches?
   • Bottom up is generally the first part of integration testing, where you start with the smallest unit of the application and gradually test larger collections of related functioning units. Top down is the other way around, and generally is performed after bottom-up testing is completed.

[Alexander_Scholten]

• It can be considered almost an extension of unit testing. After a unit is tested, integration testing can determine any problems with the implementation of the feature (unit)
• Integration tests help determine if the unit incorporated ‘play’s well’ with the rest of the program or code.
• bottom down mainly focuses on the feature and outbound dependencies of the feature being implemented. Top down, is more of a systemic overview once the unit is implemented.

[Jimo]

1. In order to get single units togheter there are an interface between each unit that are tested before testing the entire program/sotware you build.

2. It’s to find out that units in interact and run togheter as expected.

3. The bottom-up principle mean that you test single unit first and go up yo the top layer and test how the entire software run as final part of testing. Top-down is the opposite way where you test a single unit as last part of testing.

[Kieran]

1. Integration Testing [or I&T] involves bespoke Integration Tests being written to ensure that the larger component parts [grouped units] of a project actually work together properly, and properly integrate with each other.

2. They allow issues to be resolved in testing, before a system goes live.

3. Bottom Up testing allows the most basic component parts to be tested, with additional modules or parts being added and retested, before more are added and the complexity of the system is built up. In this way, each build can be run and tested before further builds are added. Top Down testing, on the other hand, is testing from the highest level modules at the top of the stack, and moving down. Bottom up testing is usually done first, and a mixture of hybrid testing is usually employed.

[illyushin]

To know if the code as a whole is functioning correct and sort out interface problems if they appear

Interface errors detection
Interaction problems between program components/systems

Top-down: Starts with main functionalities and end up with low level functions
Bottom-down: Is basically unit testing/the opposit of top down

[SalJoaNoc]

1. It is a software development process which program units are combined and tested as group in multiple ways.
2. It expose and solve problems with the interfaces among program components before trouble occurs in real world program execution.
3. Bottom-up: test begins with unit testing.
   Top-down: highest level modules are tested first.

[Raulitiu]

1. Why do we write integration tests?
   To combine and test developement proceses as groups in multiple ways.

2. What problems do integration tests solve?
   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?
   In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that and bottom-up integration testing begins with unit testing, followed by tests of of progressively higher-level combinations of units called modules or builds.