How are Unfixed Defects Usually Marked?

How are Unfixed Defects Usually Marked?
March 05 10:00 2015 Print This Article

Information technology is rather young business segment.

So, software development and web site testing, desktop testing and mobile testing appeared not long ago. But for only a few decades applications, methods and approaches to their creation and testing considerably evolved.

Software products became large multilevel systems. It is no wonder that there are a lot of different errors in such a system. They often appear due to overlooks, ambiguous requirements and misunderstandings. Some of them are critical and influence the main functionality, security or performance of the system, some have little impact and are insignificant.

That is why not all the software bugs, found in course of software testing, are immediately corrected. Unfixed errors are marked by the developers or managers.

Uncorrected Errors May by Marked As:

  • Duplicate. This mark is used when the same error is logged several times. Such situation usually happens when several testers perform functional testing, compatibility testing, user interface testing, etc.
  • Cannot reproduce. This way the defect is marked when the developer cannot reproduce it.
  • Not a bug. This mark is given when the reported issue is in compliance with the requirements and is logged as a defect into the bug tracker by mistake.
  • Later. If the defect is not important for the coming release, it is marked in such a manner.

Related Posts:

  • No Related Posts

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.