April 2014 went to Xiamen with other companies to tune the software interface.
1, code to go to check
These days in the XX company Joint Test Unit software interface, when the software bugs need to debug, I looked at their debugging, found their code is quite normative, including indentation, comments, naming, etc., which is much better than we do.
The code can indirectly improve the quality of the software, as well as maintainability, can reduce the time to find bugs, improve the efficiency of resolving bugs, easy for other team members to understand the code and reduce the maintenance costs later, it is recommended that in the development process in the future to increase the code to check this content.
The code walk-through found that the problem does not necessarily require developers to modify immediately, but at least in the subsequent development work will arouse his attention. Code walking may not see any benefits in the short term, but improving the overall quality of the company's code in the long run should be beneficial.
Coding specification to organize learning.
2, the test hillock
Based on "professional people do professional things" to consider, it is recommended to set up a special test position, to increase the full-time testers, responsible for the development of supporting related work. This article uses Chrysanthemum Zi Yue to publish
Advice on code walking and setting up full-time test posts
