Just try to use TDD to develop, it feels good. The code has more test cases. However, there are still many problems in use. The first question is to write test cases before writing, then write code, or after the classes and empty methods can be built first, write test cases, now use the latter method. The former method is not used to it, and it will show a bunch of errors, very uncomfortable. I don't know if there is any problem with the current method, as if there is TDD requirements, it is incomplete. The second question is that when you are developing, you don't consciously write a good code, write test cases, think about writing test cases based on code, and needs to be corrected. The third question is, always write a lot of code to start testing, so it is easy to accumulate. TDD has no systematic view, but also needs to study hard. . .
