Hardware and Software debugging Nine method: Sixth rule keeping audit trail

1. Record your operation, operation sequence and results

Keep track of what you do, the order in which you do things, and the results that happen, every time you finish. Just like debugging hardware, each step must be guided and the results executed to determine the focus of the next step.

2. Be aware that any detail may be important

Sometimes the bug report may have a simple sentence, such as the instrument display error, or the instrument does not work properly, such content to the tester does not help, in addition to record what happened, but also to pay attention to the details of the problem is the severity of the issue, in order to determine whether the need for immediate repair.

3. Associating time together

Symptoms associated with debugging information are useful, such as the report "buzzer at the end of the measurement, occasional sound longer", than "buzzer sound occasionally longer" useful. A case in the book, the Computer Center reports that the server crashes, often appear around 3 o'clock in the afternoon, according to this time information, the engineers found that 3 o'clock in the afternoon is the time for everyone to take a coffee break, because the large number of operations on the vending machine beyond the scope of the server to cause its collapse, it is easier to find the bug.

4, for the design of audit trail is also very useful

Software version Control tool, can tell you that version of the revision introduced a bug, and sue you two versions of the difference. Currently, it is recommended to use GIT version management tool locally, each modification of a function, and the test after the submission of records, making it easier to locate the bug in the place to a small change area! After the current version of the debug test is fully passed, upload to the company's VSS version of the server for the most release record.

5. Record the matter

In detail, never trust your memory, but write it down, no matter how busy you are. If you rely on memory, you may lose sight of the key details that you think are unimportant. Verbal delivery cannot accurately deliver messages and waste everyone's time, because you can't remember how to make things happen, the order in which they occur, and how they relate to each other, and when these very important messages are missing, others will have to re-complete the process of finding bugs and wasting more valuable energy! Save debug logs and track records, and note the relevant time and impact, record your reasoning, repair operations, and other content, and form a written bug report that is easily sent to them and backed up on your computer.

Hardware and Software debugging Nine method: Sixth rule keeping audit trail