View source for QA/Net Monitor MVP

'''Revision History'''

This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded).  The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.

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

= Overview =
== Purpose ==
Detail the purpose of this document. For example:
* The test scope, focus areas and objectives
* The test responsibilities
* The test strategy for the levels and types of test for this release
* The entry and exit criteria
* The basis of the test estimates
* Any risks, issues, assumptions and test dependencies
* The test schedule and major milestones
* The test deliverables

== Scope ==
This wiki details the testing that will be performed by the project team for the '''Net Monitor MVP''' project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
* What will be tested
* How testing will be performed

== Ownership ==
 What resources are needed, and when (developers, QA, PMs working on the feature)

Engineering contact(s):
* [mailto:odvarko@gmail.com Jan Honza Odvarko (:Honza)] 

QA contact(s):
* [mailto:florin.mezei@softvisioninc.eu Florin Mezei (:FlorinMezei)] - Project Manager of the Release QA Team
* [mailto:andrei.vaida@softvision.eu Andrei Vaida (:avaida)] - Team lead of Release QA Team
* [mailto:ciprian.georgiu@softvision.ro Ciprian Georgiu (:ciprian_georgiu)] - leading QA efforts
* [mailto:iulia.cristescu@softvision.ro Iulia Cristescu (:IuliaC)] - leading QA efforts (peer)

= Testing summary = 
== Scope of Testing ==
=== In Scope ===

Testing efforts will be focused on confirming that Net Monitor MVP is working as expected across platforms.

=== Out of Scope ===
Only the Net Monitor MVP feature functionality  will be included in the testing efforts. Any others functionalities, that are not related to this feature, are not going to be evaluated in order to find whether it satisfies the specified requirements or not.

= Requirements for testing =
== Environments ==
Full testing will be done on following OSes:
* Windows 7 
* Windwos 10
* Ubuntu 16.04 LTS
* Ubuntu 14.04 LTS
* Mac OS X 10.11 or greater

=About Netmonitor MVP=

The Network Monitor shows you all the network requests Firefox makes (for example, when it loads a page, or due to XMLHttpRequests), how long each request takes, and details of each request.
The Network Monitor records network requests any time the Toolbox is open, even if the Network Monitor itself is not selected. This means you can start debugging a page in, for example, the Web Console, then switch to the Network Monitor to see network activity without having to reload the page.

In product development, the minimum viable product (MVP) is a product with just enough features to gather validated learning about the product and its continued development.

== 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 

|-
| 1 || Netmonitor Details panel (Header) is working properly || 
The Headers tab is properly displayed and lists the basic info about the request:
* request URL
* request method
* remote IP address and port
* status code
* the HTTP request and response headers that were sent
* a button to edit and resend the request <br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team
|-
| 2 || Netmonitor Details panel (Cookies) || 
The Cookies tab correctly lists full details of any cookies sent with the request or response.<br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team 
|-

| 3 || 	Netmonitor Details panel (Params) || 
The Params tab is properly displays the GET parameters and POST data of a request. <br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team 
|-

| 4 || Netmonitor Details panel (Response) || 
	
The Response tab is properly displayed and if the response is HTML, JS, or CSS, it will be shown as text.

If the response is JSON, it will be shown as an inspectable object.
If the response is an image, the tab displays a preview. <br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team 
|-

| 5 || Netmonitor Details panel (Timings) || 
	
The Timings tab is displayed properly with the following subset of the stages defined in the HTTP Archive specification:
* Blocked
* DNS resolution
* Connecting
* Sending
* Waiting
* Receiving. <br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team 
|-

| 6 || Netmonitor Details panel (Security)  || 
	
The Security tab is properly displayed with details about the secure connection used including the protocol, the cipher suite, and certificate details.<br>
 || all scenarios provided must have the right expected result || Manual || Desktop Team 
|-

|}
== 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;" | 17-03-2017
|style="text-align:center;" | tbd
|-
| Study documentation/specs received from developers
|style="text-align:center;" | 17-03-2017 
|style="text-align:center;" | 17-03-2017 
|-
| QA - Test plan creation 
|style="text-align:center;" | 31-03-2017
|style="text-align:center;" | 31-03-2017 
|-
| QA - Test cases/Env preparation 
|style="text-align:center;" | 17-03-2017
|style="text-align:center;" | 17-03-2017  
|-
| QA - Nightly Testing 
|style="text-align:center;" | n/a
|style="text-align:center;" | n/a  
|-
| QA - Aurora Testing
|style="text-align:center;" | 20-03-2017
|style="text-align:center;" | 21-03-2017
|-
| 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 || [https://testrail.stage.mozaws.net/index.php?/suites/view/727&group_by=cases:section_id&group_order=asc]/ Google docs [https://docs.google.com/spreadsheets/d/1X5fcbl1NOWd9o6dtspepl-t3ww0ZaTv4a4XEd5n58XI/edit]
|-
| Test case execution || [https://testrail.stage.mozaws.net/index.php TestRail]
|-
| Bugs management || Bugzilla
|}

= 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

= References =
* List and links for specs
  List and links for available specs - documents, user stories, specifications
* Meta bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1307743].

