Real QA Testing

What makes a good bug title?

May 07, 2020

Any useful bug ticket is one that makes sense to the developer, as well as one that states the problem is some measurable quantity.

A ticket simply stating “The page looks broken” is not a very helpful ticket and will usually draw ire from the developers. Any developer or manager would (or should) ask the questions:

  • What seems to be broken?
  • Are you using it correctly?
  • Are you sure it’s not broken and not a known issue?
  • Do you know the correct operating behavior?

There could be any and all followup questions to the above bug title, but what happens is the QA employee usually wins favor with product management or management and draws the developer into a drawn out ordeal. This process usually also finds other bugs not mentioned in the bug title, leading to restating the above questions.

A more helpful format of the bug title might be “The page on the website at http://www.example.com/faq does not look to have any styling applied and is a white background with black text”. This is a very descriptive observation with a clear problem and would allow the developer to come to a quick determination of what is wrong.

Clear bug titles also help to cut down on reproduction steps, and back and forth with the QA employee or product management.


This website talks about sensical approaches to QA testing and how to really know that your application does what it needs to do day in and day out.