Classification of defect levels

Classification and examples of high levels

Critical data error

Cases:

The number of items in the statistics report and the funds statistics are incorrect.

Patrol work tasks, the defect record defects reported to production, in the defect registration module can see 3 of the same data.

The number of materials purchased is 10, the field and warehouse can be 10 pieces respectively.

All functions are subject to error (e.g., $ or 404 , etc.) under normal operation.

Cases:

Open the Plan Release Approval page, System report 500.

Click the Query button, the system is reported 404.

The main functions are not implemented under normal operation.

Cases:

New, save, delete, send, fallback, recall, export, and query operations were unsuccessful.

The main function is incorrect under normal operation.

Cases:

Check that a project that does not pass can escalate successfully.

Select all items to send, only go to the section.

Export function, the exported file format is garbled, the content is not corresponding to the column name, and the content is incorrect.

In the case of multiple inbound orders at the same time, will be warehousing warehouse for the storage of Guanlan warehouse to report to the manager of the water Supply Bay warehouse approval.

In the new two votes entry record, click on the new page to save the operation will add a record.

In PDA, the information of defect appearance is wrong, and the severity level is not down; In the device information, some fields are not down. such as "Installation Date", "Factory", "voltage rating" and so on.

There are performance issues with the main features.

Cases:

When distributing multiple projects, the system responds slowly, such as distributing 30 items, and the system is not finished for 1 minutes.

When the document is posted, the system appears with a white screen that takes more than 10 seconds to display. (The system response time should meet the requirements specification, the response time requirements of different systems may be inconsistent.) ）

The System Management Authority is disordered, which poses a threat to the system security.

Cases:

There is no authorized User menu, but after the user logs into the system, it can enter the relevant module through the menu and manipulate the data of the module.

Unauthorized users can make factory quotas.

In the role management canceled the new function location of the permission button, in the device account of the substation facilities, Central station, equipment, there are new next-level function location button.

The System business logic relation is not handled correctly, causing the main function error.

Cases:

After the project acceptance, the acceptance status of the project in the library to be released can be obtained continue to release.

To generate an action ticket, you can add an operation step to an approved action ticket, and you should not be able to edit the procedure.

Repair picking materials can be reported during the approval process.

Picking back to the library, the imported picking list is the field delivery list is also a live picking list, resulting in the same material many times back the phenomenon of the library.

Intermediate (Medium) defects

Non-primary functions are not implemented under normal operation.

Cases:

The query page has some query conditions to find out the corresponding data.

In the patrol item definition, when there are only 2 tours, the action of moving the patrol content up or down is unsuccessful.

The material details are not hyperlinked in the document.

The non-primary function is incorrect under normal operation.

Cases:

The title is not sorted correctly.

After adding the main transformer and modifying its technical parameters high voltage rated capacity, the value of the main transformer total capacity in the upper substation page of the equipment has not been modified.

There are performance issues with non-primary functions.

Cases:

Uploading attachments in material systems is slow, and 1M files require more than 30 seconds.

All the functions of the boundary value test, the system error.

Cases:

Large text box is full, save the report 500.

Enter the maximum value of the funds, save the report 500.

Upload large files, the system is always in the upload state.

A large number of items are selected for export and are not exported correctly.

The information in the module is not displayed correctly and is misleading to the user.

Cases:

The capital unit is not displayed.

When you add a recommended unit, the association type shown in the list does not match the input you added.

Display the item details as the project name in the material details list of the document.

In the export field in the Outage plan query, the "cause of power outage" should be "cause of power outage."

The key hints are incorrect and mislead the user.

Cases:

The actual operation succeeded but the operation failed.

In the smart ticket system, the incorrect device name is indicated when the status check is not correct.

Operation ticket, the import operation step was successful, but the prompt was unsuccessful.

Permissions control for non-primary modules is incorrect.

Cases:

When the contract management is authorized to the relevant personnel, the relevant personnel can not see the corresponding data.

Picking list cannot fill in the picking reason when the material clerk approves the product.

The System business logic relation is not handled correctly, causing the non-main work error.

Cases:

After the project is archived, the project is also visible on the escalated page of the project request and on the inquiry page of the application.

Lower (low) defects

Page and record positioning.

Cases:

Change request the 2nd item in the selected list adds a new change, and the system automatically navigates to the first item in the list when the return is complete.

User interface display, alignment, text errors, and so on.

Cases:

The page is too small to display the full content, as long as the page size.

The system displays "account number" as "account".

JavaScript error, but can operate successfully.

The user is almost unlikely to do the operation, resulting in system error.

Classification of defect levels