ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
Bug Title /
Summary		Make sure you can fit the bug summary line in a tweet-length (less than 140 characters, preferably less than 100).
3
Reader should visualise the bug on reading Bug Title
4
Indication of the impact or consequences of the bug*****************You are what you write*****************

The bug report is the primary work product of most testers. Your bug report is your representative.

Summary line or title is the most important line in the bug report, make sure you can fit a summary line in a tweet-length (less than 140 characters).

Understand who are all your audience, developers are not the only people who read your bugs.

Take the time to make your bug reports valuable.

Every bug deserves its own report.

Never exaggerate your bugs.
5
Should be only one line
6
Should be Crisp and clear
7
8
DescriptionProvide details of how did you encounter the bug
9
Pre requisites ( if any)
10
Steps to reproduce (but not like open IE, Go to Login, enter userid & Password, Click Submit)
11
Provide screenshots / Video / Log files
12
Test data used
13
Compress Videos, Screenshots
14
If there are many files, zip them all together
15
Give a meaningful names to the attachments, screenshots, videos, logs
16
Detail the impact
17
18
GeneralDon't use SMS Lingo or abbreviations
19
Read Seniors, peers and other thought leader bugs (if any ) in the bug tracking system to improve your bug reporting skills
20
Get your bugs reviewed from others ( it doesn't matter even if you are an expert), that will help you to know if the bug is understandable by others
21
Avoid "We" , "I" , "It was observed" , "I looked at "
22
Use facts/data those in favour of your bugs [ A client did not accept any Accessibility bugs we logged, but when we showed them the news that on of their competitior was sued for millions of dollar for not implementing accessibility helped us to get the bug fixed immediately]
23
Always do a Spell check
24
Don't use words like “see” “look” rather use words like “Observe”
25
Annotate wherever required, especially the UI issues
26
Crop unwanted parts of the image
27
Highlight the areas that has issues.
28
References
29
iTest - DS
30
Bug Advocacy - Cartoon Tester
31
32
33
34
35
36
37
Preferred Tools
38
https://www.cockos.com/licecap/
39
Awesome Screenshot
40
Greenshot for Windows.
41
Mac Preview
42
Skitch for Mac
43
If you are using Mac, Mojave > Shift+Command+5
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100