View source for Add-ons/QA/Testplan/OOP-WebExtensions

'''Revision History'''

{| class="wikitable" style="width:60%"
|-
! Date !! Version !! Author !! Description 
|-
| 02/03/2017 || 1.0 || Vasilica Mihasca || Created first draft
|-
|}


= Overview =
With webext-oop, addon code runs in a separate process (bugzil.la/webext-oop).
In the far future, addon code may also run in multiple processes.

== Purpose ==


=== Entry Criteria ===
* QA has access to all the PRDs, mocks and related documents
* The feature has landed on Nightly

=== Exit Criteria ===
* All the bugs against the feature have been triaged
* All the P1/P2 bugs have been fixed
* All the resolved bugs have been verified by QA
* The find/fixed rate is going down over a predefined period of time

=== Acceptance Criteria ===
This section broadly outlines when the product is ready to ship
* QA has signed off
* All the required Telemetry is in place
* All info is localized at least for a pre-defined set of locales
* All the necessary PR/blogposts have been sent out

== Scope ==
This section describes what parts of the feature will be tested and what parts won't be.

===what's in scope?===
* Webextensions installation with e10s enabled
* Webextensions running in their own process
* Regression testing for the top 20 webextensions

===what's out of scope?===
* Security testing
* Performance testing

== Ownership ==
Dev Lead: []; irc nick <br />
QA Manager: [mailto:kraj@mozilla.com Krupa Raj]; irc nick :krupa<br /> 
QA Lead: [mailto:vcarciu@softvision.ro Victor Carciu]; irc nick :victorc<br />
Webextensions QA: [mailto:vasilica.mihasca@softvision.ro Vasilica Mihasca]; irc nick :vasilica_mihasca<br />
Add-ons QA: [mailto:valentina.peleskei@softvision.ro Valentina Peleski]; irc nick :ValentinaV<br />

= Requirements for testing =
== Environments ==
OSed covered: Windows, Mac OS X, Linux

== Test Objectives ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
This could be documented in bullet form or in a table similar to the one below.

{| class="wikitable"
|-
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners 
|-
|}

== Builds ==
This section should contain links for builds with the feature - 
* Links for Nightly builds
* Links for Aurora builds
* Links for Beta builds

== Test Execution Schedule ==
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
|-
! Project phase !! Start Date !! End Date
|-
| Start project 
|style="text-align:center;" |  || 
|-
| Study documentation/specs received from developers
|style="text-align:center;" |  || 
|-
| QA - Test plan creation 
|style="text-align:center;" | 02-03-2017 || 
|-
| QA - Test cases/Env preparation 
|style="text-align:center;" | || 
|-
| QA - Nightly Testing 
|style="text-align:center;" | || 
|-
| QA - Aurora Testing
|style="text-align:center;" |  ||  
|-
| QA - Beta Testing 
|style="text-align:center;" |  || 
|-
| Release Date 
|style="text-align:center;" | || 
|}

== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
{| class="wikitable" style="width:50%"
|-
! Process !! Tool
|-
| Test plan creation || Mozilla wiki
|-
| Test case creation || [ TestRail] / [Google docs] / [etherpad]
|-
| Test case execution || [TestRail]
|-
| Bugs management || Bugzilla / Github
|}

= Status = 
== Overview ==
 Track the dates and build number where feature was released to Nightly
 Track the dates and build number where feature was merged to Aurora
 Track the dates and build number where feature was merged to Release/Beta

== Risk analysis ==
 Identify the high-risk assumptions
 Identify existing bugs on the feature with high risk
 Identify if other areas are affected by the fix

= References =
 * List and links for specs
   PRD - 
 * {{Bug|1190679}} - (webext-oop) Run WebExtensions out of process
<bugzilla>
    {
        "blocks":[1190679],
        "include_fields": "id, priority, component, assigned_to, summary, status, target_milestone"
    }
</bugzilla>


= Bug Work =
Tracking bug - [https://bugzilla.mozilla.org/show_bug.cgi?id=1190679 bug 1190679]

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

====== Bug fix verification ======
<div class="mw-collapsible-content">
</div></div>

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

====== Logged bugs ======
<div class="mw-collapsible-content">

</div>
</div>

= Sign off =
== Criteria ==
Check list
* All test cases should be executed
* Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

== Results ==
'''Nightly testing'''<br />

List of OSes that will be covered by testing<br />
*Link for the tests run
** Daily Smoke, use template from [link]
** Full Test suite, use template from [ link]
** Regression Test suite, if needed/available

'''Merge to Aurora Sign-off'''
List of OSes that will be covered by testing<br />
*Link for the tests run
** Full Test suite

== Checklist ==
{| class="wikitable" style="width:60%"
|-
! Exit Criteria !! Status !! Notes/Details
|-
|  Testing Prerequisites (specs, use cases) 
| style="text-align:center;" |   
| style="text-align:center;" | 
|-
|  Testing Infrastructure setup 
|style="text-align:center;" |   || 
|-
|  Test Plan Creation 
| style="text-align:center;" |   || 
|-
|  Test Cases Creation 
|style="text-align:center;" |   || 
|-
|  Full Functional Tests Execution 
|style="text-align:center;" |  
|style="text-align:center;" |  
|-
|  Automation Coverage ||
|style="text-align:center;" | 
|-
|  Performance Testing 
|style="text-align:center;" |  || 
|-
|  All Defects Logged || || 
|-
|  Critical/Blockers Fixed and Verified || || 
|-
|  Metrics/Telemetry|| 
|style="text-align:center;" | 
|-
|  QA Signoff  - Nightly Release|| 
|style="text-align:center;" | Email to be sent 
|-
|  QA Aurora - Full Testing 
|style="text-align:center;" |  || 
|-
|  QA Signoff  - Aurora Release || 
|style="text-align:center;"| Email to be sent 
|-
|  QA Beta - Full Testing
|style="text-align:center;" |  || 
|-
|  QA Signoff  - Beta Release || 
|style="text-align:center;" | Email to be sent 
|}