My opinion on test team construction

Catalog

Preface

1、 A complete team

2、 The role of the test team in the development process

3、 Test intervention time

4、 Unified management

5、 other

---

Preface

The function of testing in a software company is to check whether the product is qualified , Whether it conforms to the user's usage habits . In the process of inspection , Expose software as much as possible BUG. The test team is an important functional department that controls product development , Have their own strict test standards , At the same time, it has its own set of strict test procedures and methods . Working in various companies 6 Years time. , I feel that the previous teams have some problems , So I would like to suggest some suggestions on the construction of the test team .

1、 A complete team

In my previous work , Testing is a complete team , There is a clear division of labor , Everyone has his own task division . On the whole , The test is mainly divided into ： A functional test 、 Performance testing 、 automated testing 、 Security testing . But in our current team , There is no dedicated performance test 、 automated testing 、 Security testing . And test at this stage , Mainly bias and functional testing .

In my expectation , Hope to have a complete team , This includes the post of appeal test . Be able to strictly follow the test standards . Each test point is in the charge of a specially assigned person , Attend to each one's own duties .

            

 

2、 The role of the test team in the development process

In the process of research and development , The main function of the test is acceptance , Only the test passed , The product can be launched , This requires a certain degree of independence for the test team , During the test , Only test according to the product requirements given by the product . Comments can be made on functions that do not meet the requirements , Whether the product is accepted or not also needs the approval of the test team . Can't be the same as before , Let the product specify the test completion time , because , According to previous practice , After product development is completed , There is not much time left for the test team . Usually it's just the theme function implementation , Just go online . In some detail , In previous test teams , Not doing well .

3、 Test intervention time

The normal test intervention time is when the product determines the requirements .

While the development team develops the software according to the requirements , Test teams need to design test cases according to requirements , Establish test environment .

If the product has already communicated with the development team 、 After the test team confirms the requirements , Add new requirements , Need to follow the whole development 、 The test team discusses whether the requirements can be added , Instead of the product department deciding .

Later in the test , If there are any remaining problems , Need to test 、 Development 、 Product tripartite negotiation , Whether the remaining problems have been solved . The main task is to test and raise the remaining problems （ Or questions in doubt ） To the product team , The product team decides whether to solve 、 The development team cannot decide whether to solve , But I can give you the approximate time needed to solve it , It is necessary to solve this problem in this version for the reference of the product team .

                       

 

4、 Unified management

It is hoped that the existing test resources can be managed uniformly , because ,app Tests are mainly functional tests , Performance and automation 、 Less safety testing . According to the current situation of the company , Mainly mobile terminals , And multiple projects are interspersed back and forth , therefore , It needs a reasonable management system . Mobile terminals are mainly divided into apk、app And wechat . The three ends are presented in different ways , The required testing tools are also different . Later, we will adopt behat And Appium Test tools , It mainly tests the main process of the mobile terminal automatically . But there are many preparations for automation , Later maintenance takes up more manpower . therefore , It also needs a reasonable management framework .

5、 other

In my previous work , Especially in the work of netqin and Alibaba , Personally, I think some good team management experience is worth learning .

1. The testing department is mainly divided into functional testing 、 Security testing 、 Performance testing 、 automated testing ,4 Departments , Each is responsible for his own scope of work . Every department has a person in charge 、 Directly responsible to the general head of the testing department , Instead of being responsible for the product . Test department level and development 、 Product team peers , Directly responsible to the project leader .
2. There are special project management tools , Unified management BUG, The requirements document , Team management, etc . Be able to clearly assign tasks to individuals , Everyone also knows what needs to be done .

in addition , According to the past experience and the current development environment of the company , I feel that according to the existing workflow , After the product development is completed by the development team , Then the test team will conduct unified test , The advantage of this is , It can reduce the size of the test team , Save testing resources . Daily management is convenient , Easier to work on different projects 、 Communication between different products . The disadvantage is that if too many testers start the project at the same time, they can not conduct high-depth tests on multiple projects at the same time , Or the test time needs to be extended .