User:Wsm/MilestoneTesting: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: Draft - Thunderbird Milestone Testing __TOC__ Procedure below was used for Thunderbird Alpha 2 testing. =Overview= Release Candidate builds for Alpha, Beta and ... provided by builde...)
 
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Draft - Thunderbird Milestone Testing  
Thunderbird Release Candidate Milestone Testing  
__TOC__
__TOC__


Procedure below was used for Thunderbird Alpha 2 testing. 
=Overview=


=Overview=
Release Candidate builds for Alpha, Beta and ... provided by builders must be tested by volunteers and the QA team according to a rigorous process in order to certify that a release candidate build is worthy for public release.


Release Candidate builds for Alpha, Beta and ... provided by builders must be tested by volunteers and QA according to a rigorous process in order to  certify that the release candidate build is worthy for public release.
We have just a few days to complete testing, so we need all available hands.  Thank you for your interest, and if circumstances allow, your enthusiastic participation. As always, help is available on IRC and in the newsgroups for both new and experience testers.


We have just a few days to complete this important testing, so we need all available handsThank you for your interest, and if circumstances allow, your enthusiastic participation. As always, help is available ...
We have several types of tests (most of which utilize litmus), and you can choose which to run based on your available timeBFT testing and l10n, and Mac platform tests are our greatest need.


Several types of tests are listed below:
* BFT (Basic Functionality Tests) - touches most functional areas. If you do not have time to do BFT tests we hope that you will ...
* BFT (Basic Functionality Tests) is our most extensive test - using litmus testing tool. If you do not have time to do BFT tests we hope that you will ...
* Smoketest - touches a handful of functional areas (a much reduced BFT)
* Smoketest (reduced litmus test set), or
* Spot check - a visual "look see"  
* Spot check - a visual "look see"  
* l10n (localization) - If you normally run or are familiar with a localized version of Thunderbird, we would appreciate you doing your testing using a locale build.
* l10n (localization) - A set of litmus tests just for localized builds. If you can test a localized version of Thunderbird, we would appreciate you doing so.


All of these test types are described below after the BFT description.
If you can't help before the scheduled testing period ends, please stop back and run the tests as soon as you are able.


If you unable to help before the testing period finishes, please visit and run the tests as soon as you are able.  
You are not required to run a full test set to completion. So, if you don't have much time or think you might run out of time that's OK. In fact, we'd rather have you do a short amount of good testing than none at all. Tests done using litmus get recorded as you go through the list, so stop whenever you need ... and return later when (and if) you are able.


=Details=
=Details=
Thank you for enthusiastically volunteering to participate.


'''Important'''
'''Important'''
* Make sure you are using '''only the builds specified in THIS message'''
* Use '''only the builds specified in <u>this message</u>'''. Do not use a nightly build. Do not use a previous alpha or beta.
* Please file a bug whenever you encounter a problem.
* Please file a bug whenever you encounter a problem.
* When using litmus, if a testcase:
* If a litmus testcase:
** Fails - please comment in the test, file a bug, and leave the URL of the testcase in the bug
** Is not run by you (you skipped it) - please do not mark it in any way with a comment, passing or failed.
** is unclear - please comment with steps that would make it more clear
** Fails - please comment in the test, file a bug, and include URL of testcase in bug
** is not run, i.e. you skipped it - please do not mark it in any way with a comment, nor mark it passing or failed.
** Is unclear - please comment with steps and wording that you think would make it more clear
 
* [[QA/Thunderbird3/TestResults/Alpha3]] documents the release details. You want to check sections 1.1 to 1.6, '''especially the release notes.''' Contact methods are also listed.  
http://wiki.mozilla.org/QA/Thunderbird3/TestResults/Alpha2 documents the full QA process. Please take note of the release notes section. Testers will want to check sections 1.1 to 1.6. Contact methods are listed. If they don't work and you need help please email me.


==Builds==
==Builds==


Builds to be tested (do not use nightly) - <update for 3.0a3> http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/3.0a2-candidates/build1/ - pick localized version if possible.
Builds are listed in the [[QA/Thunderbird3/TestResults/Alpha3|release details]]. Use a localized version if possible. Please do not use old alphas, betas or a nightly.


==BFT - Basic Functionality Tests==
==BFT==


A BFT is a list of tests organized into subgroups. Unless you have 4-6 hours to test, to shorten your testing time you will want to focus by subgroups as follows:
Basic Functionality Tests is organized into subgroups listed below. It is a large list, but to shorten your testing time (running the full set takes 4-6 hours) you can focus by subgroups as follows:


* '''*''' indicates priority items - scan the list and if you have the resource required please do these before do other groups
* <font color=red>'''*''' indicates priority items</font> - if you have the resource required please do '''*''' groups before others
* '''ALL''' indicates items we hope everyone will test
* '''All''' indicates items we hope everyone will test
* '''AL''' and '''MZ''' - please run that test group if your last name is within the range A-to-L or M-to-Z
* '''AL''' and '''MZ''' - indicates please run that group if your last name/surname is in the range A-to-L or M-to-Z


