Bug status developers must know

Source: Internet
Author: User
During the project development process, I found that many people are not familiar with the status of this bug after solving the bug proposed by the tester, resulting in the final statistics on the number of bug fixes, and legacy bugs. As a developer, I think it is a basic course to understand the bug resolution status. Here I will list the bug resolution statuses used by developers and hope to help everyone (these are the statuses that developers should modify in the Test Library when solving the corresponding bugs ):
  • Fixed (fixed): the bug has been fixed and passed tests.
  • Invalid (not a bug): the problem describedNot a bug(The tester proposed this bug, but the developer thought it was not a bug ).
  • Wontfix (without modifying the bug, needlessfix): The problem to be describedIs a bug.
  • Later (modified later in the next version): the problem describedIs a bugBut not in the current version. (The next version has been confirmed to be modified)
  • Remind (may be modified to the next version): the problem describedIs a bug,ProbablyNot in the current version (note that later is possible)
  • Duplicate: The problem raised is the same as an existing bug.
  • Worksforme (the bug cannot be reproduced): the bug cannot be reproduced, and the source code does not know why such a bug occurs. If there are more clues about this bug in the future, the bug will be accepted again. (This is for situations where bugs are known but cannot be reproduced)

It can be seen that the bug status is not specified at will, but should be handled according to the specific situation. I see some developers handle the bug in this way: the tester raises a bug, and the developer checks whether the bug is a bug or not, the bug is fixed. At this time, the performance is very irresponsible. However, it is possible that you leave the bug in the product because you set the bug status randomly, which may lead to serious consequences. Remember !!!!

For details about the bug status of testers, refer to "bug status developers are required to know and continue".

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.