Test will: bug classification and promotion solution

There are some initial small test teams , Yes BUG The list may be divided by importance , But there is no type division .

Actually , If you don't BUG Define the error type , The project manager or test manager is not good at confirming the improvement of subsequent quality improvement , Which link of R & D needs more improvement .

Therefore, it is reasonable to BUG The classification of documents is also a submission BUG The premise of . Here's what I did BUG Type classification ：

Version submission problem

Issues related to version submission ：

1. Program file or database script submission error

2. Program file missing or database script missing

3. Relevant documents are not submitted or document submission error

4. Relevant documents are not detailed

5. Wrong version number

Demand question

It involves the problems introduced in the requirements phase ：

1. Problems caused by missing requirements in the requirements document

2. Problems caused by irrationality in requirements documents

3. Problems caused by contradictions in requirements documents

Functional issues

All problems that affect the normal use of functions ：

1. The function required by the requirement is not realized

2. The functions implemented are beyond the scope of requirements

3. The function implementation does not meet the requirements

4. The function cannot be realized or operated normally

5. The database cannot store normally or the stored value is incorrect

6. The interface cannot correctly echo the entered value

7. Data cannot be refreshed in time

8. Link or download error

Exception handling

For abnormal data 、 Handling of abnormal operations ：

1. No information legitimacy check

2. No duplicate judgment for key fields

3. No data length check

4. The abnormal operation is not handled

5. Program exceptions are not handled or handled incorrectly

UE problem

All affect the user's vision / Operational experience problems ：

1. Interface text error or missing

2. Unclear prompt information 、 Wrong or missing

3. Interface style 、 The layout is not uniform

4. Inconvenient operation

5. The operation mode is not uniform

Performance issues

For operation response 、 Stability and other related problems ：

1. The reaction speed of operation is slow

2. Unstable after long-term use

3. When the amount of data is too large, relevant operations are unresponsive or cause errors

Security issues

When it comes to encryption 、session Be overdue 、 Password verification 、 Authority and other related issues ：

1. Data storage 、 Transmission encryption problem

2. Session Expiration time judgment

3. Page access control

4. Account login uniqueness check

5. User login password authentication 、 Password modification, verification, etc

Compatibility issues

Problems related to the use of different software versions or hardware ：

1. Incompatible with operating system version

2. Incompatible with browser version

3. Incompatible with other related software versions

4. Incompatible with hardware

Suggestive questions

Include functional or operational recommendations ：

1. Functional recommendations

2. Interface / Operational recommendations

Conduct BUG Type classification is only the first step , As WEB Class projects , In general , Two on the bright side 、 Three kinds of questions , It is easy to find and modify during self-test , The probability of leaving it to the test is relatively less .

Other problems are often caused by insufficient development time or lack of attention , A lot is left for the testing phase to propose . For this kind of phenomenon , The responsible project manager is sometimes more than willing and less than able , A less responsible project manager , It's possible to turn a blind eye .

As a test team , Want to improve the quality of submitted versions , You can try it in the following ways ：

1. And project team , Confirm that the guidelines for receiving the version are clear , That is, let the project team members know what problems exist , The version will be called back ;

2. Provide P0 Use cases to development , Improve the self-test quality of development ;

3. Sort out the repeated problems of different development , Consult with the project manager on the specific code of each problem , Sort out the knowledge points in the project team , Conduct propaganda in the development team or organize special meetings to explain ;

4. For problems that seriously affect the test efficiency or occur repeatedly , The severity of the questionnaire can be appropriately increased , To attract the attention of the project team .

above , It's a personal fool , Welcome to leave a message together ！