From a development perspective, first organize the variables and functions according to certain naming and formats. Next, start writing code. In the industry, many advocate test-driven development. Next, let’s talk about unit testing. TDD is the English abbreviation of Test-Driven Development. It is a core practice and technology in agile development and a design methodology. The principle of TDD is to write unit test case code before developing functional code. 1. The Three Laws of TDD Law 1: Do not write production code before writing unit tests that cannot pass. Law 2: You can only write unit tests that just fail to pass. Failure to compile does not count as failure. Law Three: Write only enough production code to pass the current failing test. Tests are written along with the production code, the tests are written just a few seconds before the production code. 2. Keep the test clean. The test code is as important as the production code and needs to be kept tidy enough. Testing brings all the benefits. Clean unit test code will bring many benefits to your code. The dirtier the tests, the dirtier the code will eventually become. If tests are missing, the code starts to rot. 3. Neat testing There is a very important point in neat testing
1. Today’s sharing: The way to clean code - unit testing
Introduction: From a development perspective, first organize the variables and functions according to certain naming and formats. Next, start writing code. In the industry, Many people advocate test-driven development. Next, let’s talk about unit testing.
2. Detailed explanation of JavaScript programming style guide
##Introduction: The author summarizes the software engineering principles "Clean Code JavaScript" applicable to JavaScript based on Robert C. Martin's "Clean Code". This article is a translation of it. It is not necessary to strictly abide by all the principles in this article. Sometimes it may be better to abide by less. The specific decision should be based on the actual situation. This is a code optimization suggestion compiled based on the author's years of experience in "Code Cleanliness", but it is just a suggestion. Software engineering has developed for more than 50 years and is still making progress today. Now, use these principles as a touchstone and try to use them as team representatives..
#Introduction: Catalog Overview Variables Function Objects and Data Structure Classes Test Concurrency Error Handling Format Comments Overview RobertC.Martin in "Code...
Introduction: Recently, I read CleanCode (the way to clean code) while squeezing the bus to and from work. , I once again admire Uncle Bob’s humorous writing style, unique viewpoints and perspective of understanding. What is most refreshing to me is Uncle Bob’s explanation of data structures and objects
[Related Q&A recommendations]:
The above is the detailed content of Detailed introduction to code cleanliness. For more information, please follow other related articles on the PHP Chinese website!