QA/Mobile/ReferenceBrowserTestPlan: Difference between revisions

** When the development work on a github issue is completed (before/after code freeze), the issue will be closed and marked with 'QAReady' status label.

** Once an issue has been closed, when applicable, a (new) test case should be added to /updated in TestRail.

** 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''' status label if exists.

** 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).

** 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".