Changes

Jump to: navigation, search

Calendar:QA Home

3,249 bytes added, 22:19, 15 August 2006
no edit summary
==How to Get Involved==
We There are currently working on formalizing various ways you can get involved in helping the calendar Calendar QA effort. There is much to be doneteam, if you want to help make even with no previous experience!=== Filing Bugs ===Use Sunbird and /or Lightning the best calendaring applications out there, you've come to the right place. We have a weekly calendar QA chat where you can connect with the other people doing calendar QA Find bugs.*[ Write [Calendarhttp:QA_Chats]]*[[Calendar:QA_TestCase_Writing_Day]]*[[Calendar:QA_TestDays]//www.mozilla.org/quality/bug-writing-guidelines.html good bug reports].
==How to Report a Problem==
We test the [http://www.mozilla.org/projects/calendar/sunbird/ Sunbird] and [http://www.mozilla.org/projects/calendar/lightning/ Lightning] calendar projects. Sunbird and Lightning share much of the same code, and it is necessary to understand the high-level [[Calendar:Bugzilla_Component_Architecture | component architecture]] in order accurately report problems.
# Download a nightly build ([http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/ for Sunbird]) ([http://www.mozilla.org/projects/calendar/lightning/download.html for Lightning]) and check to see that the bug has not already been fixed.
# Get a [https://bugzilla.mozilla.org/createaccount.cgi Bugzilla Account] if you don't already have one – it–�it's simple and it's free
# Next, go to the [https://bugzilla.mozilla.org/enter_bug.cgi New Bug] page on Bugzilla, and it can walk you through the rest.
# [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html BE SURE TO SEARCH FOR EXISTING DEFECTS.]
# Remember === The 'qawanted' keyword ===Calendar developers will place the 'qawanted' keyword on bugs where they need help from a QA person. Generally, the bug should include a comment about what is needed from QA. If it doesn't and you're unsure what needs to be done, please add a comment saying so. [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=anywords&status_whiteboard=&keywords_type=anywords&keywords=qawanted&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=Reuse+same+sort+as specific +last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= List of current 'qawanted' bugs] === Blocking Nominations ===If I bug you've filed (or even just seen) seems to qualify as possible about a bug that should block the next release of Sunbird and/or Lightning, set the blocking0.3 flag to ?. For more information see [[Calendar:For_Everyone:Blocking_Flags]] === Verifying bugs ===Bugs get resolved all the behavior time. When this happens, it's helpful for QA to come along and ensure that you are seeingthe resolution was correct. For instance, if a patch was checked in, the bug will be marked FIXED. QA can then test the next nightly build to see if the bug has indeed been fixed. The  [https://bugzilla.mozilla.org/pagebuglist.cgi?idquery_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Calendar&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=-7d&chfieldto=Now&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Recently resolved bugs] === Confirming Unconfirmed Bugs ===Many bugs are reported to Bugzilla in the Unconfirmed state. These bugs need QA folks to examine them and help determine (1) whether a bug-writingreally exists (2) what information a developer will need to fix the bug (3) where the bug should best be filed. See also [http://www.mozilla.org/quality/help/unconfirmed.html Bugzilla Bug Writing Guidelinesthe Mozilla guidelines for triaging] and . [https://bugzilla.mozilla.org/pagebuglist.cgi?idquery_format=etiquetteadvanced&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&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=---&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=Reuse+same+sort+as+last+time&query_based_on=Unconfirmed&field0-0-0=noop&type0-0-0=noop&value0-0-0= List of Unconfirmed bugs] === Testdays and other events === We are currently working on formalizing the calendar QA effort. There is much to be done, if you want to help make Sunbird and Lightning the best calendaring applications out there, you've come to the right place.html Bugzilla Etiquette] We have a weekly calendar QA chat where you can guide you through thisconnect with the other people doing calendar QA.*[[Calendar:QA_Chats]]*[[Calendar:QA_TestCase_Writing_Day]]*[[Calendar:QA_TestDays]]
==Test Cases==
289
edits

Navigation menu