Do not report such bugs
Software Quality Assurance
Telerik Software Academy
http://academy.telerik.com
The Lectors
 Snejina Lazarova
Product Manager
Talent Management System
 Dimo Mitev
QA Architect
Backend Services Team
2
Bad Bug Report Example
 Vague ones which just report the symptom
 "I just clicked and it crashes"
3
Bad Bug Report Example (2)
 Ones which just use adjectives instead of
numbers
 "System is really slow"
4
Bad Bug Report Example(3)
 Lack of legacy behavioral,
baseline
comparisons etc.
 "it used to work ..."
 "system is slower ( than???)"
5
Bad Bug Report Example (4)
 Bugs in which there is no effort to zero in on
the root cause. No effort on removing the
variables
6
Bad Bug Report Example (5)
 Bugs which do not mention the user impact,
yes includes too techie bugs :)
 "we are using uninitialized variables here…
here… and here…"
7
Bad Bug Report Example (6)
 Bugs with poor reproducibility
information
 "happens sometimes"
8
Bad Bug Report Example (7)
 Bugs which just report the problems
(and not
the steps to reproduce or the
manifestation/symptoms of the problems)
 "feature send mail is broken"
9
Bad Bug Report Example (8)
 The usual deficient in information ones e.g.
with no logs, no customer data info, no
platform info, no SW/HW info etc.
10
Bad Bug Report Example (9)
The "Best One"
11
Bad Bug Report Example (10)
Description:
Error message is stupid.
12
Bad Bug Report Example (11)
Expected result:
Error message is less stupid.
13
Key points for good
bug report
Clear and succinct title
 Bad: Browser
crashed
 Good: Error 404: Page not found when clicking
the Export button
14
Key points for good
bug report (2)
Is it Reproducible?
 Bad: Leave it blank
 Good: "Every time", "Occasionally",
"Unable to
Reproduce"
15
Key points for good
bug report (3)
Description
 Summary – short overview
 What happened – step by step
16
Key points for good
bug report (4)
Supporting information?
 Bad: Leave it blank
 Good: "This error happens for all
event records
that are fees, but works for event records that
are campaigns"
17
Key points for good
bug report (5)
Actual results?
 Bad: "It did not work"
 Good: "Error 404: Access denied"
18
Key points for good
bug report (6)
Expected results?
 Bad: "I expected it to work"
 Good: "I expected to see a popup after clicking
the Run button"
19
Key points for good
bug report (7)
Platform
 Bad: "Windows"
 Good: "Windows 7, Google Chrome
20.0.1132.47m"
20
Key points for good
bug report (8)
Include the Screenshots/Attachments!!!
21
Do not report such bugs
курсове и уроци по програмиране, уеб дизайн – безплатно
курсове и уроци по програмиране – Телерик академия
уроци по програмиране и уеб дизайн за ученици
програмиране за деца – безплатни курсове и уроци
безплатен SEO курс - оптимизация за търсачки
курсове и уроци по програмиране, книги – безплатно от Наков
уроци по уеб дизайн, HTML, CSS, JavaScript, Photoshop
free C# book, безплатна книга C#, книга Java, книга C#
безплатен курс "Качествен програмен код"
безплатен курс "Разработка на софтуер в cloud среда"
BG Coder - онлайн състезателна система - online judge
форум програмиране, форум уеб дизайн
ASP.NET курс - уеб програмиране, бази данни, C#, .NET, ASP.NET
ASP.NET MVC курс – HTML, SQL, C#, .NET, ASP.NET MVC
алго академия – състезателно програмиране, състезания
курс мобилни приложения с iPhone, Android, WP7, PhoneGap
Дончо Минков - сайт за програмиране
Николай Костов - блог за програмиране
C# курс, програмиране, безплатно