Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.