If you start running out of time, or you get done with the assigned subgroups, please choose subgroups that show the least amount of testing coverage as shown on the "Select Subgroup" list.
If you start running out of time, or you get done with the assigned subgroups, please do more subgroups, especially those that show the least amount of testing coverage as shown on the "Select Subgroup" list.


Getting started:
Getting started:
# You've already read the [[QA/Thunderbird3/TestResults/Alpha3#Release_Notes|release notes]], of course.
# login to litmus.mozilla.org (create an account if you don't have one)
# login to litmus.mozilla.org (create an account if you don't have one)
# visit https://litmus.mozilla.org/run_tests.cgi?test_run_id=29
# visit https://litmus.mozilla.org/run_tests.cgi?test_run_id=34
# complete all the information about your setup - paste buildid, set platform, OS, and locale
# complete all the information about your setup - paste buildid, set platform, OS, and locale (note: there is only one linux OS selection)
# click "submit configuration"
# click "submit configuration"
# And you're off and running the tests!
# You're off and running the tests! Please try '''*''' items first. Figure 2.5-3.5 hours to do half the list (as assigned)
# Please attempt '''*''' items first


'''Subgroup assignments for BFTs'''
'''Subgroup assignments for BFTs'''
-----------------------------
&nbsp;
   ALL-Install, shutdown, uninstall
   All-Install, shutdown, uninstall
     MZ-Migration (from other mail systems)
     MZ-Migration (from other mail systems)
     MZ-Import (from other mail systems)
     MZ-Import (from other mail systems)
     MZ-Window configuration
     MZ-Window configuration
   ALL-Toolbars and menus
   All-Toolbars and menus
   ALL-Account settings & Preferences (Options)
   All-Account settings & Preferences (Options)
     *  IMAP accounts
     <font color="red">*  IMAP accounts</font>
     *  POP accounts (exclude Global Inbox)
     <font color="red">*  POP accounts (exclude Global Inbox)</font>
     *  Global inbox
     <font color="red">*  Global inbox</font>
   ALL-Mail composition
   All-Mail composition
     MZ-Spell checker
     MZ-Spell checker
     MZ-RSS account & subscriptions
     MZ-RSS account & subscriptions
     MZ-Newsgroups
     MZ-Newsgroups
   ALL-Navigating and displaying messages
   All-Navigating and displaying messages
     AL-Downloading and saving
     AL-Downloading and saving
     AL-Image blocking
     AL-Image blocking
     AL-Return receipts
     AL-Return receipts
     *  Proxies
     <font color="red">*  Proxies</font>
     MZ-Offline, disk space
     MZ-Offline, disk space
   ALL-Moving, copying, deleting messages
   All-Moving, copying, deleting messages
   ALL-Views and labeling messages
   All-Views and labeling messages
     MZ-Message filters
     MZ-Message filters
     MZ-Message search
     MZ-Message search
Line 84: Line 80:
     AL-Saved Search folders
     AL-Saved Search folders
     AL-Message Grouping
     AL-Message Grouping
   ALL-Message Aging
   All-Message Aging
   ALL-Quicksearch
   All-Quicksearch
     MZ-Address books
     MZ-Address books
     MZ-Junk mail
     MZ-Junk mail
Line 93: Line 89:
     AL-Printing
     AL-Printing
     AL-Master Passwords & password management
     AL-Master Passwords & password management
     *  Phishing, spoof detection
     <font color="red">*  Phishing, spoof detection</font>
     *  Secure connections
     <font color="red">*  Secure connections</font>
     *  Digital signing, encrypting messages
     <font color="red">*  Digital signing, encrypting messages</font>
     MZ-Software Update
     AL-Software Update


==smoketest==
==smoketest==
Access litmus using the procedure above for BFT, but use the smoketest URL: https://litmus.mozilla.org/run_tests.cgi?test_run_id=28
Access litmus using the procedure above for BFT, but use the smoketest URL: https://litmus.mozilla.org/run_tests.cgi?test_run_id=33.  Should take about 1.5 hours. (Ignore "Subgroup assignments" listed above - it is not relevant)
 
==Spot check==
Spot check takes the least time because is just a casual visual inspection and does not require the use of litmus. Install, poke around, inspect, test and try what you can, then visit http://wiki.mozilla.org/QA/Thunderbird3/TestResults/Alpha3#Thunderbird_Spot_Check and update the wiki.


==locale==
==locale==
Verify build is usable and update the wiki at http://wiki.mozilla.org/Thunderbird3/TestResults/Alpha2/L10N


In addition to running locale specific tests, if possible please run BFT or smoketest using the locale.
You can do any of the tests as described above in your native language build. Then please update the wiki at [[Thunderbird3/TestResults/Alpha3/L10N]]. This will help us keep track of what locales have been tested.


