QA SoftVision Team/Desktop: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 47: Line 47:


= Tasks =
= Tasks =
== Weekly==
{| class="fullwidth-table sortable" style="width: 500px;"
{| class="fullwidth-table sortable" style="width: 500px;"
|-
|-
Line 70: Line 71:
|-
|-
|}
|}
Bug triage:
===Bug triage===
the validation or invalidation of unconfirmed bugs logged by community testers (the link with the bugzilla query can be found in the spreadsheet, in the date header)
* the validation or invalidation of unconfirmed bugs logged by community testers (the link with the bugzilla query can be found in the spreadsheet, in the date header)
bugs  are to be commented and their resolution set accordingly to one of the resolutions: RESOLVED – WFM, INCOMPLETE, DUPLICATE, INVALID, WONTFIX or to NEW
* bugs  are to be commented and their resolution set accordingly to one of the resolutions: RESOLVED – WFM, INCOMPLETE, DUPLICATE, INVALID, WONTFIX or to NEW
each bug that is set to NEW has to have a regression window - http://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/
* each bug that is set to NEW has to have a regression window - http://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/


Fixed bugs verifications:
===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 RESOLVED 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


Exploratory testing:
===Exploratory testing===
ad-hoc testing on specific/error proned areas of the browser
* ad-hoc testing on specific/error proned areas of the browser
testcases are to be created during this kind of testing and written down in the specific spreadsheet
* testcases are to be created during this kind of testing and written down in the specific spreadsheet
Litmus FFTs/BFTs can be used as a starting point for the exploratory
* Litmus FFTs/BFTs can be used as a starting point for the exploratory
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/
* 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:
* 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/
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/


Update testcases in Litmus
===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
all modifications are to be registered in the created spreadsheet
* all modifications are to be registered in the created spreadsheet
 
==Periodicly==


Beside the weekly activities there are also specific tasks that are performed before the channels are merged and a new release is launched (Aurora, Beta, Final). These are as follow:
Beside the weekly activities there are also specific tasks that are performed before the channels are merged and a new release is launched (Aurora, Beta, Final). These are as follow:


Pre Aurora, Pre Beta, Pre Release specific tests:
Pre Aurora, Pre Beta, Pre Release specific tests:
Smoketests
*Smoketests
BFTs (Mozmill and Manual)
*BFTs (Mozmill and Manual)
Features owners sign off
*Features owners sign off
Ad-hoc testing
*Ad-hoc testing
 
Features owners (list available here: http://bit.ly/jVeQAf) are to take special care of their individual work on the features they own following the guideline presented on QMO:
 
http://quality.mozilla.org/docs/misc/feature-ownership-guidelines/


= Additional Information =
= Additional Information =

Navigation menu