Mozilla QA Community:ThunderBird 1.5 RC2 Community Test Day: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 23: Line 23:


=== Ok, I am in the channel, now what? ===
=== Ok, I am in the channel, now what? ===
# Ask for an area to test.  One of the [http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1.5_RC3_Community_Test_Day#Who_will_be_moderating_the_.23testday_channel.3F moderators] will help guide you to a useful area to test.  If you have a specific area you want to test you can do it through one of our test procedures with automatic logging pass/fail and comments.  Or you can test on your own.  Just work with one of the Moderators.
# Let the moderators know if you have any questions or encounter any problems.  If you are not familiar with our [https://bugzilla.mozilla.org/index.cgi bugzilla bug tracking system], feel free to report your problems to a moderator and they can log any bugs for you.
# Let the moderators know if you have any questions or encounter any problems.  If you are not familiar with our [https://bugzilla.mozilla.org/index.cgi bugzilla bug tracking system], feel free to report your problems to a moderator and they can log any bugs for you.
# Let the moderator know when you are done so we can release any test ids and wrap up any questions you or the moderator may have about your testing.


=== What build should I test? ===
=== What build should I test? ===

Revision as of 22:57, 12 December 2005

Welcome to the Thunderbird 1.5RC2 Community Test Day!

NOTE: This page is being edited during the course of the day today (Monday), so please check back later when I have all the information added. Thanks for your patience.

The test day will be held on December 13th, 2005. It will run from 6am PST/9am EST until 5pm PST/8pm EST

Welcome to the Firefox 1.5 RC3 Community Test Day!!

Thank you for participating in this test day. The success of Firefox is heavily dependent on community members like you. We appreciate your support!!

When you are done, please send feedback to [1]. We are very interested to hear about how the test day went, any overall thoughts about Firefox 1.5 RC3, and roll up of issues found and bugs filed.

FAQ

Where do I start?

Ok, I am in the channel, now what?

  1. Let the moderators know if you have any questions or encounter any problems. If you are not familiar with our bugzilla bug tracking system, feel free to report your problems to a moderator and they can log any bugs for you.

What build should I test?

We will be testing the Thunderbird RC2 build. Here are links to the various platforms:

Windows Mac Linux

If you are using an earlier build (RC1), feel free to test out our great software update feature to bring yourself up to RC2.

How do I use Litmus to test?

  • Go to http://litmus.mozilla.org/
  • Click on run tests. Please make sure to enter your email address in the last field.
  • Select product "Thunderbird" and your platform and OS
  • Select trunk
  • Enter 2005120115 as the build ID
  • Enter your email address

In the next section, select the following:

  • Select the radio button that says BFTs
  • Select the radio button for the section you want to test

Who will be moderating the #testday channel?

Moderators are designated by a solid green dot in the IRC client and will be at the top of the channel.

The moderator's nicks are:

  • tracy
  • coop
  • bc
  • timr
  • marcia
  • jay
  • davel

How do I file bugs?

First of all, let one of the moderators know so they can check if it is already a known problem. Then they can guide you to either provide more details, update an existing bug or file a new bug. If filing a new bug, please do a quick check to see if the bug already exists. This can easily be done by searching for the error message, window name, or some over identifing feature of the bug.

How do I send feedback?

Please use the [2] to send feedback about how the testday went, any overall thoughts about Thunderbird 1.5 RC2, and roll up of issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.