==Spot checks==
In addition to (or instead of) the above, you can run the [https://litmus.mozilla.org/run_tests.cgi?test_run_id=32 l10n trunk baseline tests] that focus on checking that localized language strings are correct. The results are recorded in litmus.
Spot checks take the least amount of time because they are are casual visual inspection and do not require the use of litmus.  Visit http://wiki.mozilla.org/QA/Thunderbird3/TestResults/Alpha2#Thunderbird_Spot_Check and update the wiki

Latest revision as of 01:58, 5 October 2008

Thunderbird Release Candidate Milestone Testing

Overview

Release Candidate builds for Alpha, Beta and ... provided by builders must be tested by volunteers and the QA team according to a rigorous process in order to certify that a release candidate build is worthy for public release.

We have just a few days to complete testing, so we need all available hands. Thank you for your interest, and if circumstances allow, your enthusiastic participation. As always, help is available on IRC and in the newsgroups for both new and experience testers.

We have several types of tests (most of which utilize litmus), and you can choose which to run based on your available time. BFT testing and l10n, and Mac platform tests are our greatest need.

  • BFT (Basic Functionality Tests) - touches most functional areas. If you do not have time to do BFT tests we hope that you will ...
  • Smoketest - touches a handful of functional areas (a much reduced BFT)
  • Spot check - a visual "look see"
  • l10n (localization) - A set of litmus tests just for localized builds. If you can test a localized version of Thunderbird, we would appreciate you doing so.

If you can't help before the scheduled testing period ends, please stop back and run the tests as soon as you are able.

You are not required to run a full test set to completion. So, if you don't have much time or think you might run out of time that's OK. In fact, we'd rather have you do a short amount of good testing than none at all. Tests done using litmus get recorded as you go through the list, so stop whenever you need ... and return later when (and if) you are able.

Details

Important

  • Use only the builds specified in this message. Do not use a nightly build. Do not use a previous alpha or beta.
  • Please file a bug whenever you encounter a problem.
  • If a litmus testcase:
    • Is not run by you (you skipped it) - please do not mark it in any way with a comment, passing or failed.
    • Fails - please comment in the test, file a bug, and include URL of testcase in bug
    • Is unclear - please comment with steps and wording that you think would make it more clear
  • QA/Thunderbird3/TestResults/Alpha3 documents the release details. You want to check sections 1.1 to 1.6, especially the release notes. Contact methods are also listed.

Builds

Builds are listed in the release details. Use a localized version if possible. Please do not use old alphas, betas or a nightly.

BFT

Basic Functionality Tests is organized into subgroups listed below. It is a large list, but to shorten your testing time (running the full set takes 4-6 hours) you can focus by subgroups as follows:

  • * indicates priority items - if you have the resource required please do * groups before others
  • All indicates items we hope everyone will test
  • AL and MZ - indicates please run that group if your last name/surname is in the range A-to-L or M-to-Z

If you start running out of time, or you get done with the assigned subgroups, please do more subgroups, especially those that show the least amount of testing coverage as shown on the "Select Subgroup" list.

Getting started:

  1. You've already read the release notes, of course.
  2. login to litmus.mozilla.org (create an account if you don't have one)
  3. visit https://litmus.mozilla.org/run_tests.cgi?test_run_id=34
  4. complete all the information about your setup - paste buildid, set platform, OS, and locale (note: there is only one linux OS selection)
  5. click "submit configuration"
  6. You're off and running the tests! Please try * items first. Figure 2.5-3.5 hours to do half the list (as assigned)
Subgroup assignments for BFTs
 
  All-Install, shutdown, uninstall
   MZ-Migration (from other mail systems)
   MZ-Import (from other mail systems)
   MZ-Window configuration
  All-Toolbars and menus
  All-Account settings & Preferences (Options)
   *  IMAP accounts
   *  POP accounts (exclude Global Inbox)
   *  Global inbox
  All-Mail composition
   MZ-Spell checker
   MZ-RSS account & subscriptions
   MZ-Newsgroups
  All-Navigating and displaying messages
   AL-Downloading and saving
   AL-Image blocking
   AL-Return receipts
   *  Proxies
   MZ-Offline, disk space
  All-Moving, copying, deleting messages
  All-Views and labeling messages
   MZ-Message filters
   MZ-Message search
   AL-Address search
   AL-Saved Search folders
   AL-Message Grouping
  All-Message Aging
  All-Quicksearch
   MZ-Address books
   MZ-Junk mail
   MZ-Extensions
   AL-Theme management
   AL-Help
   AL-Printing
   AL-Master Passwords & password management
   *  Phishing, spoof detection
   *  Secure connections
   *  Digital signing, encrypting messages
   AL-Software Update

smoketest

Access litmus using the procedure above for BFT, but use the smoketest URL: https://litmus.mozilla.org/run_tests.cgi?test_run_id=33. Should take about 1.5 hours. (Ignore "Subgroup assignments" listed above - it is not relevant)

Spot check

Spot check takes the least time because is just a casual visual inspection and does not require the use of litmus. Install, poke around, inspect, test and try what you can, then visit http://wiki.mozilla.org/QA/Thunderbird3/TestResults/Alpha3#Thunderbird_Spot_Check and update the wiki.

locale

You can do any of the tests as described above in your native language build. Then please update the wiki at Thunderbird3/TestResults/Alpha3/L10N. This will help us keep track of what locales have been tested.

In addition to (or instead of) the above, you can run the l10n trunk baseline tests that focus on checking that localized language strings are correct. The results are recorded in litmus.