Eat a little feelings of failure

This week received a demand due to an existing field in a table can not satisfy the query, it adds a few fields.

The meal is done, add the field, kafka consumption data from complete, was flattered.

The question arises, check out the other departments to reflect data problems, leading to some of their online business can not operate, and heart Ji Ling, to immediately begin the investigation together.

Anyway to stop bleeding of it, it is due to have a table in the database field and both null null characters caused flew inquiry judge added, bleeding ends.

Although stop the bleeding, but always know what causes it, then start a little bit of investigation and the reasons.

The reason is that now the company provides field must be empty and to default, but is not required before, resulting in a cousin there are many fields are allowed to be null.

The company then encapsulated frame, insert statement is too little pits, led after the new consumer logic, there is a field into a null character.

In fact, these fields and allow null, the company insert statements are not big pit relations, the problem still lies in our own it.

Why he was so respected TDD, in fact unreasonable, but it is really difficult to achieve.

A problem for several reasons: 1. there is no unit test development 2. Developing the lack of appropriate documentation 3. Nobody commuting 4. Development Code does not speak with the test data clearly who will influence 5. Test did not realize some of the downstream Happening

In short, the problem is nothing more than two reasons production machine or 1. 2. The intermediate code is linked to the bug.

The first point we can not control, but we can control the second point.

Now their own group began to implement the following:

Test unit (abnormality coverage Interface)
codes commuting (commuting cross backup)
code review
backup
interface document

It is also proposed test requirements, if data related to the parties or interface, notify the interested parties must be verified over and over again.

Of course, there is a very important point:

The development process, developers and developers to communicate, developers and testers communicate.

Will not communicate much ambiguity in order to reach an agreement.

 

This is the time to eat a little thank failures, such as yo Please do not put forward together to improve, thank you!

Guess you like

Origin www.cnblogs.com/shenqiaqia/p/11295577.html