Mozilla QA Community:1.5.0.8 Community Test Day: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Welcome to the Firefox/Thunderbird 1.5.0.8 Community Test Day!! =
= Welcome to the Firefox 2.0.0.1/Firefox/Thunderbird 1.5.0.9/Thunderbird 2 Beta 1 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!!
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 [mailto:testday@mozilla.org].  We are very interested to hear about how the test day went, any overall thoughts about Firefox and Thunderbird 1.5.0.8, and roll up of issues found and bugs filed.  '''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! :-)'''
When you are done, please send feedback to [mailto:testday@mozilla.org].  We are very interested to hear about how the test day went, any overall thoughts about Firefox 2.0.0.1 and FIrefox/Thunderbird 1.5.0.9, and roll up of issues found and bugs filed.  '''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, November 3, 2006, from 7am - 5pm PDT''', but anyone can jump on Litmus at any time on any day!
The official time for the test day is '''Friday, December 8, 2006, from 7am - 5pm PST''', but anyone can jump on Litmus at any time on any day!


'''For more information about this release, please check out the [[Firefox:1.5.0.8:Community | Firefox/Thunderbird 1.5.0.8 Community Wiki]].  You will find the current schedule, test plan, and specific areas you can help us test.'''
'''For more information about this release, please check out the [[http://wiki.mozilla.org/Firefox:Home_Page#Firefox_1.5.0.9_-_2.0.0.1 Firefox 1.5.0.9/2.0.0.1 Testing Page]].  You will find the current schedule, test plan, and specific areas you can help us test.'''


== FAQ ==  
== FAQ ==  
Line 25: Line 25:


=== What build should I test? ===
=== What build should I test? ===
We will be testing the latest Firefox and Thunderbird 1.5.0.8 candidate builds:
We will be testing the following:


'''Firefox:''' http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/1.5.0.8-candidates/rc2/
'''Latest Firefox 2.0.0.1 candidate builds:''' ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0.0.1-candidates


'''Thunderbird:''' http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/1.5.0.8-candidates/rc1/
'''Latest Firefox and Thunderbird 1.5.0.9 candidate builds:
'''
'''Firefox:'''  TBA
 
'''Thunderbird:''' TBA
 
'''Thunderbird 2 Beta 1 builds:''' ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2.0b1-candidates/
If you find issues with Tbird


=== <font color=darkred>'''What needs to be tested?'''</font> ===
=== <font color=darkred>'''What needs to be tested?'''</font> ===
'''The easiest thing to do...'''
'''The easiest thing to do...'''


