Shulou(Shulou.com)06/01 Report--

What are the specifications for the use of the Bugzilla system? in view of this problem, this article introduces the corresponding analysis and solutions in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

The status of a Bugzilla

Status description

Unconfirmed

Undetermined (for feedback Bug/ requirements) confirming confirmation (for feedback requirements) new new

Assigned assigned resolved resolved verified verified closed closed reopened reopened

Second, the solution of Bugzilla

Solution description

Fixed fixed waitpacket

Waiting for packaging (abandoned, to be deleted) invaild invalid wontfix decides not to change later subsequent version duplicate repeats

Worksforme

Unable to retry walkaround to circumvent remind

Remind moved that it has been removed

3. Submission form of Bugzilla

Submit form description file file built upgrade package code code

Note: the submission form can only be used when the status is resolved and the solution is fixed.

Four Bug priority definition

Priority defect feedback BUG internal BUG

High

1 the customer's network or business system is interrupted or paralyzed due to our company's equipment; [time limit]: 24 hours

2 serious problems or unavailability of the equipment, causing the customer's network or business system not to work properly [time limit]: 48 hours

1 prevent the test from continuing to run

2 the test schedule of the project is greatly affected

(3) affecting the adoption of the final item

4 affect the release of the current test upgrade package

5 known problems also exist in the external release version, and there is a risk of disrupting or paralyzing the customer's network or business system.

[time limit]: 48 hours

Medium

There is a serious problem with online serial equipment, but the customer's network or business is not affected.

[time limit]: 72 hours

From the current point of time, the degree of urgency of the problem is not high, time limit requirements:

1 must be resolved in the closing version

2 must be resolved in the current test upgrade package release version

3 solve the problem within the deadline time limit negotiated by both the test and the developer

There is a problem with the low equipment, but it can still function properly. There is no special requirement on the time limit.

If it does not affect the normal use of the customer, if the development has time, it will be included in the plan.

[time limit] one week

Note: the priority of defects can be adjusted according to the actual situation over time.

5 Bug severity level specification

Sample Bug related products for severity level definition criteria

Critical

1 cause the customer's network or business system to be interrupted or paralyzed

2 system crash / suspend data loss or serious memory leak causing the system to be unavailable

(3) there are security loopholes in the system that are easy to * and do high harm.

[public platform] Bug 24149: after the device's external network port is suspected of LAND***, the depletion of NAT pool resources leads to abnormal TCP communication.

[eps] bug 10581 found memory and handle leaks

Major

1 the function is seriously unavailable, or affects the completion of the business process of the system itself

(2) there are security loopholes in the system that are easy to * * or highly harmful.

[public platform] Bug 25432 URL filtering function fails

[EPS] about 5 minutes after the Bug 13915 proxy port was powered on, the self-protection function failed.

Nornal

1. The functional part is not available, and the impact is general: it does not affect the normal operation of the customer's business system, nor does it affect the completion of the system's own business processes.

2. There are general security vulnerabilities in the system.

IPS] Bug 23624 29001 rule mistakenly blocks the popularity of online video

[public platform] Bug 25657: after clearing the report, the http404 prompt appears on the page

Trivial

UI display, text, text and other errors, and does not affect the function

Comments of the nature of the enhancement proposal

Six feedback defect handling instructions

6.1 defect handling instructions for feedback

1) for the performance statistics involved in feedback Bug, see the performance Dictionary.

2) Bug in the resolved state must first change the state to verified (verified) before it can be changed to closed (closed). Before changing to verified status, you must fill in the "defect introduction stage" field (except if the solution is: invaild (invalid), duplicate (duplicate), worksforme (non-reproducible))

3) for the feedback Bug that has problems at the customer site and cannot be reproduced internally, if you can determine that the problems may be caused by product defects, after communication and confirmation between the test manager and the product manager, you can first set the Bug status to NEW. Subsequently, if it is finally confirmed that it is not a product defect, the solution of Bug will be set to INVAILD (invalid); if it is finally confirmed to be a product defect, it will be dealt with according to the defect. (note: the statistical method for the related performance "average resolution cycle of feedback defects in the product maintenance phase" is from the first unconfirmed (undetermined for feedback bug/ requirements) to VERIFIED, excluding invalid Bug. )

4) if the feedback Bug of customer site is long or difficult to reproduce, but cannot be reproduced internally, under the condition that it can ensure that other customers will not repeat, and the relevant parties can accept the circumvention solution, we can first avoid the solution by setting the solution to WALKAROUND and the status to RESOLVED. After that, the technical support manager waits for a month for the customer site to no longer have problems and does not receive the same defect feedback. The feedback Bug can be turned off. If there is another problem or the same defect feedback is received while waiting, turn the feedback Bug back on REOPENED. If the same problem occurs after the feedback Bug is closed, create a new feedback Bug to track, and no longer reopen the closed feedback Bug.

