i want integration testing test cases for gmail
|
integration testing for gmail
|
i want integration testing test cases for gmail
10-04-2017, 04:22 PM
In integration tests, individual software modules are logically integrated and tested as a group. A typical software project consists of several software modules, coded by different programmers. The integration tests focus on verifying the communication of data between these modules. Therefore, it is also referred to as "I & T" (Integration and Testing), "String Testing" and sometimes "Thread Testing".
Approaches / Methodologies / Integration Testing Strategies:
The software industry uses a variety of strategies to perform the integration tests, that is,
• Big Bang Approach:
• Incremental approach: divided into the following
Big Bang Focus:
Here all the components are integrated together at once, and then tested.
Advantages:
• Suitable for small systems.
Disadvantages:
• Troubleshooting is difficult.
• Given the large number of interfaces that must be tested in this approach, some interface links to be tested could be easily lost.
• Since integration testing can begin only after the "all" modules have been designed, the test team will have less time to run in the test phase.
• Since all modules are tested at the same time, critical high-risk modules are not isolated and tested in priority. Peripheral modules dealing with user interfaces are also not isolated and tested in priority.
Incremental Focus:
In this approach, the test is performed by joining two or more modules that are logically related. The other related modules are then added and tested for proper operation. The process continues until all modules are assembled and tested successfully.
This process is carried out by using fictitious programs called Stubs and Drivers. Stubs and Drivers do not implement all the programming logic of the software module, but simulate data communication with the calling module.
Stub: It is called by the module under test.
Controller: call the module to test.
The incremental approach, in turn, is carried out through two different methods:
• Bottom up
• From top to bottom
Approaches / Methodologies / Integration Testing Strategies:
The software industry uses a variety of strategies to perform the integration tests, that is,
• Big Bang Approach:
• Incremental approach: divided into the following
- The Downward Approach
- The Ascending Approach
- Sandwich Approach - Combination of Top Down and Bottom Up
Big Bang Focus:
Here all the components are integrated together at once, and then tested.
Advantages:
• Suitable for small systems.
Disadvantages:
• Troubleshooting is difficult.
• Given the large number of interfaces that must be tested in this approach, some interface links to be tested could be easily lost.
• Since integration testing can begin only after the "all" modules have been designed, the test team will have less time to run in the test phase.
• Since all modules are tested at the same time, critical high-risk modules are not isolated and tested in priority. Peripheral modules dealing with user interfaces are also not isolated and tested in priority.
Incremental Focus:
In this approach, the test is performed by joining two or more modules that are logically related. The other related modules are then added and tested for proper operation. The process continues until all modules are assembled and tested successfully.
This process is carried out by using fictitious programs called Stubs and Drivers. Stubs and Drivers do not implement all the programming logic of the software module, but simulate data communication with the calling module.
Stub: It is called by the module under test.
Controller: call the module to test.
The incremental approach, in turn, is carried out through two different methods:
• Bottom up
• From top to bottom
10-04-2017, 04:23 PM
In integration tests, individual software modules are logically integrated and tested as a group. A typical software project consists of several software modules, coded by different programmers. The integration tests focus on verifying the communication of data between these modules. Therefore, it is also referred to as "I & T" (Integration and Testing), "String Testing" and sometimes "Thread Testing".
Approaches / Methodologies / Integration Testing Strategies:
The software industry uses a variety of strategies to perform the integration tests, that is,
• Big Bang Approach:
• Incremental approach: divided into the following
Big Bang Focus:
Here all the components are integrated together at once, and then tested.
Advantages:
• Suitable for small systems.
Disadvantages:
• Troubleshooting is difficult.
• Given the large number of interfaces that must be tested in this approach, some interface links to be tested could be easily lost.
• Since integration testing can begin only after the "all" modules have been designed, the test team will have less time to run in the test phase.
• Since all modules are tested at the same time, critical high-risk modules are not isolated and tested in priority. Peripheral modules dealing with user interfaces are also not isolated and tested in priority.
Incremental Focus:
In this approach, the test is performed by joining two or more modules that are logically related. The other related modules are then added and tested for proper operation. The process continues until all modules are assembled and tested successfully.
This process is carried out by using fictitious programs called Stubs and Drivers. Stubs and Drivers do not implement all the programming logic of the software module, but simulate data communication with the calling module.
Stub: It is called by the module under test.
Controller: call the module to test.
The incremental approach, in turn, is carried out through two different methods:
• Bottom up
• From top to bottom
Approaches / Methodologies / Integration Testing Strategies:
The software industry uses a variety of strategies to perform the integration tests, that is,
• Big Bang Approach:
• Incremental approach: divided into the following
- The Downward Approach
- The Ascending Approach
- Sandwich Approach - Combination of Top Down and Bottom Up
Big Bang Focus:
Here all the components are integrated together at once, and then tested.
Advantages:
• Suitable for small systems.
Disadvantages:
• Troubleshooting is difficult.
• Given the large number of interfaces that must be tested in this approach, some interface links to be tested could be easily lost.
• Since integration testing can begin only after the "all" modules have been designed, the test team will have less time to run in the test phase.
• Since all modules are tested at the same time, critical high-risk modules are not isolated and tested in priority. Peripheral modules dealing with user interfaces are also not isolated and tested in priority.
Incremental Focus:
In this approach, the test is performed by joining two or more modules that are logically related. The other related modules are then added and tested for proper operation. The process continues until all modules are assembled and tested successfully.
This process is carried out by using fictitious programs called Stubs and Drivers. Stubs and Drivers do not implement all the programming logic of the software module, but simulate data communication with the calling module.
Stub: It is called by the module under test.
Controller: call the module to test.
The incremental approach, in turn, is carried out through two different methods:
• Bottom up
• From top to bottom
|
« Next Oldest | Next Newest »
|
