Independent testing corresponds to an independent team, who involve in testing activities other than developer to avoid author bias and is often more effective at finding defects and failures.
There is several level of independence which is listed here from the lowest level of independence to the highest:
1. Testing done by developer himself.
2.Independent testers ceded to the development team.
3.Independent Testing Team within Organization.
4.Independent Testers of different Organization.
5.Outsourced test team members of other organization.
Advantages of independence testing:
1. The tester sees each defect in a neutral perspective.
2.An independent tester can repeatedly find out more, other, and different defects than a tester working within a programming team – or a tester who is by profession a programmer.
3.The tester is totally unbiased.
4.The tester sees what has been built rather than what the developer thought.
5.The tester makes no assumptions regarding quality, which often helps in exposing the hidden defects and problems whereas business analysts, marketing staff, designers, and programmers bring their own assumptions to the specification and implementation of the application under test.
Disadvantages of independence testing:
1.There is a possibility that the testers and the test team can get isolated. This can take the form of interpersonal isolation from the programmers, the designers, and the project team itself which can sometimes lead to outdated documentation reference.
2.The independent test execution is normally the last stage and affected by any delays earlier in the process.
3.Developers might be irresponsible for quality as they might assume that independent testing team is there to find the issues within the system.
4.Independent testing can smetimes leads to communication problems, feelings of unfriendliness and hostility.
5.Lack of identification with and support for the project goals, spontaneous blame festivals and political backstabbing.