5) the confirmation and recurrence of feedback defects shall be the responsibility of the product quality department (developers in special or emergency situations can deal with them urgently). The operation of changing the UNCONFIRMED state to the NEW state is generally completed by the test manager or tester after the problem is confirmed.

Seven requirements processing instructions for feedback

7.1 requirements processing instructions for feedback

1 for feedback requirements in unconfirmed (undetermined) state, the status must be changed to new first, and cannot be changed directly to resolved (except if the solution is invaild invalid duplicate duplicate

2 feedback requirements in the new state must first change the status to assigned (assigned), and cannot be changed directly into resolved (except for those with invaild duplicate as the solution). Before changing to assigned, you must complete the 'deadline' field

3 for feedback requirements in confirming status, the status must be changed to unconfirmed first

7.2 demand state machine with feedback

Eight-process bug processing instructions

8.1 State Machine of process bug

9 Deadline fill in the instructions

1 for the product feedback requirements that are feasible and planned to be realized in the follow-up, the product manager and the test manager jointly evaluate the demand realization cycle, propose a demand realization plan, include it in the demand processing system, and notify the system engineer and product marketing manager.

The demand realization plan at least includes the time point of completion of the battlements plan (deadline, refers to the time point in which the status of the verified verified is verified) and the workload is estimated (in person * hours), which can include the version number and implementation method of the planned implementation, etc.; the product manager is required to complete the task within 2 working days after receiving the notification of demand processing, and the demand record status is set to assigned assigned in bugzilla

2 to confirm the product feedback defects that need to be repaired, the product manager and the test manager together evaluate the defect repair and complete the verification cycle. After the discussion, the product manager gives a repair plan, including the time point promised to complete the plan (deadline, the point in time to the verified verified status), records in the bugzilla system, assigns responsibility, and sets the defect record status to assigned (assigned).

3 if the system engineer, product marketing manager or product support manager thinks that time commitment can not meet the requirements of the market, they can consider convening a review meeting to review, or escalating the event to a higher level of leadership coordination.

Instructions for the use of the bug introduction phase field

10.1 purpose

Problem backtracking-defect analysis after product release for product system quality improvement

Process related problem discovery and process improvement

10.2 range

Add a new field to buggilla to locate and retrace the introduction phase of bug in the lifecycle after release

Bug for feedback in buggilla, internal test will not be executed for the time being

10.3 instructions for use

10.3.1 definition of the introduction phase

The introduction phase is initially defined as 6 items: "market demand", "frequency measurement demand", "design", "coding", "version management" and "historical legacy". You can see it when querying bug to update bug, as shown in the following figure:

10, 3, 2, fill in the instructions.

This phase is filled in by the developer. When the person responsible for the feedback bug points to a developer, the developer responds and processes the bug while locating the introduction phase of bug. As shown in the figure above, you can select the introduction phase in the drop-down box to the right of the defect introduction phase.

When the developer is unable to locate, the product manager must be informed, and the product manager shall carry out the positioning

In order to ensure the accuracy of the problem positioning and reduce the deviation of the follow-up system improvement trend analysis, the problem positioning needs to be confirmed by the relevant personnel to ensure that the problem positioning is agreed within the group and there are no differences. The confirmed personnel are as follows:

Feedback bug positioned as the "design" phase requires confirmation by the architect or product manager

Feedback bug positioned as "product demand" phase needs to be confirmed by SE or product manager

Feedback bug positioned as "market demand" stage needs to be confirmed by the product marketing manager

Feedback bug positioned as "version management" requires confirmation by project-level configuration administrator or product manager

Feedback bug positioned as a "historical legacy" requires confirmation by the product manager, etc.

It is usually recommended that when the feedback bug is closed, the positioning of the introduction phase of bug should also be determined, except in the case of differences in positioning, which is allowed until an agreement is reached.

Due to the needs of process improvement and system improvement, the project management team of the development center will regularly extract relevant data for a period of about 2 weeks (the middle of each month) or 4 weeks (the last week of each month). Please submit it within the relevant cycle as far as possible.

This field was completed on a trial basis in May 2009.

National Day holiday test bug submission specification

When submitting BUG, testers should submit BUG-related information in accordance with the following format requirements.

ENV and other places of content, each product according to its own characteristics, add or reduce relevant content items, for example, the RCM group may also need to include the number of plug-ins, the number of vulnerabilities, the version of the scanned system and other information.

Twelve develop bug reply content specification

After completing the BUG positioning and BUG repair work, the developer should reply to the BUG in accordance with the following format requirements while updating the BUG status. Try to fill in the following clearly, and you can omit the content that is not involved.

Thirteen bug Verification Specification

Fourteen bugzilla management specifications

Description of the main fields in the Tenth five-year Plan

The answers to the questions about the specifications of Bugzilla system are shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.