Confirmed users
487
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
m
style tweak
Rpappalardo (talk | contribs) (Update to process) |
Rpappalardo (talk | contribs) m (style tweak) |
||
| Line 49: | Line 49: | ||
* 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 flagged as '''QAReady''', a (new) test case should be added to /updated in TestRail. | ||
* TestRail type should be set to: " | * TestRail type field should be set to: "Functional" and automation field to: "Untriaged" | ||
* QA will verify the issue, and make sure to | * 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 an issue is not QA verifiable, it can be marked with '''QANotNeeded''' | * If an issue is not QA verifiable, it can be marked with '''QANotNeeded''' | ||