Identify and describe defects
1 , the definition of software defects
One of the following five conditions (all software problems are called defects)
Software does not meet product specifications have been marked function.
An error has occurred Software products specified in the description does not arise.
Software functions beyond the specified range of product specifications.
Software does not meet product specifications although it is not stated but the objectives to be achieved.
Software testers thought the software difficult to understand, difficult to use, slow speed, or the end user of the software considered bad results.
2 , the causes of defects
Persons (users, design, development, test, the technical support, etc.) communication between not enough, there is some misunderstanding on the exchange or not exchange.
Incomplete documentation or no documentation (especially domestic small and medium software enterprises).
Constantly changing needs.
Overconfidence personnel involved.
Program design itself is wrong.
The complexity of large software defect is difficult to avoid.
Short construction period, heavy task, time pressure.
Software development tools and hardware support.
3 , the defect determination
Software technicians discovered the problem, determine what if the problem is based on flawed?
To identify defects (requirements specifications, outline design, detailed design, user manuals ......) by reference to the documentation.
By understanding the software industry standards, industry typical of similar background or reference software to find defects.
To confirm and identify defects through communication.
Ask developers, ask staff needs, ask the user ......
4 , reproduced defect optimization
Reproducing method for optimizing defects:
Do not take it for granted accept any assumptions.
Find a dependency problem and competitive conditions.
And pressure boundary conditions and comply with the relevant software bugs, memory leaks and data overflow can occur for certain conditions (clear the cache).
Only to reveal defect state (sequence) in a particular state of the software.
Consider resource dependencies, memory, network, hardware sharing interactions.
Failure concerns hardware, the hardware may not work (hardware bad sectors) in a predetermined manner.
Watch software failures, defects modification may lead to back new defects.
Starting from reading the report defects and improve the ability to write bug reports (learn from others).
5 , how to effectively record defects
A simple way to determine the quality of report writing deficiencies:
Let not a defect report writers (technician) to reproduce the defect based on defect reports, if simple, quickly reproduce defects, defect reports indicate better.
Fault - with minimal steps to reproduce the defect
Reduce the time developers to reproduce the defect.
It allows developers to more accurately locate defects.
It contains all the necessary steps to reproduce defects.
Testers assumed common procedure developers are not necessarily familiar with the necessary steps omitted often cause developers can not reproduce the defect.
7 , defect content
Symptom:
Use the "Notepad" reservation only "Unicom" word and then open the file, appear garbled.
Steps:
1. Click "Start" -> "Programs" -> "Accessories" -> "Notepad" to open the Notepad software;
2, enter "Unicom" after the word, click on the "File" only -> "Save";
3, then open the "Save As" dialog box, save the file after the launch;
4, open the saved file, garbled, not "Unicom" word appears.
expected results:
Use the "Notepad" reservation only "Unicom" word and then open the contents of the file, the contents of the input consistent.
8 , record defects
One drawback of a report, why?
Example (a bug report two defects)
Overview: Using the "Notepad" reservation only "Unicom" word and then open the file, garbled, and "Save As" dialog box, the default file extension written ".txk"
Description steps:
1. Click "Start" -> "Programs" -> "Accessories" -> "Notepad" to open the Notepad software;
2, enter "Unicom" after the word, click on the "File" only -> "Save";
3, in the open "Save As" dialog box, keep the file after the launch, the default file extension should be ".txt", actually wrote the ".txk";
4, open the saved file, garbled, not "Unicom" word appears.
So what adverse consequences?
步骤3出现的缺陷对于开发人员而言容易修复，而步骤4出现的缺陷很难修复，那么如果开发人员修复了步骤3出现的缺陷而没有修复步骤4出现的缺陷，这个缺陷报告是解决了还是没解决？
9、值得注意的经验
记录bug最好能配有截图，这样有利于开发理解。
如果有能力，尽量附上可能原因，以供开发参考。