QA/Community/Test Day/HowTo: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>[[QA/Community/Test Day|&laquo; QA/Community/Test Day]]</small>
== '''How to prepare for Test Day''' ==
== '''How to prepare for Test Day''' ==


== 1. Announcements should be posted to the following areas: ==
== 1. Announcements should be posted to the following areas: ==
 
*(a) Mozilla QA blog
  *(a)   Mozilla QA blog
*(b) MozillaZine Firefox build Forum
  *(b)   MozillaZine Firefox build Forum
*(c) moz.dev.quality newsgroup
  *(c)   moz.dev.quality newsgroup
*(d) Submit a story to MozillaZine (this won't work on short notice)
  *(d)   Submit a story to MozillaZine (this won't work on short notice)


If we are testing *pre-Firefox 2 *release builds, please do not announce the testing as Firefox 2 testing since it confuses the press.  I customarily use Bon Echo, or emphasis that it is a release candidate, beta, etc.
If we are testing *pre-Firefox 2 *release builds, please do not announce the testing as Firefox 2 testing since it confuses the press.  I customarily use Bon Echo, or emphasis that it is a release candidate, beta, etc.


== 2. Morph the page from the last test day ==
Make sure the latest test day pages is updated with the correct builds, dates, any rewards we are giving out to top testers, etc.
*'''NOTE:'''  Please use http://releases.mozilla.org/... for all links pointing to actual "releases", like Firefox/BonEcho 2.0 RC3.  For nightly builds, it is ok to use http://ftp.mozilla.org/...


== 2.  Morph the page from the last test day (this has the most up to date ==
== 3. Change the following sections as appropriate: ==
information about rewards, etc. I think in the last iteration we removed information about AIM, we should restore that in case anyone wants to join on AIM)
*(a) What needs to be tested
 
*(b) Who is moderating
 
*(c) Name of product(s)we are testing
== 3.   Change the following sections as appropriate: ==
*(d) Update links to the builds you want them to test
 
  (a)   What needs to be tested
  (b)   Who is moderating
  (c)   Name of product(s)we are testing
  (d)   Update links to the builds you want them to test




== 4.  Add a link to the Test Day under Hot Events: ==
== 4.  Add a link to the Test Day under Hot Events: ==
http://wiki.mozilla.org/Mozilla_QA_Community#Hot_Events
* [[QA/Community#Hot_Events]]

Latest revision as of 04:21, 15 November 2007

« QA/Community/Test Day

How to prepare for Test Day

1. Announcements should be posted to the following areas:

  • (a) Mozilla QA blog
  • (b) MozillaZine Firefox build Forum
  • (c) moz.dev.quality newsgroup
  • (d) Submit a story to MozillaZine (this won't work on short notice)

If we are testing *pre-Firefox 2 *release builds, please do not announce the testing as Firefox 2 testing since it confuses the press. I customarily use Bon Echo, or emphasis that it is a release candidate, beta, etc.

2. Morph the page from the last test day

Make sure the latest test day pages is updated with the correct builds, dates, any rewards we are giving out to top testers, etc.

3. Change the following sections as appropriate:

  • (a) What needs to be tested
  • (b) Who is moderating
  • (c) Name of product(s)we are testing
  • (d) Update links to the builds you want them to test


4. Add a link to the Test Day under Hot Events:

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Community/Test_Day/HowTo&oldid=74586"