Organisational structures for testing

Organisational structures for testing and pro's & con's of each testing group.

1. Developer responsibility (only):
Subjective assessment of work.They can find and fix faults cheaply.They have tendency to 'see' expected results, not actual results

2. Development team responsibility (buddy system):
Have some independence on friendly terms with “buddy” but with lack of testing skills.

3. Tester(s) on the development team:
Dedicated to testing, no development responsibility and part of the team, working to same goal: quality.But work in a single view / opinion.

4. Dedicated team of testers (Independent test team):
Dedicated team just to do testing with specialist testing expertise and testing is more objective & more consistent.

5. Internal test consultants (advice, review, support):
Highly specialist testing expertise, providing support and help to improve testing done by all and better planning, estimation & control from a broad view of testing in the organisation.But not performs the testing so someone still has to do the testing.

6. outside organisation (3rd party testers):
Highly specialist testing expertise and independent of internal politics.Associated disadvantages are:
lack of company and product knowledge,expertise gained goes outside the company and more expensive.