How the test team conducts QA specification

How to test the team QA standard

Catalog

1、 Daily process

2、 Requirements testing

3、 Problem tracking

4、 Demand Online

5、 Team structure

6、 performance appraisal

1、 Daily process

1、 The work report

（1） Time and submission method ： Every Friday before work ,SVN/GIT/ Group mail / Group file Submit

（2） Content ：BUG Statistical table 、 Website project schedule （ Based on monthly statistics , Weekly update ）、 Statistical table of delay demand

（3） Naming specification ： Document name + A signature + date

2、 The regular meeting

（1） Time and place ： Every Monday morning 10-12 spot ,XXX Conference Room / Online meeting

（2） Participants ： Full group members

（3） Process and content ：

a、 Summarize the work of the week （ Requirements test progress 、 Question feedback, etc ）

b、 Intra group test sharing （ Demand for logic 、 The test point 、 Test difficulty ）

c、 Work arrangement and follow-up project plan for next week

d、 Summary of the meeting

e、 The meeting minutes are sent to the director by email 、 The manager 、 Supervisors of each test group and members of this group

3、 Tutorial system ： Qualified people can apply to become tutors

4、 On duty and overtime ： Work overtime on Saturday and Sunday , Take turns on duty during holidays （ No special circumstances ）

2、 Requirements testing

1、 Environment and sequence ： Test environment ->（ Pressure test environment ）-> Preproduction environment -> Production environment

2、 Comprehensively test all involved logic

3、 Focus on URL response time （ Especially the activity page ）

4、 prevent XSS attack 、SQL Injection and special characters （ When it comes to the input box ）

5、 All button labels in the website need to be loaded by default

6、 Check whether the page has been replaced with a new https Network security protocol

7、 Online testing , The test data should be accompanied by test The word , The test link is not allowed to be an external chain , Delete in time after the test

8、 New functions or major changes , You can communicate with the demander or the product to increase the data embedding point

9、BUG Grade ： Crash level 、 Severity 、 Defect level 、 Defect level 、 Suggestion level

10、 Requirements test progress ： Not tested 、 In the test 、 To be accepted 、 Waiting to go online 、 Online 、 Cancel the test

3、 Problem tracking

1、 Follow up the feedback from the group in turn every month

2、 The personnel on duty need to follow up the problems fed back by the Group

3、 Count the feedback problems on the Group 、 Confirmed problems known by other channels 、 Testers found online problems , Send the statistical form to the supervisor at the end of the month （ The personnel who follow up the problem in the current month make statistics and send it to SVN/ Group mail / Group file ）

4、 Demand Online

1、 Need to go online alone in advance , Must be informed by the product

2、 Version Online

3、 Any online demand , Test emphasis must be added

4、 Before going online , After passing the pre production environment test , Corresponding product acceptance must be notified

5、 demand BUG It needs to be counted in the test management platform and urged the development to solve

6、 Online demand , Front end performance test is required , All requests , Pay attention to the page response

5、 Team structure

1、 Basic function group （APP、WEB client 、WEB The management end 、 Real vehicle 、 Simulation Protocol ）

2、 Performance test group

3、 Automated test group

4、 Security test group

5、 Test development team

6、 Special group

6、 performance appraisal

1、 Assessment content

（1） Work task completion

（2） Requirements testing and online BUG Discovery rate

（3） Logical documents 、 The test case 、 Test script and other output （ It needs to be updated in time ）

2、 Report submission

（1） monthly 9 Before （ On weekends or holidays , Advance to the working day of the week ）

（2）SVN/GIT/ Group mail / Group file submission