Missing elements of the questionnaire

Table Items	Description
Defect number	First, the defect is entered into the Project Defect Library, and then added to the leak test library. The problem number in the missing library is the number in the Project defect Library, which is unique.
Owning module	Problem occurs in the software parts, according to the actual situation of the system can be divided into modules, such as file management, database, localization module.
Brief description	A brief description of the problem phenomenon, generally not more than 50 words.
Detailed description	A detailed description of the problem, including steps to reproduce the problem.
Problem level	Refers to a fatal, severe, general, secondary level that is used to determine whether a detailed leak analysis is to be performed.
Leakage of yield monitor health activities	In the software development testing Process , a certain category of missing defects should be found in the activity. The purpose of this classification is to facilitate further refinement of the analysis of missed activities.
	The development stage mainly includes the original requirement review, the concept review, the design review, the Code view, the unit test, the module joint adjustment and so on.
	The testing phase mainly includes functional test , system test , local language test, equipment driving test, installation Test , performance test , anomaly test, etc.
Version of Bug found	Fill in the software version number that found the bug, which corresponds to the version number in the code base for traceability.
Problem time found	Question input time, format (xxxx year XX month XX day)
Issue closed version	The defects of the input to the leakage test database must be closed within the expected time, and the closing time of the software should be filled out in the leak-test library.
Related Products	Which products are affected by missing defects, must be listed
Defect Impact	It is a risk analysis that the impact of defects on users, such as system crashes, business termination, data integrity, command invalidation, installation failure, usability, ease of use, etc., will affect the user.
Problem-solving measures	For a fatal and serious problem, here is a brief explanation of the resolution. Specific solutions that need to be tracked in the leak detection tracking table.
Reason Analysis of development introduction	In addition to analyzing the cause of the bug, the developer will have to analyze the impact of the leak analysis.
Develop solutions	Developing a method to evade leakage test
Test Leak Detection Analysis	In addition to the analysis of the leakage test, the tester must analyze the relevant impact.
Testing Solutions	The method of avoiding leakage test is put forward
Demand Introduction Analysis	The requirement personnel carry on the leakage analysis, the analysis of the leakage from the demand angle, and the related impact analysis
Demand-solving measures	The requirements of personnel to avoid leakage test methods, if the direct cause of the leak, and demand-related, such as the need to change, not informed to test, then the need to improve the control method of change.

From the soul of software testing

Missing elements of the questionnaire