Confirmed users
487
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
Update to process
Rpappalardo (talk | contribs) (Update to process) |
|||
| Line 38: | Line 38: | ||
= Test Strategy = | = Test Strategy = | ||
== Process == | == Process == | ||
* When the development work on github issue is completed, whether | === Current Sprint === | ||
* QA will verify the issue, and | SUMMARY | ||
# Label Issues | |||
# Create/Update Test Cases | |||
# Verify Issues | |||
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. | |||
* 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. | |||
* TestRail type should be set to: "functional" and automation to: "Untriaged" | |||
* QA will verify the issue, and make sure to add clear test steps in the (new) TestRail test case. | |||
* 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''' | ||
* After code freeze, ideally, all issues should be marked with either ''' | * 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 ''' | * After the QA signoff, ideally, all issues should be marked with '''QAVerified''', or '''QANotNeeded'''. | ||
* The issue can be closed after it is marked as ''' | * 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). | |||
* 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". | |||
=== Current or Post Sprint === | |||
* Query github for issues labelled "automation-TBD" | |||
* Create new automated test(s) to verify proper function of feature based on steps outlined in TestRail. | |||
* Cross-link TestRail testcase within automated test (add link to java test file on github in Pre-Conditions section) | |||
* Cross-link automated test to TestRail test case (add link to TestRail test case in java file). | |||
* Submit PR for review and, once UI tests are passing, change github label to '''automated''' and set TestRail type to: "Automated" and automation to: "Completed" | |||
== Manual Tests == | == Manual Tests == | ||
UI | UI test case suite for project: "Focus for Android" will be located in [https://testrail.stage.mozaws.net/index.php?/suites/overview/48 TestRail]. As a minimum, each of the P1 UI features will have corresponding test cases. The test suite will be executed by Softvision for the acceptance testing. | ||
== Automated Tests == | == Automated Tests == | ||