QA/Test Days/Conclusion Checklist

From MozillaWiki
< QA‎ | Test Days
Jump to navigation Jump to search

The following is a list of things to be done once an event is over.

Immediately

1. Comment in IRC thanking everyone for helping out.

2. Set the IRC channel topic to a thank you message and a link to the next event (if available). For example, "Thank you for helping us test the Firefox Add-ons Manager. See you next Friday for the Firefox 4.0b11 Testday! <bit.ly link>"

Day After

1. Create a blog post on QMO showcasing the results of the event. See below for tips on creating that blog post.

2. Tweet a link to the results blog post using the MozillaQA twitter account.

3. Reply to your mailing list thread thanking everyone for their help and linking to the blog post. Be sure to remind everyone of the next event.

4. Once the meeting notes wiki page has been published for Monday's All-hands Meeting, add a note nominating your top tester as a Friend of the Tree.

5. Add a link to the Testdays page to your event wiki page. Put your event on top of the list (ie. the list should be in reverse chronological order).

Results Blog Post

This is being moved to a template page

The following is a list of tips for composing your results blog post.

  • The title of your blog post should be something like "Results of the <event name>".
  • You should open with a brief summary of what the event was for.
  • Briefly explain whether the event was a success and why or why not
  • Summarize the results of the event using the raw data from the results section of your wiki page
  • Create a line chart using the Google Chart Wizard which visualize the raw data from the results. Simply copy and paste the <img> URL into the HTML view of your blog post.
  • Finish with a general thank you to those who helped and a special thank you to any people who stand out (especially your top tester)
  • Be sure to invite people to attend the next event
  • Set the category to QMO News, Syndicated, and apply the "mozilla, qa" tag

NOTE: You should save draft and preview before publishing your content. It should appear on Planet after 30 minutes and Facebook the next day.

You can find an example of a good results blog post here.