forked from jdm/trainingmontage
-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathbugzilla-triage-tutorial.html
executable file
·190 lines (165 loc) · 10.4 KB
/
bugzilla-triage-tutorial.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
<html>
<head>
<title>Firefox bug triage tutorial</title>
<link rel="stylesheet" href="style.css">
<script src="jquery.min.js"></script>
<script src="magic.js"></script>
</head>
<body>
<div id="floater">
</div>
<div id="begin" class="step initial">
<h1>Bug triage tutorial</h1>
<p>Before we begin...</p>
<p>Do you have an account at http://bugzilla.mozilla.org?</p>
<span class="button" next="change-intro">I have a Bugzilla account</span>
<span class="button" next="setup">Not yet!</span>
</p>
</div>
<div id="setup" class="step">
<h1>Let's get started!</h1>
<p><a href="https://bugzilla.mozilla.org/createaccount.cgi" target="_blank">Create a bugzilla.mozilla.org account</a> </p>
<p>You will need to confirm your account and then log in.</p>
<p><span class="button" next="change-intro">Done!</span></p>
</div>
<div id="change-intro" class="step">
<h1>Time to have some fun.</h1>
<p>Start your training mission:</p>
<p><span class="button" next="triaging">Triaging!</span>
</p>
<img src="images/mission-buggie.png">
</div>
<div id="triaging" class="step">
<h1>How to Triage!</h1>
<p>Bug Triaging is the process of moving bugs logically from state to state, so they get resolved in an efficient and easy-to-comprehend manner. </p>
<p>Go through the <a href="https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=-60d&bug_status=UNCONFIRMED&component=Untriaged&product=Firefox&list_id=7134104" target="_blank">bugs in the Untriaged component which have the status UNCONFIRMED</a>. Choose a bug from the list.</p>
<p><span id="run-hint" class="hint">Refine the search to the bugs of your OS. Read the summaries to understand what the bugs might be about. This will help you choose one to triage. You can sort by OS or edit the search to create a new query. The edit search link is at the bottom of the page. Give it a try!
<img src=images/mission-edit-search.png>
</span></p>
<p>
<span class="button" next="bug-chosen">I've chosen a bug</span>
<span class="button" unhide="run-hint">I don't know what bug to choose</span>
</p>
</div>
<div id="bug-chosen" class="step">
<h1>You have chosen a bug</h1>
<p>Read the bug. Read its summary, description, comments. Do you understand it enough that you know how to try to replicate the bug?</p>
<span class="button" next="bug-understood">I understand what the bug is about</span>
<span class="button" next="bug-notunderstood">I can't understand the bug</span>
</p>
</div>
<div id="bug-notunderstood" class="step">
<h1>I can't understand the bug</h1>
<p>Leave a comment to ask for more information about the bug. You may want to use the needinfo flag. </p>
<p> Please cc [email protected] on the bug, so that I know you participated in this training mission! Thanks!</p>
<p><span id="hint-understand" class="hint">Near the end of the bug page, after the comments, there is a checkbox labelled needinfo. When you check it, you can select the bug reporter, or manually add an email address to ask a person for more information. <br>
<img src="images/mission-needinfo.png">
</span></p>
<span class="button" next="bug-chosen">I've added the comment</span>
<span class="button" unhide="hint-understand">I need a hint!</span>
</p>
</div>
<div id="bug-understood" class="step">
<h1>You can understand the bug</h1>
<p>Check to see if the bug is a duplicate of an already existing bug. Open a new tab, and search for other bugs that use the same keywords and describe the same problem. </p
<p><span id="hint-duplicate" class="hint">Here is a <a href="https://developer.mozilla.org/en-US/docs/Screening_duplicate_bugs" target="_blank">detailed description of how to detect duplicate bugs.</a> If you're not sure if it's a duplicate, explain what you think in the comments and include the bug number of a possible dupe.
</span></p>
<span class="button" next="bug-duplicate">It is a duplicate </span>
<span class="button" next="bug-notduplicate">It's not a duplicate</span>
<span class="button" unhide="hint-duplicate">I need a hint!</span>
</p>
</div>
<div id="bug-duplicate" class="step">
<h1>The bug is a duplicate</h1>
<p> Close the Bug as RESOLVED DUPLICATE. You should enter the duplicate bug number. Keep whichever bug was reported first, and has good information such as comments and attachments on the bugs. Be sure to thank the bug reporter and be polite; we want them to know we appreciate their efforts, even if the bug report is not needed. </p>
<p> Please cc [email protected] on the bug, so that I know you participated in this training mission! Thanks!</p>
<span class="button" next="change-intro">I've done!</span>
</p>
</div>
<div id="bug-notduplicate" class="step">
<h1>The bug isn't a duplicate</h1>
<p>Check if it's a support question. Many bug reports are not about bugs but are for common issues answered in the Mozilla <a href="https://support.mozilla.org" target="_blank">support forums.</a></p>
<p>
<span id="hint-supportQuestion" class="hint">Is the reporter asking questions about how to use Firefox, or reporting a vague problem like Firefox being slow, or malware popups?
</span>
</p>
<span class="button" next="bug-supportQuestion">It is a support question </span>
<span class="button" next="bug-notSupportQuestion">It's not a support question</span>
<span class="button" unhide="hint-supportQuestion">I need a hint!</span>
</p>
</div>
<div id="bug-supportQuestion" class="step">
<h1>The bug is a support question</h1>
<p> Let the reporter know where to find help. Add link to <a href="https://support.mozilla.org/" target="_blank">support </a> Close the Bug as RESOLVED INVALID. </p>
<p>Please cc [email protected] on the bug, so that I know you participated in this training mission! Thanks!</p>
<span class="button" next="change-intro">I've done!</span>
</p>
</div>
<div id="bug-notSupportQuestion" class="step">
<h1>The bug isn't a support question</h1>
<p>Keep on doing triaging and check if the bug needs a testcase</p>
<p> Ask the reporter for a reduced test case code or a URL. You could generate a test case and attach it.</p>
<p>
<span id="hint-testcase" class="hint">A testcase can be an image, an .html page or an url depending on the specific bug. For some bugs in web pages, you can create the simplest possible page that triggers the bug. It can be handy to use a tool like <a href="http://jsfiddle.net">http://jsfiddle.net</a>.</span>
</p>
<span class="button" next="bug-replicate">Replicate the bug</span>
<span class="button" unhide="hint-testcase">I need a hint!</span>
</p>
</div>
<div id="bug-replicate" class="step">
<h1>Now it's really fun :)</h1>
<p>Reproduce the scenario reported from the bug on the same Firefox version, on the same OS or a different one. </p>
<span class="button" next="bug-sameOS">Replicate the bug on the same OS</span>
<span class="button" next="bug-differentOS">Replicate the bug on a different OS</span>
</p>
</div>
<div id="bug-sameOS" class="step">
<h1>...so here we are :)</h1>
<p>Can you reproduce the bug on the same OS?</p>
<span class="button" next="bug-reproducible">I can reproduce the bug</span>
<span class="button" next="bug-notreproducible">I can't reproduce the bug</span>
</p>
</div>
<div id="bug-reproducible" class="step">
<h1>You can reproduce the bug</h1>
<p>Comment that you can replicate the bug, add info you think can be useful; Add the build id of the firefox version and user agent used</p>
<p>If it is a Mozilla bug mark it NEW. Assign the bug into a product and component, orif you aren't sure where it belongs, tag it needs-component. Tag the bug with other triage tasks that may be needed.</p>
<p>
<span id="hint-reproducible" class="hint"> For example User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko 20100101 Firefox/23.0
buildID :20130708202947 (you can find the buildID typing about:config in the url bar and search for buildID).</span>
</p>
<span class="button" next="change-intro">I've done!</span>
<span class="button" unhide="hint-reproducible">I need a hint!</span>
</p>
</div>
<div id="bug-notreproducible" class="step">
<h1>You can't reproduce the bug</h1>
<p>Ask the reporter need-info (especially if it's an old bug ) to see if it's still valid and tag as needs-replication in the whiteboard </p>
<p>or resolve it as WORKSFORME or tag it as need-replication</p>
<span class="button" next="change-intro">I've done!</span>
</p>
</div>
<div id="bug-differentOS" class="step">
<h1>And now? :)</h1>
<p>Can you reproduce the bug on a different OS?</p>
<span class="button" next="bug-reproducibleDiff">I can reproduce the bug</span>
<span class="button" next="bug-notreproducibleDiff">I can't reproduce the bug</span>
</p>
</div>
<div id="bug-reproducibleDiff" class="step">
<h1>You can reproduce the bug</h1>
<p>Add comment and eventually change the bug platform ( Platform field of bugzilla)</p>
<span class="button" next="bug-chosen">I've done</span>
</p>
</div>
<div id="bug-notreproducibleDiff" class="step">
<h1>You can't reproduce the bug</h1>
<p>tag as needs-replication in the whiteboard and leave a comment </p>
<span class="button" next="bug-chosen">I've done</span>
</p>
</div>
<div id="contribute">
<p>Created by <a href="http://www.joshmatthews.net">Josh Matthews</a>. Training Mission content added by <a href="http://www.tizianasellitto.it/blog/">Tiziana Sellitto</a>. Patches are welcome on <a href="https://github.com/tizianasellitto/trainingmontage">github</a>. </p>
</div>
</body>
</html>