Specification for self test requirements of program developers

One 、 background

Items that have not completed self-test in the past shall be delivered for test , A large number of low-level errors occur , This leads to inefficient man hour investment in the testing department , The test quality is not high , Therefore, development testing is regarded as an important node before delivery and test , Developers must have basic test awareness and ability , Make sure there are no major problems , The main function logic is smooth , Ensure the quality of delivery and test .

Two 、 Self test requirements

1. Develop self-test cases

Test according to the development self-test cases provided by the test department .

Example ：

2.YAPI Interface documents are complete

Check that the interface documentation is complete , Including interface definition , Enter the reference , Return value , Field length limit, etc . It must be confirmed by the front-end personnel .

3. Interface pass rate 100%

adopt Postman or Yapi Perform a set test on the interface . Next, the execution result must 100% adopt .

4. Complete a round of development self-test

After the self-test is completed, the project developer's self-test document will be produced .

The objects involved in the self-test ： product 、 Design 、 front end 、 backstage .

Purpose of self-test ：

1. The designer checks the visual restoration of the design .
2. Check that the business process and function access of the product meet the requirements , Avoid missing features .
3. Check whether the product copy is correct .
4. Background personnel check whether the interface is normal .
5. Front end and background developers can check whether the page function and logic are normal .

3、 ... and 、 Requirements for writing self-test documents

1. Module classification

Class A ： Small program end 、 Wechat end 、 Background management

second level ： Business module

2. Problem aggregation

Different problems of the same module are recorded in the same column .

3. Problem status

Set the state of ： To be processed 、 resolved 、 Verified .

Four 、 Self test questions

1. Time is tight , Whether self-test is required for urgent tasks

A： Ensure that the main line functions properly , Specify which function modules are not fully functional , However, the requirements still need to be tested , Must be confirmed by the Department Manager .

2. The code written by developers is not very demanding

A： Adhere to code specifications , Review the complex process first out process or scheme .

3. Think that developing self-test is not important or has no self-test thinking consciousness

A： Self test is an important part , Strengthen team self-test awareness and standardize process operation .

4. I don't know how to carry out effective self-test through tools

A： Use Chrome Browser open Console View input and return ,Postman The interface test ,Jmeter Do pressure test ,WEB The development tool checks the wechat interface call , Real machine experience of other core businesses .

5. simulation ( normal ) Test data , And data volume .

A： Initialize normal data , Do not use 123 or abc This test data . Simulate a reasonable amount of data , And add the necessary table indexes , Ensure that... Is on the real data volume SQL Execution efficiency .

6. simulation ( Submit ) Abnormal data

A： Page submit unconventional data , Including special symbols , expression , Null value , Extra long character , Check whether the interface call is normal .

7. Simulate abnormal process operation , Think about which operations or processes are abnormal

A： Through direct access to the page , Check whether the page operation is normal , Whether the prompt is normal .

8. Check security checklist

A： Safety rules checklist, Make preparations before launching .