= Testcases = 
== Test Areas ==
{| class="wikitable" style="width:80%"
|-
! Test Areas !! Covered !! Details
|-
| Private Window 
|style="text-align:center;" | || 
|-
| Multi-Process Enabled 
|style="text-align:center;" |  || 
|-
| Multi-process Disabled 
|style="text-align:center;" |  || 
|-
| Theme (high contrast) 
|style="text-align:center;" |  || 
|-
| '''UI''' 
||  || 
|-
| Mouse-only operation  
|style="text-align:center;" |  || 
|-
| Keyboard-only operation  
|style="text-align:center;" |  ||
|-
| Display (HiDPI) 
|style="text-align:center;" | || 
|-
| Interaction (scroll, zoom) 
|style="text-align:center;" | || 
|-
| Usable with a screen reader  
|style="text-align:center;" |  || e.g. with NVDA
|-
| Usability and/or discoverability testing   
|style="text-align:center;" |  || Is this feature user friendly
|-
| RTL build testing   
|style="text-align:center;" |  ||
|-
| '''Help/Support''' 
||  || 
|-
| Help/support interface required   
|style="text-align:center;" |  || Make sure link to support/help page exist and is easy reachable.
|-
| Support documents planned(written)  
|style="text-align:center;" |  || Make sure support documents are written and are correct.

|-
| '''Install/Upgrade''' 
||  || 
|-
| Feature upgrades/downgrades data as expected   
|style="text-align:center;" |  ||
|-
| Does sync work across upgrades   
|style="text-align:center;" |  || 
|-
| Requires install testing    
|style="text-align:center;" |  || separate feature/application installation needed (not only Firefox)
|-
| Affects first-run or onboarding     
|style="text-align:center;" |  || Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned.
|-
| Does this affect partner builds? Partner build testing  
|style="text-align:center;" |  || yes/no options, add comment with details about who will lead testing

|-
| ''' Enterprise ''' 
||  ||  Raise up the topic to developers to see if they are expecting to work different on ESR builds
|-
| Enterprise administration   
|style="text-align:center;" |  || 
|-
| Network proxies/autoconfig   
|style="text-align:center;" |  || 
|-
| ESR behavior changes   
|style="text-align:center;" |  || 
|-
| Locked preferences  
|style="text-align:center;" |  ||

|-
| ''' Data Monitoring ''' 
||  || 
|-
| Temporary or permanent telemetry monitoring   
|style="text-align:center;" |  || List of error conditions to monitor
|-
| Telemetry correctness testing   
|style="text-align:center;" |  || 
|-
| Server integration testing   
|style="text-align:center;" |  || 
|-
| Offline and server failure testing   
|style="text-align:center;" |  ||
|-
| Load testing   
|style="text-align:center;" |  ||

|-
| ''' Add-ons ''' 
||  || If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on.
|-
| Addon API required?   
|style="text-align:center;" |  || 
|-
| Comprehensive API testing   
|style="text-align:center;" |  || 
|-
| Permissions   
|style="text-align:center;" |  || 
|-
| Testing with existing/popular addons
|style="text-align:center;" |  || 

|-
| ''' Security ''' 
||  || Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature.
|-
| 3rd-party security review   
|style="text-align:center;" |  || 
|-
| Privilege escalation testing
|style="text-align:center;" |  || 
|-
| Fuzzing   
|style="text-align:center;" |  || 

|-
| ''' Web Compatibility ''' 
||  || depends on the feature
|-
| Testing against target sites   
|style="text-align:center;" |  || 
|-
| Survey of many sites for compatibility   
|style="text-align:center;" |  || 

|-
| ''' Interoperability  ''' 
||  || depends on the feature
|-
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers.   
|style="text-align:center;" |  || 
|-
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS   
|style="text-align:center;" |  || 
|-
| Interaction of this feature with other browser features   
|style="text-align:center;" |  || 
|}

== Test suite ==
 Full Test suite - Link to test rail - tascases should be added under Firefox Desktop project [https://testrail.stage.mozaws.net/index.php?/suites/view/727&group_by=cases:section_id&group_order=asc link]
 Smoke Test suite - Link with the tests - if available/needed.
 Regression Test suite - Link with the tests - if available/needed.

= Bug Work =
Meta bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1307743 - (netmonitor-html) [meta] Migrate Net panel to HTML]

<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
====== Logged bugs (netmonitor-html) [meta] Migrate Net panel to HTML [https://bugzilla.mozilla.org/show_bug.cgi?id=1307743] ======

<div class="mw-collapsible-content">
<bugzilla>
    {
        "id":"1349173, 1346380, 1349198, 1353335, 1366983",
        "include_fields": "id, priority, component, assigned_to, summary, status, target_milestone"
    }
</bugzilla>

</div>
</div>

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

====== Bug fix verification ======
<div class="mw-collapsible-content">
<bugzilla>
    {
        "blocks":[1307743],
        "resolution":"FIXED",
        "include_fields": "id, priority, component, assigned_to, summary, status, resolution, target_milestone"
    }
</bugzilla>
</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
** Full Test suite, link to TestRail - Tests Runs and Results [https://testrail.stage.mozaws.net/index.php?/suites/view/727&group_by=cases:section_id&group_order=asc link]
** Daily Smoke, lif needed/available
** 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

'''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 
|}