Open source framework That thing 18: Why start with test case writing and document writing first?

There is a classmate, ask me a question: Does joining tiny have to start with writing unit test cases and documents?

This problem caused me a lot of feelings, so the formation of strum an article.

As a new addition, look more, less say, is hot. And this time, writing test cases, documents, is a good choice. This is easier to start, and more easily to reflect the level.

Good programmers, tests and documentation are well written. Test and documentation must not write well, must not be a good programmer.

At the same time, in the process of reading code, writing test cases, writing documents, you can also think:

Why would he design this? What am I going to do with my design? Then there is quite a part that will translate into: Oh, that's what it looks like! You have made progress at this time. Then there is a part left to let the original author into: Oh, the original is this look! Then he made progress, and the open source works improved. And part of it, he will tell you, the story is so, so that, and then into your: Oh, the original is this look!!! So you went further.

In fact, writing documents is the same truth, is the so-called: the test case is the program, the document is the program.

After you are familiar with a considerable part of your voice is getting bigger, you get everyone's recognition more and more, your scope of work will certainly become wider and richer.

Said, more see, Less said, is because, here all you are still very unfamiliar, many stories, you have not understood clearly, this time, see more, you can find his merits, or the shortcomings of doubt, and then slowly confirm, eliminate their own understanding of the wrong, leaving the real existence, this time, you are very easy to integrate into the team.

The most taboo of a situation is that only a few eye code, it is not right, that is not good, maybe you say a few are indeed some, but more is you have some things do not understand clearly, after all, to challenge others have been carefully scrutinized, thinking of the solution, need to have a deeper analysis, accumulation, precipitation. , if you mention very good, very right, the team will be very grateful to you, after all, can do open source, the mind is certain, if always take their own not careful reading, thinking to waste other people's time, finally difficult to integrate into the team.

That year, many heroes joined the water park Liangshan, are going to do a little thing, that you are sincerely willing to join, such as: Go downhill to do a vote, take personal head back and so on. When you join the tiny framework, it is also meant to do test cases and write documents before your true level appears. If the test case is written in good quality, but also found the original existence of a number of major defects, how can not be reused? If even the test case is not well written, the document is not well written. It also means that you write code, you also write bad test cases, write bad documents, which is unbearable for the open source organization.

So, don't look down on writing test cases and document-related work.

Open source framework That thing 18: Why start with test case writing and document writing first?