Maybe you haven't seen the value of an error management system; maybe you are being flooded by a large number of test data, and urgently need a product defect record and a good helper; maybe you are passing well, Database and other ways to continuously develop and improve an error tracking system. Mozilla has provided us with a shared free tool buzilla. As a product defect record and tracking tool, it can create a perfect bug tracking system, including report bugs, query bug records and generate reports, processing resolution, management The system initializes and sets four parts. And have the following characteristics:
1. Based on web way, easy installation, easy to run, safe and safe to manage.
2. It is conducive to the clear conversion of defects. This system uses the database to manage, providing a comprehensive detailed report entry, generating a standardized bug report. Provide a large number of analytical options and powerful query matching capabilities, BUG statistics can be combined according to various conditional combinations. When the error changes in its life cycle, developers, testers, and managers will promptly obtain dynamic change information, allowing you to get history records and refer to this record when checking errors.
3. The system is flexible, powerful configible capabilities. Buzilla tools can set different modules for software products and set developers and testers to different modules; this can be automatically sent to the designated responsible person when submitting reports; and can set different groups, permissions Can also be divided. Set different users differently, and can be effectively controlled. Allows the setting of different severity and priority to manage errors in the wrong life, from the initial report to the final solution, ensure that the error will not be ignored, while the attention can be concentrated in priority and severe degree Error.
4. Automatically send Email to notify the relevant personnel. Automatically send the latest dynamic information to the different responsible persons, which effectively help testers and developers communicate.
Below we will document the specific use of this tool in accordance with Bugzilla's operating instructions, Bugzilla administrators. There are many views from individual use experience, and please have an ax.
Bugzilla operating instructions
1, user login and setup
1.1 User Login 1. User Enter the server address http://192.168.1.6/bugzilla/. 2. After entering the main page, click [ForgeTly Stored Login], then click [Login in] to enter. 3. Enter the registration page, enter the username and password to log in. The user name is an Email address, and the initial password is the user name. 4. Forgot your password, enter your username, click [Submit Request] to reset it according to the received message.
1.2, modify the password and set 1. Login After logging in, [Edit Prefs] -> [Accout Settings] is modified. 2. [Edit prefs] -> [email settings] for email settings. 3. [Edit prefs] -> [permissions] permission query
2, bug processing process
2.1, report BUG
2.1.1 Test staff report BUG 1. Please check first. Confirm that the bug report to be submit will not exist in the original record. If you already exist, don't submit, if you have any suggestions, you can add your comments in the original record, tell the owner, let the BUG's home Go to this and go to modify it. 2. If BUG does not exist, create a valid BUG report to submit. 3. Operation: Click New, after selecting the product, fill in the following table. 4. Fill in the table: Assigned to: Owner set by default for the air, or manually. CC: You can use "," can be separated. The following cases are described in detail in the DESRIPTION: 1) Step 2 of the Discovery Problem The case where the above steps appear. 3) It is expected that the correct result should appear. Select Group settings to qualify this bug to group permissions, if it is empty, it is open. 5. Operation Results: BUG Status You can select Initial State as New or Unconfirmed. The system will automatically notify the project team leader or directly notify the developer. 6. Help: Bug Writing Guidelines2.1.2 Developer Report Bug. 1. The specific method is reported to the tester. 2. Difference: BUG The initial state will be automatically set to Unconfirmed, and the person to be tested is determined to become "new".
2.2, BUG different processing
2.2.1 BUG's owner (OWNER) After processing the problem, the solutions and methods are proposed. 1. Give the solution and fill in Additional Comments, you can also create attachments (such as changing submission) 2. Specific operation (fill in the form) 3. Fill in the table: Fixed Description Problem has modified the issue of Invalid descriptions is not a bug (after an incorrect, cancel) Wontfix descriptions will never be fixed. The problem description of the Later will not be resolved in this release of the product. The problem description of Duplicate is a copy of the BUG existing. Attempts to regenerate this bug in Worksforme is invalid. If there is more information, reassign this bug, and now use it to archive it.
2.2.2 Project Portal or Developers Re-specify the BUG's home. (OWNER) 1. For this purpose, BUG is not worthy of its own range, can be set to Assigned, waiting for the tester to re-specify. 2. To this end, BUG does not belong to its own range, but knowing who should be responsible, enter the Email of the specified person directly, perform RESSIGNED. 3. Operation: (Options are as follows) * Accept bug (Change Status to assigned) * Reassign Bug to * Reassign Bug to Owner and qa contact of successd Component 4. Operation results: At this time, the BUG state changes again to NEW, and this bug's Owner becomes a person specified.
2.2.3 Tester verifies the modified bug. 1. The tester queried the developer's modified bug, ie status "resolved", resolution is "fixed". Repeat. (Create Test Case Accessories) 2. After verifying, modify resolution is verified. After the entire product is released, modify it to close. If there is still a problem, reopened, the state is revert to "new", and mail notifications. 3. Specific operation (optional item) 1. Leave as resolved fixed 2. Reopen bug 3. Mark Bug As verified 4. Mark Bug as closed2.2.4 bug reporter or other privilege-free user modification and supplement BUG 1. You can Modify the contents of the bug. 2. You can increase the establishment of an attachment, add relevant, and add some comments to explain what you are doing and why do you do. 3. Operations: Whenever some people modify the bug report or add a comment, they will be added to the CC list, the changes in the bug report will appear to be sent to the owner, the writer and the CC list Email.
2.2.5 Tester confirms whether the BUG reported by the developer is present. 3. Details: Select "CONFIRM BUG (CHANGE STATUS TO NEW)", make commit. 4. Operation results: The status becomes "new".
2.3, query bug
1. Enter the bug ID directly, click on the Find query. You can view the BUG's activity record. 2. Click Query and enter the condition for query. 3. Query the history of BUG activities 4. Report. 5. Help: Click Clue.3, about permissions
1. Group members have the right to query the bug, but cannot be modified. 2. BUG's Owner and Reporter have the right to modify. 3. Users with special permissions have the right to modify.
4, BUG processing process
1. After the tester or developer discovers bug, it is determined which module belongs to which module is brought, after filling the bug report, notify the project team leader or directly notify the developer through the Email. 2. The project team leader re-corrected to the developer to which the BUG is assigned according to the specific situation. 3. After the developer receives Email information, it is determined whether it is a range of modifications. 1) If not, reassigned to the project team leader or the developer that should be assigned. 2) If it is processed, resolved and give a solution. (Create patch attachments and supplementary description) 4. Test staff queried developers' modified bugs for retest. (Create Test Case Accessories) 1) After verification, the modified state is Verified. After the entire product is released, modify it to close. 2) There is also a problem, reopened, the state is revert to "new", and email notifications. 5. If this bug has never been processed in a week. Bugzilla will always harass it with Email until action.
5, a bug survival cycle
Bugzilla Administrator Operation Guide
1. Main work content:
1. 1 Definition of Products, Versions (Versions), and Modules, and specify the developer (Owner) and QA Contact of the module.
1.2 Group definition and division
1.3 Definition of the severity and priority of the BUG in the test
1. 4 Add users and set all the groups, permissions.
1. 5 Settings 1) URLBASE: Enter the server IP address where the bugzilla tool is located. 2) UsebugGroupSentry: Set to ON, you can group. 3) Whindays: bug is not processed within the deadline set by Whindays, will automatically retransmate, and the default is 7 days. 4) DEFAULTPRIORITY: Set the default priority 5) CommentonResolve: Set to ON, the system will force the developer to complete the BUG, you must fill in the modified content.
2, basic operation:
2.1 Creating a default administrator user. Run Checksetup.pl. Run Checksetup.pl if you accidentally delete the administrator.
2.2 Manage users
2. Increase the new user Click on the lower right corner of the page [Users], Submit, appears [Add New User] page. Enter the corresponding input. Login Name: Generally, the email address can be set to other identifiers.
2.2 Prohibiting a user can fill in the Disabled Text input box.
2.3 Modifying users can modify user registration names, passwords. Set the permissions of the permission QA generally set to: Canconfirm, EditBugs Developer permissions set to: NONE Packet Control: Group3, Manage Group
3.1. Increase Group Edit GroupàAdd Groups (New User RegexP) -> Add in NEW / ACTIVE Selection) -> Add
3.2 Modify Group, Submit. 4. Manage Product and Component a) Add Product B) Component Corresponds to an Owner (Make Fixed), QA Contact, COMPONENT NUMBER OF UNCONFIRMED = 10000, this product will select BUG's initial state (Unconfirmed, New)
