Bug

We are going to introduce following:

§       1. What is a Bug

§       2. The Bug elements

§       3. The life cycle of a Bug

 What is a bug?

1.  A formatted form. can managed

2. Reflect an existing issue

3. The Carrier of Communication

4. Quality track bases

5. Workload measure

6. Case measure

Why bug is a formatted form. can managed?

Put all involved people at same page by a specific format:

• Easy write by QA with same template
• Easy read by Dev. with same template
• Easy to classify for time saving
• Easy to assign resources
• Easy to track
• Easy to analysis
• Easy to communicate

How bug reflect an existing issue?

Included all required information to it clearly:

• Number
• Type
• Reporter
• CC List
• Assigner
• Product information
• Status and Resolution
• Priority and Severity
• Content
• Flags
• Summary
• Environments
• Build Version
• Parameters and Data
• Pre-configuration
• Steps
• Expected result
• Actual result
• Workaround
• Attachment
• Related bugs
• Dev. comments
• QA comments
• Management comments

What be carried in communication?

All information that used to fix and track bug:

• The all required information to reproduce the issue
• The Dev. fixing information
• The QA provided additional information
• The QA verification information
• The status information
• The handling information

When track quality base on bug?

If the bugs affect the original test plan in progress:

• Bug is missed
• Bug is a blocker
• Too many bugs were found in specific functional area
• Too many reopening happened
• Resources changed
• After functional testing and before regression testing
• After a new version released
• Before a plan be made(*)

Whose workload can measure?

Measuring different roles’ workload before and after milestone:

• Fixed rate
• Fixed time
• Fixed quantity
• Reported rate
• Reported quality
• Reported quantity

Where measure the case base on bug?

• The case quality
• The case quantity
• The case deep
• The case span
• The case priority
• The case severity

The life cycle of a Bug

Phase:

• Opening ( New, Assigned, Reopened and Resolved)
• Closed (Verified and Closed)

Role:

• QA – Assigned, Resolved, Verified and Closed
• Dev. – New, Assigned and Reopened