Changes

Jump to: navigation, search

Calendar:QA TestDay:2007-01-30

10,719 bytes added, 23:15, 23 January 2007
no edit summary
<small>[[Calendar:QA_TestDays|<< Back to Calendar QA TestDays]]</small>

== When is the test day? ==
* '''TWO''' test days this week.
* <font color=red> PRIMARY </font> test day will be held from 13:00 UTC January 30th to 1:00 UTC on January 31st.
* A smaller, secondary day will be held on February 1, times to be announced.
* If there is great demand at the end of the day, we will extend the test day ending time.
*[http://www.timeanddate.com/worldclock/fixedtime.html?month=12&day=5&year=2006&hour=13&min=0&sec=0&p1=0 Find the starting time in your timezone]
*[http://www.timeanddate.com/worldclock/fixedtime.html?month=12&day=6&year=2006&hour=1&min=0&sec=0&p1=0 Find the ending time in your timezone]

== Where do I start? ==
* Open up your [http://www.ircreviews.org/clients/ favorite IRC client]:
** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
** [http://www.ircreviews.org/clients/platforms-macos.html MacOS clients]
** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]
** [https://addons.mozilla.org/firefox/16/ ChatZilla (Firefox extension)]
* Connect to [irc://irc.mozilla.org irc.mozilla.org]
* Join the #calendar-qa channel

== OK, I am in the channel, now what? ==

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.

== Who will be moderating the #calendar-qa channel on the Test Days? ==
The moderator's nicks for this test day will be:
* ctalbert
* ssitter
* lilmatt
* dmose
* xFallenAngel
* mschroeder
* jminta

== What build should I test? ==

Due to the upcoming [http://groups.google.de/group/mozilla.dev.apps.calendar/msg/438d63147bfb3809 calendar maintenance release (0.3.1)] our normal nightly locations have changed.

If you will be doing maintenance release testing you need a 0.3.1 build. If you are doing current testing for 0.5, then you must have a 0.5 build. Note that there are not any current nightly builds for 0.5 lightning on Thunderbird 1.5 and 2.0.

=== For Next Release 0.5 Testing ===
'''Sunbird 0.5:''' : http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-mozilla1.8/

'''Lightning 0.5''' (for '''Thunderbird 3.0 only''') : http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-trunk/
* Note: For the Sun dialogs load the '''lightning-wcap.xpi''' from the subfolder for your Operating System in the directory above.

=== For 0.3.1 Maintenance Release Testing ===
'''Sunbird 0.3.1''' : http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/

'''Lightning 0.3.1''' (for Thunderbird 1.5.x and 2.0 candidates):
http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/
* Note: For the Sun dialogs load the '''lightning-wcap.xpi''' from the subfolder for your Operating System in the directory above.

== What specifically will we be testing? ==

<font color=red> This is still in discussion, please check back soon. </font>

<font color=red>

== BEFORE YOU START--BACKUP YOUR PROFILE ==

'''Due to a recent SQL Database change you CANNOT test this nightly on any profile that was created prior to Nov. 29. If you attempt this, your database will be automatically upgraded.'''

Therefore, we '''strongly''' recommend you create a new profile data for testing.
</font>

Backing up a profile is easy:<br>
1. Find your profile directory:
{| border="2" cellpadding="2"
! OS !! Thunderbird Profile !! Sunbird Profile
|-
| Windows || %AppData%\Thunderbird || %AppData%\Mozilla\Sunbird
|-
| Linux || ~/.thunderbird || ~/.mozilla/sunbird
|-
| MacOSX || ~/Library/Thunderbird || ~/Library/Application Support/Sunbird
|}
2. Copy the root of it somewhere else, for example copy the Thunderbird or Sunbird directory and everything below it.

Creating a testing profile is also easy:
# Launch your application with a -P option
# Create a New Profile by clicking the Create a New Profile button
# Click Next, Give it a name like "Testing Profile", click Finish
# Select the testing profile and click the "Start Calendar" (Or Start Mail in Thunderbird) button.
'''Remember that you will have to start the application with the -P option during testing so you can pick your Testing profile'''

Once you've finished testing, you can delete the extra profiles and you'll be back to normal.

If something goes terribly wrong (although we don't expect it to), close the application and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.

== Testing Instructions ==
'''To Run Litmus Test Cases'''

Build ID for December 5 Test Day
--------------------------------
OS | Sunbird | Lightning
Linux | TODO | TODO
Mac | TODO | TODO
Windows | TODO | TODO

# Download Sunbird or Lightning from the above URLs
# Create your testing profile (see above)
# Go to [http://litmus.mozilla.org Litmus].
##Select Run Tests, the Product is Calendar. Your buildId should match the one in the table above. Verify that it does. Sunbird's buildId is in the "About Sunbird" window. Lightning's buildId is in its description in the Add-ons Manager.
##Choose a Test group and subgroup to test on. If you are running the lightning-wcap extension, please run the "Prototypes" and "WCAP Calendar" tests prior to other tests.
##Follow the test steps and verify the function under test works as described in Expected Results.
## If the test case performs as expected, mark it as a "Pass". If not, mark it as a "Fail" and then enter a bug (see below).
## When you've finished one test, go to the next test by clicking the test case name.
## Once you've completed all the tests in a group, click the "Submit All Results" button at the bottom.

'''BUG FOUND!'''
# In the process of working with the Bugzilla or Litmus, you may find another bug. When you think you've found a bug, try to reproduce it. Restart Sunbird/Lightning and do the same steps again. The most valuable bugs are those that can be reproduced.
# Once the bug has been reproduced, search for it or something similar on [https://bugzilla.mozilla.org Bugzilla]. This can easily be done by searching for the error message, window name, or some other identifying feature of the bug. If you found an existing bug that is just like the bug you found, read the comments. Maybe your situation is slightly different and your input could help developers find the origin of the bug.
# If you can't find the bug in Bugzilla, talk about it in the channel. Maybe others can confirm your bug or find a similar bug in Bugzilla. This also gives moderators a chance to guide you to either provide more details, update an existing bug or file a new bug.
# If you are certain you found a unique bug and have read the [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Bug Writing Guidelines] and [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette], go ahead and file the bug in Bugzilla. Remember to be as specific as possible.

Some other ways you can help:

* Think of some test cases that aren't already included in Litmus (we love suggestions!).
* Ask your friends to join you. The more people to help the better!
* Consider looking at the [[Calendar:QA_TODO|Calendar ToDo list]], there is much you can help with.

== Where do I find Litmus and Bugzilla? ==

* Litmus can be found at http://litmus.mozilla.org/
* A list of Calendar specific test cases can be found via the [http://litmus.mozilla.org/search_results.cgi?product=Calendar&locale=en-US search function]

* Bugzilla can be found at http://bugzilla.mozilla.org/
* A list of Calendar specific bugs (without enhancements) can be found [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Calendar&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&resolution=---&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0= here]
* A list of already filed enhancement requests can be found [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Calendar&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&resolution=WONTFIX&resolution=---&bug_severity=enhancement&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0= here]

Tips:
* Make sure you enter the correct information for your platform, version of Thunderbird, Lightning etc. Please include the full build identifier (i.e Thunderbird 1.5.0.7 (20060909) with Lightning 0.3 (2006100206)).
* Be sure to read the [[Calendar:QA_TestDays#Testing_Instructions|Testing Instructions]] above before filing a bug.
* Feel free to ask on [[Calendar:QA_TestDays#Where_do_I_start.3F|IRC]] if you need help or have any more questions.

== How do I send feedback? ==
Please use email us at [mailto:dev-apps-calendar@lists.mozilla.org dev-apps-calendar at lists.mozilla.org] to send feedback about how the test day went, any overall thoughts about Sunbird and Lightning, and to follow up on issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.

== Rewards ==
* There will be rewards for the '''PRIMARY''' test day only. Unfortunately, we do not have the resources to reward people at both test days.
* There will be one Mozilla Store gift certificate available for that hard working individual who wins the test day. Additionally, their IRC nickname will take the position of honor in our channel's IRC title.
* <font color=red> More information on rewards is coming soon, please check back. </font>
Confirm
3,816
edits

Navigation menu