Several states of BUG in defect management of software testing

关注我，每天分享软件测试技术干货、面试经验，想要领取测试资料、进入软件测试学习交流群的可以直接私信我哦~~

In the process of project testing, we often find many problems that are inconsistent with the requirements or contrary to the user's habits, and then raise the problem to the development. After the development is solved, the test is passed to us, and the problem is over. However, if you only verbally raise issues to the development or use txt, word, excel, etc. to feedback issues to the development, effective tracking cannot be achieved. At this time, a defect management tool is needed to help us manage defects and achieve a closed loop.

A commonly used defect management tool

In the project, in addition to the tools developed by the company itself, the top defect management tools used by testers are: Zen Tao, Bugzilla, Jira, Bugfree...

1. Zen Tao

ZenTao is the first domestically produced open source project management software. Her core management idea is based on the agile method scrum, with built-in product management and project management. At the same time, it supplements test management, plan management, release management, and document management based on the current domestic research and development status. With functions such as, business management, etc., the requirements, tasks, bugs, use cases, plans, releases and other elements in software development can be tracked and managed in an orderly manner in a single software, which completely covers the core process of project management.

2.bugzilla

Bugzilla is an open source bug tracking system (Bug-Tracking System), which can manage the entire life cycle of bug submission (new), repair (resolve), and close (close) in software development.

3.jira

JIRA is a project and transaction tracking tool produced by Atlassian. It is widely used in defect tracking, customer service, demand collection, process approval, task tracking, project tracking, and agile management.

4.Bugfree

BugFree is a bug management system written independently using PHP+MySQL based on Microsoft's R&D process and bug management concept. Simple and practical, free and open source (following GNU GPL). Naming BugFree has two meanings: one is to hope that the software has fewer and fewer bugs (Bugs) until there are no; the other is to indicate that it is free and open source, and everyone can use it freely to spread (Free).

Two common states of defects

For a problem, its processing is a cycle, and different stages of the cycle have different states. Its person in charge is different in different states. We often divide defects into submission, receiving, verification, closing, reopening, returning, postponement, etc.

1. New

After the problem is found and confirmed during the test, the bill of lading will be carried out on the defect management tool. We will fill in the defect discovery conditions, operation steps, expected and actual results, logs, screenshots, etc. on the bug list, and select the test version And according to the module assignment development, after saving it, it will enter the new state.

2. Submit

After entering the new state, confirm that the filling is correct and confirm whether it is a problem next time, submit a bug, and enter the submit state.

3. Receive/call back

After the bug is submitted, the bug will be added to the pending list of the designated development, and the development will accept it if it is considered a problem, otherwise it will be returned and the basis for the return will be explained. The test in some tools believes that the defect returned by the development is indeed a problem, and it can also be returned to the development for processing and explain the basis for the return, without the need for development to receive directly back to the receiving state.

4. Verification

After the development receives the bug, the problem is solved, and the test is submitted for verification, and then it enters the pending verification state.

5. Close/open again

After the test passes the verification of the problem to be verified, the bug is closed, and then it enters the closed state. If the problem occurs again in subsequent versions after closing, the bug can be opened, that is, reopened.

6. Postponement

After the development receives the bug, the impact of the problem is low after PM and testing and product confirmation. This version may not be resolved. After the subsequent version is resolved, the development will change the bug status to deferred processing.

In fact, if you subdivide it, you can actually separate a few more states, such as being resolved... and so on.

4 levels of three defects

In the testing process, in order to handle the speed or time corresponding to the known problems, we generally divide it into 4 levels, but the names of each company are different, such as (1, 2, 3, 4) (minor, normal) , Serious, blocking)... etc. Many names, but they all have the same meaning.

Blockage: Causes system crashes, crashes, and endless loops, resulting in database data loss, connection errors with the database, loss of main functions, and missing basic modules. Such as: code error, infinite loop, database deadlock, important first-level menu functions cannot be used, etc.

Critical: The main functions of the system are partially lost, the database is saved and called incorrectly, and the user data is lost. The first-level function menu cannot be used but it does not affect the testing of other functions. The functional design is seriously inconsistent with the requirements, the module cannot be started or called, the program restarts, automatically exits, the calling conflict between related programs, security issues, stability, etc.

General: The function is not fully realized but does not affect the use, and the function menu has defects but does not affect the system stability.

Minor: This kind of problem often does not affect the normal execution of user operations, but there are some small flaws; or there are constructive problems at the moment.

If you

① Engaged in functional testing and want to advance automated testing

②I have been in the testing industry for one or two years, but still can’t type code

③ Interviews with big companies but repeatedly bumped into walls

I invite you to join the group! Come on~~Tester,313782132(There are technical experts in the Q group to communicate and share together, the value of learning resources depends on your actions, don’t be a "collector") Get more technology and interview materials from major factories

Golden nine silver ten interview season, job-hopping season. The information compiled for everyone is organized around [software testing]. The main content includes: python automation test exclusive video, Python automation details, a full set of interview questions and other knowledge content.May you and I meet and you will find something! Follow me to receive~

If the article is helpful to you, please reach out to make a fortune and give me a like. Thank you for your support. Your likes are my motivation for continuous updating.