Defect / bug severity

Các vấn đề liên quan đến bug/defect và các hệ thống quản lý lỗi
Forum rules
Các bạn chỉ được phép post bài liên quan đến bug/defect và các hệ thống quản lý lỗi.
Post Reply
thuct89
Hoc Tester
Posts: 3
Joined: Tue 25 Oct, 2011 10:04 am
Contact:

Defect / bug severity

Post by thuct89 »

Defect/Bug Severity Definition, Classification, Caution:

Defect Severity or Impact is a classification of software defect (bug) to indicate the degree of negative impact on the quality of software.

ISTQB Definition
  • severity: The degree of impact that a defect has on the development or operation of a component or system.
DEFECT SEVERITY CLASSIFICATION

The actual terminologies, and their meaning, can vary depending on people, projects, organizations, or defect tracking tools, but the following is a normally accepted classification.

Critical: The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.

Major: The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.

Minor: The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.

Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.

Severity is also denoted as:
  • S1 = Critical
    S2 = Major
    S3 = Minor
    S4 = Trivial
CAUTION:
Defect Severity is one of the most common causes of feuds between Testers and Developers. A typical situation is where a Tester classifies the Severity of Defect as Critical or Major but the Developer refuses to accept that: He/she believes that the defect is of Minor or Trivial severity.

Though we have provided you some guidelines in this article on how to interpret each level of severity, this is still a very subjective matter and chances are high that one will not agree with the definition of the other. You can however lessen the chances of differing opinions in your project by discussing (and documenting, if necessary) what each level of severity means and by agreeing to at least some standards (substantiating with examples, if necessary.)



StevenPhuong
Sr. Tester
Posts: 380
Joined: Thu 20 Jan, 2011 9:28 am
Contact:

Re: Defect / bug severity

Post by StevenPhuong »

Bổ sung thêm 1 severity quan trọng nữa trong thực tế khi làm việc sẽ gặp.

S0 = Fatal (trên Mantis) hoặc Blocker (trên Jira). Bug dạng này có độ ảnh hưởng lớn làm tester không thể complete được testing round.

S4 = Trivial ở 1 số cty nó phân ra 2 loại Suggestion & Question 2 loại này đều là S4 và đều ngang cấp nhau
- Suggestion: là đưa ra gợi ý cho DEV. Ví dụ suggest về GUI xấu quá nên sửa, đối với dạng bug này DEV có quyền sửa hay không.
- Question: là dạng bug mà tester không biết DEV sẽ fix hay không vì nó quá nhỏ. Question giống dạng 1 câu hỏi (tuy cũng là bug) mà đôi khi DEV chỉ cần trả lời câu hỏi đó thôi chứ không cần phải fix trong software.



hong0924
Hoc Tester
Posts: 3
Joined: Wed 05 Mar, 2014 8:32 pm
Contact:

Re: Defect / bug severity

Post by hong0924 »

Minh bo sung them cai nay nua cho Jira nhe. Cty minh da dung cai nay 5 nam roi. Minh khong biet cac loai khac nhu the nao, nhung theo minh thi Jira rat tot

Deal-Breaker
- Deal will get canceled if this is not resolved.



Post Reply

Return to “Bug Tracking/Management System - Bug và Công cụ Quản lý Bug”