Add-ons/QA/Testplan/NewHeader: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 10: Line 10:


= Overview =
= Overview =
Currently, every add-on version listed on AMO is manually code reviewed by a human (called: reviewer). This process is meant to ensure a good user experience with add-ons. This manual review process requires significant human effort and this is why we need '''auto-approvals''' - a change that will be implemented in the review process, Reviewer Tools and submission to move to a hybrid system that includes human reviews as well as automatic reviews.
A new design for the AMO header , on Desktop and Mobile


== Purpose ==
== Purpose ==
Reducing delays in reviews (delays present due to decreased reviewer activity and increase submissions) by automatically reviewing some add-ons (that meet a list of criteria).
Change the design of AMO header, following the new design specs




=== Entry Criteria ===
=== Entry Criteria ===
* QA has access to [https://docs.google.com/document/d/1VxvvzQQvfDOVCylSVlpfeXv0tDYRLZfIMvWOoraANGU/edit#heading=h.diha6b7e1on6 PRD] and instructions (from bugs)
* QA has access to [https://github.com/mozilla/addons-frontend/blob/master/assets/sketch%20files/AMO%20Desktop%20-%20Master.sketch mocks] and instructions (from bugs)
* The feature has landed in [https://addons-dev.allizom.org/en-US/firefox/ -dev]
* The feature has landed in [https://addons-dev.allizom.org/en-US/firefox/ -dev]


=== Current Status ===
=== Current Status ===
* The feature was released.
* The feature is on -dev.


=== Exit Criteria ===
=== Exit Criteria ===
Line 31: Line 31:
== Scope ==
== Scope ==
===what's in scope?===
===what's in scope?===
* Add a counter for approvals since last automatic review
* Test the new AMO header for UI and functionality issues
* Get extensions auto-approved if they meet the following criteria:
* Test on both AMO and Mobile
** Have been manually approved once
** Are not flagged for admin review (this can happen automatically on submission in some cases, but is generally done manually by reviewers)
** Are WebExtensions
** Active Daily Users are under 10K (initially set to this value, but configurable).
** Are not triggering any of the following linter warnings:
*** CSP
*** Native Messaging
        
        
'''Not yet implemented:''' 
* Auto-approve extensions that are not triggering content scripts warnings for all URLs at validation


===what's out of scope?===
===what's out of scope?===
* Human unreviewed extensions
* None
* Embedded Webextensions


== Ownership ==
== Ownership ==
Line 75: Line 65:
|-
|-
| Start project  
| Start project  
|style="text-align:center;" | 31.01.2017 ||  
|style="text-align:center;" | 25.05.2017 ||  
|-
|-
| Study PRD/mocks received  
| Study PRD/mocks received  
|style="text-align:center;" | 01.02.2017 ||  
|style="text-align:center;" | 09.06.2017 ||  
|-
|-
| QA - Test plan creation  
| QA - Test plan creation  
|style="text-align:center;" | 21.04.2017 ||  
|style="text-align:center;" | 12.06.2017 ||  
|-
|-
| QA - Test cases preparation  
| QA - Test cases preparation  
|style="text-align:center;" | 21.04.2017 ||  
|style="text-align:center;" | 13.06.2017 ||  
|-
|-
| QA - Test cases execution   
| QA - Test cases execution   
|style="text-align:center;" | 24.04.2017 ||  
|style="text-align:center;" | 13.06.2017 ||  
|-
|-
| Release Date  
| Release Date  
|style="text-align:center;" | 27.04.2017 (Q1 - 2017)  
|style="text-align:center;" | (Q2 - 2017)  
|}   
|}   
    
    
Created an etherpad with more detailed scenarios - [https://public.etherpad-mozilla.org/p/auto-approvals Auto-Approvals]


== Testing Tools ==
== Testing Tools ==
Line 102: Line 91:
| Test plan creation || Mozilla wiki
| Test plan creation || Mozilla wiki
|-
|-
| Test case creation || [https://testrail.stage.mozaws.net/index.php?/suites/view/939 TestRail]
| Test case creation || TestRail - TBD
|-
|-
| Test case execution ||[https://testrail.stage.mozaws.net/index.php?/suites/view/939 TestRail]
| Test case execution || TestRail - TBD
|-
|-
| Bugs management || Github
| Bugs management || Github
Line 110: Line 99:


= References =
= References =
  * PRD - https://docs.google.com/document/d/1VxvvzQQvfDOVCylSVlpfeXv0tDYRLZfIMvWOoraANGU/edit#
  * Mocks for AMO desktop - https://github.com/mozilla/addons-frontend/blob/master/assets/sketch%20files/AMO%20Desktop%20-%20Master.sketch
  * Tracker: [https://github.com/mozilla/addons-server/issues/4533 4533]
  * Tracker: [https://github.com/mozilla/addons-frontend/issues/2436 2436]


= Testcases =  
= Testcases =  
Line 118: Line 107:


== Test suite ==
== Test suite ==
  Full [https://testrail.stage.mozaws.net/index.php?/suites/view/939 Test Suite]
  Full Test Suite TBD


= Bug Work =
= Bug Work =
* Feature implementation bug - [https://github.com/mozilla/addons-server/issues/4533 4533]   
* Feature implementation bug - [https://github.com/mozilla/addons-frontend/issues/2436 2436]   


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
181

edits