How to build Software Test team-Test team

Four types of software testing teams:

(1) Fusion type

The so-called fusion software testing team refers to software testers and software developers integrated, software testing work is actually done by the people engaged in the software development.

Applicable environment Analysis:

Although this type of test team has some advantages in some way, its fatal flaw is the inability to effectively guarantee test quality. As a result, this type of testing team can only be a small business start-up (because this type of company on the one hand, fewer projects, on the other hand management is not perfect) expedient, can never be used as a long-term type.

(2) relatively independent type

The so-called relatively independent software testing team refers to the software testers and software developers belong to a department, but belong to different groups (that is, testers belong to the test team, developers belong to the development team, relatively independent), software testing work by the Test team completed, software development work by the development team completed, two group division of Labor Clear. This test and development of a relatively independent Test team has some of the following advantages and disadvantages.

Applicable environment Analysis:

This type of testing team, although there are obvious deficiencies, but in most cases can better guarantee the quality of testing, but also good control of test costs. Therefore, this type of Test team is suitable for small software companies (because this type of test team does not need to occupy the company's larger financial and human input).

(3) completely independent type

The so-called completely independent software testing team refers to the software testers and software developers belong to their own independent departments (that is, the tester belongs to the testing department, the developer belongs to the development department), the quality of the testing department by the company evaluation, the quality of the test staff by the Test department supervisor evaluation. Specifically, testers and developers belong to separate departments, the company's independent assessment of the various departments, the performance of the tester is fully assessed by the test supervisor, whether the product passed the test needs to be given a clear conclusion by the tester.

Applicable environment Analysis:

This type of test team can effectively guarantee the quality of the test, but it easily leads to misunderstandings and contradictions between developers and testers. This type of testing team is more suitable for companies engaged in product development and marketing (because such a company generally products are relatively single, stable, testers do not need to know too much product information to the developer).

(4) Mutual restriction type

The so-called mutual control software testing team refers to the software testers and software developers belong to their own independent departments (that is, the tester belongs to the testing department, the developer belongs to the development department), but there is a relationship between the tester and the developer to evaluate the quality of work. Specifically, testers and developers belong to separate departments, the company's independent assessment of various departments. When the test supervisor assesses the performance of the tester, taking the effective test workload and test quality approved by the development department as one of the evaluation indexes; When the development supervisor assesses the performance of the developer, the test defect provided by the tester is used as one of the evaluation indexes, and whether the product passes the test requires a clear conclusion from the tester.

Applicable environment Analysis:

This type of testing team, although there are some deficiencies, but can effectively ensure the quality of testing. This type of test team consumes a higher cost of testing, so it is more suitable for large companies with a certain economic strength, especially for large companies with the main business of project delivery (because such companies need to be closely communicated and coordinated by testers and developers)

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html