Calendar:QA TestDay:2006-12-05: Difference between revisions

Calendar:QA TestDay:2006-12-05 (view source)

Revision as of 15:39, 5 December 2006

5 bytes added , 5 December 2006

m

→‎Testing Instructions

Ssitter

278

edits

@@ Line 89: / Line 89: @@
   OS      | Sunbird    | Lightning
   Linux   | 2006120503 | 2006120503
-  Mac     | TODO | TODO
+  Mac     | 2006120504 | TODO
   Windows | 2006120503 | 2006120503
@@ Line 96: / Line 96: @@
 # 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 extentions, please run the "Prototypes" and "WCAP Calendar" tests prior to other tests.
+##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).
@@ Line 104: / Line 104: @@
 '''To Confirm Unconfirmed Bugs:'''
-We need help confirming bugs in bugzilla. We currently have 252 unconfirmed bugs. Can you help confirm some? If you need privileges, please let a moderator know and we will try to help with that.
+We need help confirming bugs in Bugzilla. We currently have 252 unconfirmed bugs. Can you help confirm some? If you need privileges, please let a moderator know and we will try to help with that.
 #Click on a Bugzilla query below for a component that you would like to work on.
@@ Line 121: / Line 121: @@
 #Pick a bug that sounds interesting, and tell one of the moderators in the channel that you're working on it. (They will let you know whether or not someone's already taken it).
 #To confirm the bug, follow these steps:
-##Do some bugzilla searching first to see if the bug might be a duplicate of an existing issue. If it is a duplicate, please add a comment stating the existing bug that this is a duplicate of, and include your IRC nickname. Also, let a moderator know in the channel, so that they can change its status to DUPLICATE.
+##Do some Bugzilla searching first to see if the bug might be a duplicate of an existing issue. If it is a duplicate, please add a comment stating the existing bug that this is a duplicate of, and include your IRC nickname. Also, let a moderator know in the channel, so that they can change its status to DUPLICATE.
 ##Attempt to perform the steps reported using a nightly build from above. Be certain that you can reproduce the bug using the nightly build.
 ##If you were able to reproduce the bug in the last step, then add a comment to the bug containing detailed steps on how you confirmed the bug. Be certain to include the buildID of the nightly (see table below), your operating system, the steps you followed, your IRC nickname (for Test Day tracking), and any other information that might be pertinent to the developer when they attempt to fix it.
-##If you have bugzilla privledges, please move the bug to the "New" state, if not, alert one of the moderators and they will do it for you.
+##If you have Bugzilla privileges, please move the bug to the "New" state, if not, alert one of the moderators and they will do it for you.
 There is more information about confirming bugs [http://www.mozilla.org/quality/help/unconfirmed.html| here].
@@ Line 132: / Line 132: @@
 # 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 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.