What Are Main Statuses of Software Bugs?
It is common knowledge that various software bugs appear in course of any software development process. That is why every project includes a test team. Test engineers’ task is to find defects in the application and inform the programmers and other project parties about them.
Modern applications are complex, the errors in them often are tricky and sophisticated. This fact makes the process of error reporting and communication between the testers and developers complicated.
Experts in mobile testing, desktop testing or web site testing know that every software bug has its life cycle. It begins when the bug is discovered during functional testing, cross-platform testing, load testing, etc. and logged into the bug tracker; it ends when the software bug is closed.
The Main Statuses of a Software Bug During its Life Cycle Are:
- New. An error is considered to be new when it is just entered into an error tracking system.
- Assigned. An error is usually assigned to the programmer, who is responsible for fixing it, to the test engineer, who must verify it after fixing during regression testing, or to a manager.
- Resolved. This status is given to a defect when it is fixed and waiting for verification.
- Verified. A software bug is verified when the responsible test engineer confirms that it is corrected.
- Reopened. An error is reopened if it appears after fixing it.
- Closed. A defect is closed if it is corrected, verified and do not require any actions.