QA/Mobile/FocusAndroidTestPlan: Difference between revisions

Jump to navigation Jump to search

QA/Mobile/FocusAndroidTestPlan (view source)

Revision as of 20:42, 22 November 2018

367 bytes removed ,  22 November 2018
→‎Current Sprint: Process update
(→‎Personnel: personnel change)
(→‎Current Sprint: Process update)
Line 38: Line 38:


DESCRIPTION
DESCRIPTION
* When the development work on github issue is completed, whether before/after code freeze, '''ReadyForQA''' label will be applied so that the issue is available for testing.  
* When the development work on github issue is completed, whether before/after code freeze, the issue will be closed so that the issue is available for testing.  
* The issue should belong to a correct milestone before development work can be started and may include either new features or bugs.
* The issue should belong to a correct milestone before development work can be started and may include either new features or bugs.
* Once an issue has been flagged as '''QAReady''', a (new) test case should be added to /updated in TestRail.
* Once an issue has been closed, a (new) test case should be added to /updated in TestRail.
* TestRail type field should be set to: "Functional" and automation field to: "Untriaged"
* TestRail type field should be set to: "Functional" and automation field to: "Untriaged"
* QA will verify the issue, and make sure to outline clear test steps in the (new) TestRail test case.
* QA will verify the issue, and make sure to outline clear test steps in the (new) TestRail test case.
* Upon completion, github issue should be marked with '''QAVerified''', removing '''QAReady''' label.
* Upon completion, github issue should be marked with '''QAVerified''', removing '''QAReady''' label if exists.
* If an issue is not QA verifiable, it can be marked with '''QANotNeeded'''
* After the QA signoff, ideally, all issues should be marked with '''QAVerified'''.
* After code freeze, ideally, all issues should be marked with either '''QAReady''', '''QAVerified''', or '''QANotNeeded'''.
* After the QA signoff, ideally, all issues should be marked with '''QAVerified''', or '''QANotNeeded'''.
* The issue can be closed after it is marked as '''QAVerified''', or '''QANotNeeded''' (this does not apply to metabugs).
* NOTE: the meta-label '''testing''' is also added by both devs and QA for any bug or feature requiring testing of any kind).
* NOTE: the meta-label '''testing''' is also added by both devs and QA for any bug or feature requiring testing of any kind).
* Once the issue is closed, if suitable for automation, label the it in github as '''automation-TBD''' and change the automation dropdown in TestRail to "Suitable".
* Once the issue is closed, if suitable for automation, label the it in github as '''automation-TBD''' and change the automation dropdown in TestRail to "Suitable".
Npark
352

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1204236"

Navigation menu