Integration

So what is integration?

As mentioned before, integration is the process of combining components or systems into larger assemblies.

During integration testing testers concentrate solely on integration itself.

For example, if the tester is integrating module A with module B, he is interested in testing communication between the modules, not the functionality, as it was done during component testing.

In general, to be a good integration tester, more technical skills are required.

Ideally, testers should understand the architecture and the interfaces.

What is V Model in Software Testing?

V model is also known as verification and validation software model is an SDLC (system development life cycle) and STLC (software testing life cycle) based where main execution process takes place in a sequential manner of v shape.
V model is nothing but the extension of the waterfall model which is based on the association of the development phase and each of the corresponding testing phases.
That means there is a direct link between the testing cycle and the development cycle. V model in software testing is highly specific model and movement to next only occur after completion of the first cycle.

The testing phase of the V model may include:

• Unit testing: It is developed in the model designing phase, to eliminate any bug if present. Usually happens after b
• Integration testing: It is performed after completion of unit testing and in this modules are integrated into the system to be tested. This verifies the communication aspect.
• System testing: It looks after the functional and non-functional requirements.
• User acceptance testing(UAT): It is performed in the user environment that simply resembles the production unit, in this step it is made sure that the software is ready to be used in the real world.

Advantages of the V model

1. Easy to understand and apply, with its flexibility it is easier to manage.
2. It is a highly discipline-based model and can be used in specific industries like health.
3. As each step is designed in a very rigid and fixed manner so it is much easier to do the review process.
4. It is useful in smaller projects where requirements are less and well known.
5. Useful in projects where documentation is fixed and no ambiguous technological changes are required.
6. Find more about this software development methodology here

Disadvantages of waterfall model

1. Testing only starts after implementation is already done.
2. It is difficult to work on large projects as key details are subject to being missed out.
3. If you make any mistake at any point you must design the whole software to combat the error.
4. Architectural defect in the designing and defect introduction.
5. Cost of fixing a defect is way too high.
6. Find more about this type of software development metodology here