Integration Testing - Reading Assignment

Blockchain Business Course
#603

1. Why do we write integration tests?

The aim of integration testing is to test the interfaces between the modules and expose any defects that may arise when these components are integrated and need to interact with each other.

2. What problems do integration tests solve?

Verifying if the individual units are communicating with each other properly and working as intended.

Even when each module of the application is unit-tested, some errors may still exist. To identify these errors and ensure that the modules work well together after integration, integration testing is crucial.

Integrating disparate modules testing can help ensure that the integrated units function properly as one unit and align with stated requirements. It can also ensure there are no errors between the different interfaces of different modules.

Ensuring that changing requirements are incorporated into the application : In many real-time application scenarios, requirements can and do change often. These new requirements may not be unit-tested every time, which may lead to missed defects or missing product features. Integration testing can fill in these gaps to ensure that new requirements are incorporated into the final application.

Eliminating common issues missed during unit testing: Some modules that interact with third-party application program interfaces (APIs) need to be tested to ensure they function properly. This may not be done during unit testing, so

Eliminating other common problems: Integration testing also helps eliminate issues, such as inadequate exception handling, API response generation, data formatting, erroneous external hardware interfaces, incorrect third-party service interfaces and error trapping.

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

Top-down testing: The top-down approach is an incremental approach that involves testing from the topmost or highest-level module and gradually proceeding to the lower modules. Each module is tested one by one, and then integrated to check the final software’s functionality.

Bottom-up testing: Bottom-up (also known as bottom-to-top) integration testing is the opposite of the top-down approach. It involves testing lower-level modules first, and then gradually progressing incrementally to higher-level modules. This approach is suitable when all units are available for testing.

1 Like
#604

1.) Why do we write integration tests?
Unit tests prove that individual functions work. Integration tests prove that aggregations of functions work in concert and don’t break each other along all relevant combinations of their edge cases.

2.) What problems do integration tests solve?
Integration tests address the overall robustness of the system in response to combinations of nominal and edge case inputs to its various components.

3.) What are the differences between top-down and bottom-up approaches?
Top-down stubs in lower-level functions and starts with integration tests. Unit tests are performed as the system is developed into its details. Bottom-up approaches stub in coordinating components and begin with unit tests on the lower-level components. Integration tests are then performed as the aggregating functions are built.

#605 
1.	Why do we write integration tests?

To ensure different modules of a software application work together correctly when combined.
2. What problems do integration tests solve?
They identify issues in module interaction, ensure overall system functionality, and detect integration-specific errors.
3. Differences between top-down and bottom-up approaches?
• Top-Down: Tests from high-level to low-level modules; early system visualization; critical top-level flaws found early.
• Bottom-Up: Begins with low-level modules; quicker initial testing; delays in detecting high-level module defects.

#606
  1. Why do we write integration tests?
    “The aim of integration testing is to test the interfaces between the modules and expose any defects that may arise when these components are integrated and need to interact with each other”
  2. What problems do integration tests solve?
    They make sure the individual units work well together. individual units (functions) are worked on by different programmers. In integration testing we make sure that the application as a whole works well.
  3. What are the differences between top-down and bottom-up approaches?
    top down kind of puts the tester in the shoes of the user, when the bottom up comes accross as a more developer/technical approach. Here you start with the higher level modules and then go to the lower levels
#607

1-Integration tests are written to identify and resolve issues with the interactions between different components of a program. They help catch problems early, making them easier and cheaper to fix.

2-Integration tests identify issues with the interfaces between different components, ensuring they work together correctly. This helps prevent major problems during real-world execution.

3-

  • Top-Down Testing: Starts with testing the highest-level modules first and progressively tests lower-level modules.
  • Bottom-Up Testing: Begins with unit testing individual components and progressively tests higher-level combinations of these units, known as builds.