Have you ever had to test a bug case and could not make heads or tails on what it is about?

End up spending a lot of time and effort on deciphering the description and trying duplicating the issue. Asking yourself, what in the world are they talking about?

All this effort and time cost money.

This session will show you how to write up a good defect case, so that whoever has to verify it can do it without having to spend a lot of precise time figuring what the issue is and how to test it.

Money saving topics will include:

  • What is a defect? 
  • Types of defects
  • Who writes a bug report?
  • When should you write up a defect?
  • Elements of a good defect case
  • What happens next once the defect has been created? 
  • Tips on reducing defects