Welcome to the Firefox and Thunderbird Test Case Writing Community Test Day!!

Thank you for participating in this test day. The success of Firefox and Thunderbird 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 our Test Case Writing Day. We are also looking for ways to get more people involved, so any ideas or suggestions on how to make future events more interesting and fun are welcome too! :-)

The official time for the test day is Friday, January 12, 2007, from 7am - 5pm PST, but anyone can work on writing test cases at any time on any day!

FAQ

Where do I start?

• Go to your favorite IRC client:
  • Windows clients
  • MacOS clients
  • Linux clients
  • Firefox client
• Connect to irc.mozilla.org -- In most clients, this is done by typing /server irc.mozilla.org and hitting Enter.
• Join the #testday channel -- In most clients, typing /join #testday will get you into the channel.

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.

Where can I find some test case writing guidelines?

Test Case Writing Guidelines

Please feel free to write test cases about Firefox and Thunderbird.

Where can I get ideas about writing new test cases?

• A Litmus query for reported Unclear test cases. Please review these and submit small fixes to the #testday irc channel, if it hasn't already been fixed. Someone (one of the moderators) with editing rights will help make the changes to the test case. Lengthy test case rewrites should be submitted to the testday@mozilla.com alias. A note to moderators: please add a comment when you fix a test case.

• Bugzilla query for regressions in FF and Tbird Please review these to get ideas about which bugs might make candidates for a test case. If the reporter has included a good set of steps to reproduce in the bug, that would be a good first start in crafting a test case. Another good strategy is to look at this set of bugs by priority.

There may be cases where someone has filed a regression bug where there is a specific layout issue, or where a particular site is not working properly. These may not be the best candidates for test cases. It would be better to focus on issues where there is a specific regression in functionality that could benefit from a new test case.

Where do I find Litmus?

• Go to Litmus
• log in and then select run tests
• Talk to a moderator if you need help.
• Please make sure to choose the correct platform when you start your run.

Who will be moderating the #testday channel?

The moderator's nicks are:

• tracy
• bc
• timr
• marcia
• jay
• juanb
• robcee
• alice
• coop
• tchung

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 the Test Case writing day, and roll up of issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.

Results

Testcases added: 0 Testcases updated: 4