C Language Programming Specification--------11 code testing, maintenance

(1) Unit testing requires at least a statement overlay.

(2) The unit test begins by tracking each statement and observing changes in the data flow and variables.

(3) The code after cleaning, sorting or optimization should be reviewed and tested.

(4) Code version upgrade to undergo rigorous testing.

(5) Use the tool software to maintain the code version.

(6) Any modification of the software on the official version should be documented in detail.

(7) Errors are immediately corrected and recorded.

(8) Key code is tracked at the assembly level.

(9) Carefully design and analyze test cases, so that test cases cover as many cases as possible to improve the efficiency of test cases.

(10) As far as possible to simulate a variety of errors in the program, error handling code to fully test.

(11) Carefully test the code processing data, variable boundary conditions.

(12) Retention of test information for analysis, lessons learned and more thorough testing.

(13) The problem should not be solved by "try", and the root cause of the problem should be found.

(14) Analyze the error of automatic disappearance and find out how the error disappears.

(15) Correction of errors not only to the table, but also to cure the problem.

(16) Testing should try to make infrequent events occur frequently.

(17) Define which events the module or function handles and make them happen frequently.

(18) Adhere to the coding phase of the code thoroughly unit testing, do not wait for future testing work to identify problems.

(19) To remove the randomness of the operation of the code (such as removing useless data, code, and as much as possible to prevent and notice "internal registers" in the function), so that the results of the function can be predicted, and the resulting errors can be reproduced.

C Language Programming Specification--------11 code testing, maintenance