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
191
192
193
194
195
196
197
198
199
200
201
202
|
---
title: একটি Testday আয়োজন
slug: Mozilla/QA/Organizing_a_Testday
translation_of: Mozilla/QA/Organizing_a_Testday
---
<p>Please remember that the following is only a rough guideline. The more effort you put into preparing your testday, the more likely it is to be successful. Give yourself, and the community, ample time to prepare for the event. Above all else, experiment and have fun with your test day.</p>
<h4 id="Planning_Your_Event">Planning Your Event</h4>
<div>The following should be done no later than one week before your event:</div>
<div> </div>
<ol>
<li>Once you have a topic in mind, pick a day to schedule your event — check the <a href="https://quality.mozilla.org/events/">calendar on QMO</a> for availaility</li>
<li>Create a test plan to define success criteria, declare a designated spot for signups for mentors, set a schedule (e.g, <a href="https://etherpad.mozilla.org/testday-20141024">past event test-plan</a>)</li>
<li>Publicize and post the event on QMO (if need be, ask QA staff in IRC for assistance) — a valuable post must contain a request for mentorship sign-up and links to available documentation (e.g, <a href="https://quality.mozilla.org/2014/09/volunteers-needed-for-testdays-relaunch-initiative/">see past event notice</a>)</li>
<li>Broadcast your event — Follow our suggested communication list below to help broadcast and publicize the event</li>
<li>Enlist mentors to help facilitate and educate throughout the event — gather contact information to ensure that they're able to attend during the event</li>
</ol>
<h4 id="The_Day_Of">The Day Of</h4>
<ol>
<li>Make sure the IRC channel topic is updated to point people to your test plan</li>
<li>Be proactive in greeting people and removing barriers for them to contribute - ask questions and engage with people who join the channel</li>
<li>Recommend sign-up to dev-quality and mozillians to attendees for future event notice</li>
<li>Provide a feedback survey to participants, <a href="https://docs.google.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/viewform">clone or copy this example document</a></li>
</ol>
<h4 id="After_the_Event">After the Event</h4>
<ol>
<li>Provide a followup post in your communication channels thanking those who attended</li>
<li>Plan a future event</li>
</ol>
<h4 id="Tips_for_Success">Tips for Success</h4>
<div>The following is a list of tips which will hopefully make your event more successful.</div>
<div> </div>
<ul>
<li>Make sure you have enough mentors committed to your event, otherwise it might come off as disorganized</li>
<li>Make sure your project is ready for testers; remember that most testers are just Firefox users</li>
<li>The more you advertise the greater your audience</li>
<li>Give yourself enough time to prepare the material</li>
<li>Give your audience enough time to familiarize themselves with any material needed as a prerequisite before the event</li>
<li>Have a peer review your event material and attempt an activity to test the ease of your ramp-up path</li>
<li>Don’t be afraid to reach out to external communities (especially true for development related testdays)</li>
</ul>
<h4 id="Communication_Channels">Communication Channels</h4>
<p>The following is a list of the various communication channels we should use to advertise. Choose as many or as few as you see fit.</p>
<h5 id="Mailing_Lists">Mailing Lists</h5>
<ul>
<li>dev-quality: the primary public mailing for Mozilla QA</li>
<li>events: use if your event incorporates physical meetup</li>
</ul>
<h5 id="Social_Networks">Social Networks</h5>
<ul>
<li>Twitter: @MozillaQA is our Twitter account</li>
<li>Facebook: MozillaQA is our Facebook account. Note that QMO Event posts are automatically syndincated to Facebook</li>
<li>Yammer</li>
<li>Google Plus</li>
</ul>
<h5 id="Forums">Forums</h5>
<ul>
<li>Reddit: <a href="http://reddit.com/r/firefox">http://reddit.com/r/firefox</a> — active Firefox community</li>
<li>Discourse: <a href="/en-US/docs/">https://discourse.mozilla-community.org/c/quality-assurance</a></li>
</ul>
<h5 id="Meeting_Pages">Meeting Pages</h5>
<ul>
<li>Mozilla Project Weekly Update, <a href="https://wiki.mozilla.org/WeeklyUpdates">meeting details here</a></li>
<li>QA Team: public QA meeting, <a href="https://wiki.mozilla.org/QA/Team_Meeting">meeting details here</a></li>
</ul>
<h5 id="Other_Websites">Other Websites</h5>
<ul>
<li><a href="http://forum.xda-developers.com/">XDA Forums</a></li>
<li><a href="http://www.softwaretestingclub.com/">Software Testing Club</a></li>
</ul>
<hr>
<h2 id="Moderators">Moderators</h2>
<p>The following are some tips for moderators to make the testday a success.</p>
<ul>
<li>Greet people as soon as they join the channel</li>
<li>Ask them to sign up for Mozillians.org</li>
<li>Ask them to download the test build</li>
<li>Ask them about their interest and give them a specific task to perform</li>
<li>Offer to answer questions</li>
<li>Touch base with your testers if you haven't heard from them in the last 20 minutes or so</li>
<li>Thank and encourage your testers when they are completing tasks</li>
<li>Thank and encourage your testers before when they indicate they are leaving</li>
<li>Tell people in other channels about your testday (#qa, #firefox, etc)</li>
</ul>
<h2 id="Contributors">Contributors</h2>
<p>The following are some tips for contributors to make the testday a success.</p>
<ul>
<li>Ask questions, any and all questions you have are valid</li>
<li>Don't be afraid to stumble, hopefully you will learn something new</li>
<li>Read over the testplan and provided documentation</li>
<li>Get a build and start testing; just dive right in</li>
<li>Offer to help other testers and answer questions once you've learned the ropes</li>
<li>Sign up for <a href="https://mozillians.org">Mozillians.org</a> so we can keep in touch</li>
<li><strong>Missed the testday?</strong> Reach out to the organizer and see how you can help out after the fact</li>
</ul>
<div class="originaldocinfo">
<h2 id="Original_document_information">Original document information</h2>
<ul>
<li>Author(s): Anthony Hughes</li>
<li>Date last modified: February 3, 2012 at 10:54 pm PST</li>
</ul>
</div>
<hr>
<h3 id="QMO_Event_Page"><a name="event"></a>QMO Event Page</h3>
<p>The week before a testday we need to create a QMO event page.</p>
<ul>
<li>Once you are logged in (yes you need to be authenticated) simply click on the left to add a <a href="https://quality.mozilla.org/wp-admin/post-new.php">new post</a></li>
<li>Your title should indicate the topic and date (ie. Firefox Aurora Bugday May 6th)</li>
<li>Start out by giving a small summary of the topic, goals, and when the event takes place.</li>
<li>Give some context as to why this event/activity is necessary and valuable.</li>
<li>Give some encouragement for people who have absolutely no experience to attend.</li>
<li>Frame the language of your post with "making Firefox better", show them what benefit their contributions provide (no matter how big or small).</li>
<li>Provide a link to your testplan etherpad and a mibbit URL so people without IRC clients can join easily.</li>
<li>Be sure to thank them in advance for attending.</li>
</ul>
<p>This is an example of an excellent <a href="http://quality.mozilla.org/events/2011/02/28/add-ons-compatibility-and-add-ons-manager-testday-march-4th/">QMO Event</a> page. <strong>Before posting make sure you:</strong></p>
<ul>
<li>"Is this post an event?" is set to "Yes" below</li>
<li>"All day event?" is unchecked and the date/times are properly set (all times in PDT)</li>
<li>All other event details can be left blank</li>
<li>On the right under "Categories", check "Events", "QMO News" and any appropriate "Teams"</li>
<li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong> (if you have to, get someone else to review)</li>
</ul>
<h3 id="QMO_Blog_Post"><a name="blog"></a>QMO Blog Post</h3>
<p>The day before the testday, simply create a post which reminds people that a testday is happening <em>tomorrow</em>.</p>
<ul>
<li>The title should be similar to "REMINDER: Firefox Aurora Testday Tomorrow!"</li>
<li>The message should summarize the activity, time, a mibbit URL to the channel, and a link to the QMO Event page for more information</li>
<li>Be sure to thank them ahead of time for attending</li>
<li>Be sure the "Categories" on the right are set to "QMO News"</li>
<li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong></li>
</ul>
<p>This is a good example of a <a href="http://quality.mozilla.org/qmo-news/2011/03/24/testday-reminder-mozmill-crowd-and-endurance-testing/">QMO Event Reminder</a>. Your post should be syndicated to Planet within 30 minutes to an hour.</p>
<h3 id="QMO_Results_Post"><a name="results"></a>QMO Results Post</h3>
<p>The day after a testday, create another post which highlights the results.</p>
<ul>
<li>The title should be similar to "Results of the Firefox Aurora Testday"</li>
<li>The message should summarize the activity and the value it provided</li>
<li>Highlight some of the results (number of bugs filed, number of bugs confirmed/verified, number of testers, etc)</li>
<li>Identify and thank the top tester</li>
<li>Identify and thank some of the people who were runners up for the top-tester</li>
<li>Give general thanks to everyone who helped</li>
<li>Provide a link to the next testday (should it be available) and ask people to come back to help</li>
<li>Be sure the "Categories" on the right are set to "QMO News"<strong> </strong></li>
<li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong></li>
</ul>
<p>This is a good example of a <a href="http://quality.mozilla.org/qmo-news/2011/04/26/results-of-the-aurora-422-testday/">QMO Results Post</a>. Your post should be syndicated to Planet within 30 minutes to an hour. </p>
<div class="originaldocinfo">
<h2 id="Original_document_information_2">Original document information</h2>
<ul>
<li>Author(s): Anthony Hughes</li>
<li>Date last modified: October 25, 2011 at 11:16 am PST</li>
</ul>
</div>
<p> </p>
|