Try running through any number of Basic Funcational Tests (BFTs) that are available through [http://litmus.mozilla.org/ Litmus], our test tracking system.'''
Try running a smoketest on any of the builds, or the Fun Smoketest (Surf's Up!)
 
Try running through any number of Basic Functional Tests (BFTs) that are available through [http://litmus.mozilla.org/ Litmus], our test tracking system.'''


'''For those that want to do a bit more exploring...'''
'''For those that want to do a bit more exploring...'''


You can do some exploratory testing around our [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=anywords&keywords=fixed1.8.0.8+verified1.8.0.8&order=Bug+Number Fixed Bugs].  There are plenty of them, so pick a few and then try:
You can do some exploratory testing around some of the new features or bug fixes.  There are plenty of them, so pick a few and then try:
* Reading through the bug comments to get a better understanding of the problem
* Reading through the bug comments to get a better understanding of the problem
* Try any testcases in the bug to see if they work for you or create your own simplified testcase or steps to reproduce.
* Try any testcases in the bug to see if they work for you or create your own simplified testcase or steps to reproduce.
* Find features, components, areas, etc to test that might be effected by the fix and verify that everything works as expected.
* Find features, components, areas, etc to test that might be effected by the fix and verify that everything works as expected.
* If you want, you can leave a comment in the bug, or just include your results in the notes you send to us.
* If you want, you can leave a comment in the bug, or just include your results in the notes you send to us.
We have made changes or fixed bugs/regressions in parts of the code that deal with the following areas, so you should try to test around them to make sure everything still works as expected:
* SSL certificates and websites (try going to "secure" websites to make sure everything works as expected.  One site that can point you to a few more is https://www.verisign.com/, just check the customers link).
** Financial sites
*** any banking site - try testing any online bank site that you use, ensure that it works correctly
*** any shopping site - go to your favorite online shopping site and log in to your account.  Try adding things to your online cart, checking out, etc.
** This may also effect secure gmail accounts.  Try using https://gmail.google.com and see if it works correctly
** Any other online mail accounts (yahoo, etc)
* Websites with fancy table layouts or other unique structure.  Do a Google search for layout testing and you might be able to find some test suites to run to make sure Firefox renders pages properly.  You can also compare websites in Firefox to what they look like in IE, Opera, or Safari (99% of the time they should all look pretty much the same).
** Specific sites of interest.  If you have accounts on any of these sites please use them to ensure that they layout/functionality is correct
*** http://www.myspace.com
*** http://www.flickr.com
*** http://del.icio.us/
*** any ajax-style site
* We have made a change to how Java is run on the Mac.  If you are using a Mac browse any sites with Java or Java applets.  Ensure that they load and work correctly
* There have been a couple of tweaks that may effect eBay.  If you have an eBay account login, place bids, check-out or do any other day-to-day activities
* Browse your favorite sites and make sure your experience is the same as with 1.5.0.7.
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=anywords&keywords=fixed1.8.0.8+verified1.8.0.8&order=Bug+Number Fixed Bugs] list and pick a few bugs to explore and test around.


If you decide to test on your own, please try to make note of any bugs you have looked at, any testcases you have run, and any other info about your testing. When you're done, please email us at [mailto:testday@mozilla.org] with your results.
If you decide to test on your own, please try to make note of any bugs you have looked at, any testcases you have run, and any other info about your testing. When you're done, please email us at [mailto:testday@mozilla.org] with your results.
Line 82: Line 72:
* marcia
* marcia
* jay
* jay
* davel
* juanb
* juanb
* robcee
* robcee
* alice
* alice
* coop
* coop
* ispiked
* tchung


=== How do I file bugs? ===
=== How do I file bugs? ===
Line 97: Line 86:
== Results ==
== Results ==


=== Total Test Results By Locale ===
Once the testday is complete, results will be available here:
 
=== Total Test Results By Platform ===
 
=== Total Test Results By Result Status ===
 
=== Total Test Results By Subgroup ===
 
=== Top Testers ===


=== Result Status Breakdown By Tester ===
http://litmus.mozilla.org/testday_report.cgi?testday_id=21

Latest revision as of 23:08, 5 December 2006

Welcome to the Firefox 2.0.0.1/Firefox/Thunderbird 1.5.0.9/Thunderbird 2 Beta 1 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 Firefox 2.0.0.1 and FIrefox/Thunderbird 1.5.0.9, and roll up of issues found and bugs filed. 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, December 8, 2006, from 7am - 5pm PST, but anyone can jump on Litmus at any time on any day!

For more information about this release, please check out the [Firefox 1.5.0.9/2.0.0.1 Testing Page]. You will find the current schedule, test plan, and specific areas you can help us test.

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 following:

Latest Firefox 2.0.0.1 candidate builds: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0.0.1-candidates

Latest Firefox and Thunderbird 1.5.0.9 candidate builds: Firefox: TBA

Thunderbird: TBA

Thunderbird 2 Beta 1 builds: ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2.0b1-candidates/ If you find issues with Tbird

What needs to be tested?

The easiest thing to do...

Try running a smoketest on any of the builds, or the Fun Smoketest (Surf's Up!)

Try running through any number of Basic Functional Tests (BFTs) that are available through Litmus, our test tracking system.

For those that want to do a bit more exploring...

You can do some exploratory testing around some of the new features or bug fixes. There are plenty of them, so pick a few and then try:

  • Reading through the bug comments to get a better understanding of the problem
  • Try any testcases in the bug to see if they work for you or create your own simplified testcase or steps to reproduce.
  • Find features, components, areas, etc to test that might be effected by the fix and verify that everything works as expected.
  • If you want, you can leave a comment in the bug, or just include your results in the notes you send to us.

If you decide to test on your own, please try to make note of any bugs you have looked at, any testcases you have run, and any other info about your testing. When you're done, please email us at [2] with your results.

If you discover a bug or regression that you feel is critical, please let us know on the #testday IRC channel ASAP!

Where do I find Litmus?

  • Go to Litmus
  • log in and then select run tests
  • You can do a smoketest or a Basic Functional Test, it is entirely up to you!
  • 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 [3] to send feedback about how the testday went, any overall thoughts about Firefox or Thunderbird 1.5.0.8, and roll up of issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.

Results

Once the testday is complete, results will be available here:

http://litmus.mozilla.org/testday_report.cgi?testday_id=21