Integration Testing - Reading Assignment


#21

Why do we write integration tests?

Integration tests are written because they provide an extrememly comprehensive methodology for finding errors before deployment. They combine individual units of code to make sure they work when tested all together.

What problems do integration tests solve?

Integration testing can show us problems with the interfaces in program components before deployment.

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

In Bottoms up testing the smallest parts are tested first with more progressive combinations of parts added until all parts have been tested. In Top down, they begin with larger parts and go down from there to smaller units until the testing gets to the smallest.


#22
  1. Integration testing is to check interactions between all levels of the complete application.
  2. These tests are done to find errors between subsystems.
  3. Top-down begins with testing at the highest level and works down into individual components. Bottom-up begins at the unit level and works up. Top-down is usually done before bottom-up.

#23

1.Why do we write integration tests? A: to test interaction between functional areas/sw-units

2.What problems do integration tests solve? A: they assure interfaces and API’s are correcly used between units/functional-areas.

3.What are the differences between top-down and bottom-down approaches? A: top-down is testing from the overall scope/usecases untill unittesting/whitebox; and bottom-down does not exist but bottom-up if from the unitting tests up to the overall end-2-end application usecases.


#24
  1. Why do we write integration tests?
    To test SW behaves as required on multiple levels of the application, across code units and modules/builds.

  2. What problems do integration tests solve?
    Interface defects, in relational database also the data classes behaviour and querying, can test nondeterministic or multiple threads.

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

** we mean bottom-up

Bottom-up approach starts testing with code units, progressively to higher combinations of units in modules/builds.
Top-down approach testing starts with highest-level of the application like features (Search, Export, Import, etc), down to lower level modules.


#25

Why do we write integration tests?

  • Because is the next natural step when we want to know whether small functions work well together or not.

What problems do integration tests solve?

  • Problems related to the interaction of units of code making up a bigger system, module or builds.

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

  • The differences are related to the initial modules selected to be tested and the subsequent modules to test going down or up respectively the chain of relation between them.

#26
  1. Why do we write integration tests?

They are important to do after unit testing but prior to functional testing.

  1. What problems do integration tests solve?

Integration testing can expose problems with interfaces prior to real-world program execution.

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

In bottom up integration testing, you start with units and combine them in smaller modules and build up (in other words, make the modules bigger by adding units). You continue to test bigger and bigger modules.

In top-down testing, you start testing the biggest modules first, and then work your way down to smaller and smaller modules.