QA SoftVision Team/Desktop: Difference between revisions

QA SoftVision Team/Desktop (view source)

Revision as of 09:11, 8 August 2011

252 bytes added , 8 August 2011

→‎Weekly

George.carstoiu

464

edits

@@ Line 61: / Line 61: @@
 |-
 | Bug triage
-| Nighly
+| Nightly
 | [http://bit.ly/lwFNN6 Spreadsheet link]
 |-
@@ Line 87: / Line 87: @@
 ===Fixed bugs verifications===
-* the verification of fixed bugs -issues should be commented and resolution set to either RESOLVED FIXED or REOPENED
+* the verification of fixed bugs -issues should be commented and resolution set to either VERIFIED FIXED or REOPENED
-* verification is performed across all platforms against which the bug was logged
+* verification is performed across all platforms against which the bug was logged and on all channels to which the patch applies.
 ===Exploratory testing===
@@ Line 96: / Line 96: @@
 * each NEW bug has to have a regression window - http://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/
 * Logged bugs should respect the best practices presented here:
-** http://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/
+** [http://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ How to write a proper bug - part 1]
-** http://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug-part-2/
+** [http://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug-part-2/ How to write a proper bug - part 2]
+** [http://bit.ly/oupbcj Testcase writing primer]
 ===Update testcases in Litmus===
-* based on the Litmus Unclear, Broken / Fail reports, testcases should be kept up-to-date
+* based on the Litmus Unclear, Broken / Fail reports, testcases should be kept up-to-date and the testing results must be vetted/unvetted - [http://bit.ly/p5WdBd Guide]
 * all modifications are to be registered in the created spreadsheet