1, the origin of the bug
Worm crawling into the mainframe caused a short circuit of the relay, causing the machine to malfunction. The real flaw is: the host cooling hole less installed block of wire, so as to prevent insects crawling to the host.
2. What is a bug?
A bug is a manifestation of a defect, and a flaw can cause a variety of bugs. Software testing, the process of running the software in order to discover errors in the software.
- Bug Evaluation Point
- 1) The software does not meet the functionality and performance of customer requirements documentation
- 2) The software can not tolerate the error of customer demand
- 3) The use of the software does not conform to the customer's custom and working environment (ease of compatibility)
- 4) software beyond the scope of the requirements document (requirement bug)
- Bug Categories:
- Defect, defect: The deviation in software, a static form exists inside the software, can be activated;
- Failure, failure: The result of external abnormal behavior when the software is running, performance is inconsistent with customer demand, function terminates, the user can not complete the required application;
- Error: There are code that writes the error, syntax errors, and logic errors.
- Fault, fault: The state of the software operation, can cause unexpected situation, if not added processing, can produce failure, is a dynamic behavior.
- Here are some common categories:
- Partitioning method One:
- Code Error
- Design flaws
- Interface optimization
- Configuration related
- Installation deployment
- Performance issues
- Standard specification
- Test code
- Other
- Dividing mode two:
- Functional Class (function)
- Performance Class (performance)
- Interface Class (UI)
- Ease of Use class (usability)
- Compatibility Class (compatibility)
- Other (ELSE)
3. Why should I submit a bug?
- 1) speed up the processing of defects;
- 2) Improve the credibility of the test;
- 3) Strengthen the team cooperation between the test group and the development Group during the whole project;
- 4) Effective Error tracking method, providing basis for subsequent bug analysis and product quality measurement;
4. Bug Management tools?
- Open Source: Bugzilla, Bugfree, Zen Road, Easybug, Mantis, Trac;
- Enterprise level: QC, JIRA,
- App:bugtags
5, how to write good bug description?
- Need to be brief, clear, and defective. If done poorly, it can confuse and increase the cost of communication.
- Workaround: Bug Template
- A good bug description should include 9 basic sections:
Overview (briefly indicate the dependencies of program errors, not too long or too short),
Project (version number), owning module, priority level, severity level (fatal, severe, general, prompt),
Repeatability (non-reproducible, 2 occurrences per 3 times, mandatory), test conditions (software-hardware configuration-environment information-operating system-database-browser),
Operating Procedures and attachments (pictures, data, and logs), expected results
6, how to deal with the common bug problem?
- 1) Similar bugs, the root cause is different, even if the appearance, but also log two or more than two
- 2) Repeat the bug, log before the bug library to find the results to tell the partner, avoid being developed to call back
- 3) can not reproduce the bug, to log detailed description of the operation procedures, symptoms, testing environment, so that for re-reproduction also has a certain reference
- 4) Small problem bug, also want log. If not solved, it will continue, small problems will affect customer confidence
- Other:
The number of defects found does not explain the quality of the software.
Don't expect to find all the flaws in the software
Do not expect to fix all defects found
7. Bug Life cycle
New, open, fixed, re-open, delay, reject, closed.
8, how to make a bug analysis?
- 1) The defect distribution of the module, generally with a histogram or pie chart, is each function module to find the proportion of the bug, found that the most bugs in the module proved to need more maintenance after the release.
- 2) The cause distribution of defects, generally with histogram or pie chart, can be divided into architectural defects, functional defects, ease of use defects, performance defects, security defects, demand defects, interface text defects. In general, if the architectural defects accounted for a large proportion, it indicates that the design has a lot of problems.
- 3) According to the distribution of defects of different personnel found, generally with a histogram or pie chart, generally divided into testers found that the developers found that the beta test found that external customers found. If the tester finds a bug that is below a certain scale, it proves that the quality assurance test is insufficient.
- 4) defect analysis, which is already found and resolved curve relationship, with time as the horizontal axis, the closer the two shows the higher the product quality
- 5) According to the distribution of defects in the time period, the general use of time for the horizontal axis of the graph, the main explanation at which stage found the most bugs, the test summary is instructive.
9, how to prevent the bug
- The best way to ensure quality is to prevent bugs and prevent them from happening.
- 1) Establish a bug prevention system: Root cause analysis, summarize the different projects often found common similar bug, advance inform development, prevention beforehand. and continuously maintain updates.
- 2) Develop normative development: Code specification, code review, Unit testing, Code refactoring specification, development self-test.
- 3) Web Prevention: resolution, browser compatibility, error message display code information, text abbreviations and lines, repeat submissions, scripting attacks, cross-site attacks, sensitive information disable caching, password encryption, log level info level ...
Bug Management Those things _20160910
