352
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
QA/Mobile/FocusAndroidTestPlan (view source)
Revision as of 20:49, 22 November 2018
, 22 November 2018→Current Sprint: update
(→Current Sprint: Process update) |
(→Current Sprint: update) |
||
| Line 38: | Line 38: | ||
DESCRIPTION | DESCRIPTION | ||
* 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. | * 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. If a bug requires extra attention, it'll be marked with 'QAReady' label. | ||
* 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 closed, 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. If the issue is not verificable, then the '''QANotNeeded''' label will be applied. | ||
* 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 issues should be marked with '''QAVerified''' or '''QANotNeeded'''. | ||
* 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". | ||