352
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
QA/Mobile/FocusAndroidTestPlan (view source)
Revision as of 21:21, 22 November 2018
, 22 November 2018→Current Sprint: simplify
(→Current Sprint: update) |
(→Current Sprint: simplify) |
||
| Line 42: | Line 42: | ||
* Once an issue has been closed, when applicable, a (new) test case should be added to /updated in TestRail. | * Once an issue has been closed, when applicable, 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 if exists. | * Upon completion, github issue should be marked with '''QAVerified''', removing '''QAReady''' label if exists. | ||
* After the QA signoff, ideally, all issues should be marked with '''QAVerified | * After the QA signoff, ideally, all verifiable issues should be marked with '''QAVerified'''. | ||
* 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". | ||