View source for QA/A11y Windows touchscreen

'''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
|-
| 12/13/2016 || 1.0 || Grover Wimberly IV || Created first draft
|-
| || || ||
|}

= Overview =
== Purpose ==
Testing accessibility features with e10s for touch screen devices using Windows operating system.

== Scope ==
This wiki details the testing that will be performed for Test Pilot 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 ==
Product contact:<br />
[mailto:elancaster@mozilla.com Erin Lancaster] (IRC: )<br />
[mailto:aklotz@mozilla.com Aaron Klotz] (IRC: )<br />

User Experience contact:<br />
[mailto: ] (IRC: )<br />
[mailto: ] (IRC: )<br />

Engineering contact:<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />

QA contact:<br />
[mailto:] (IRC: )<br />
[mailto:] (IRC: )<br />


QA:<br />
PM for QA team - [mailto:rares.bologa@softvisioninc.eu Rares Bologa] (IRC: RaresB)<br />
QA Lead - [mailto:gwimberly@softvision.com Grover Wimberly IV] (IRC: Grover-QA)<br />
QA - [mailto:kkumari@softvision.com Kanchan Kumari] (IRC: )<br />
QA - [mailto:jwilliams@softvision.com Justin Williams] (IRC: )<br />
QA - [mailto:stefan.georgiev@softvision.com Stefan Georgiev] (IRC: )<br />
QA - [mailto:amasresha@softvision.com Abe Masresha] (IRC: )<br />

Feature email address: []

= Testing summary =
== Scope of Testing ==
=== In Scope ===
Test Pilot is an add-on through which users can install experiments developed by Mozilla. The experiments have a limited time in which they can be used and after that new experiments will replace the old ones. 
The scope of our testing is the Test Pilot add-on and its functionality. The testing effort for Test Pilot will be invested on the following areas:

* integration: verify the add-on integration with the current browser functionalities and UI;
* functionality: basic and advanced functionality to be verified according to the existing requirements;
* usability: the Test Pilot experiments need to be easily accessible to users;
* testing how experiments are installed and the dependencies between them;

=== Out of Scope ===
- The mobile implementation and testing.

= Requirements for testing =
== Environments ==
Testing will be performed on following OSes:

* Windows 10 (x64)

= Test Strategy =
== 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 || Install Test Pilot add-on || Verify that the add-on is correctly installed || Add-on UI changes are present in the browser || Manual || Eng Team
|-
| 2 || Test Pilot content and experiments || Verify all available related pages content and experiments || 1. Test Pilot Main page content is displayed. <br />2. Experiment page content is displayed.<br />3. Experiments are displayed in the Test Pilot door-hanger || Manual || Eng Team
|-
| 3 || Enable/Disable Experiments || Verify that the experiments can be enabled/disabled without any issues || 1. Enable Test Pilot experiments<br />2. Verify that the UI has changed in Test Pilot and browser after the experiments were installed <br />3. Verify that the Test Pilot and browser UI returned to default functionality after the experiments were uninstalled || Manual || Eng Team
|-
| 4 || User feedback || Verify that the user feedback system is working || 1. Test Pilot forum is accessible for users.<br />2. Experiments feedback page can be accessed by users.<br />3. Feedback is successfully submitted. || Manual || Eng Team
|-
| 8 || Uninstall Test Pilot add-on || Verify that the UI changes are reverted and browser returns to default || 1. Uninstall the Test Pilot add-on<br />2. Verify that the browser UI returned to default and all experiments were uninstalled || Manual || Eng Team
|-
|}


== Builds ==
Since Test Pilot is an add-on, you can install it from the following links:
* [https://testpilot.firefox.com/experiments Firefox Test Pilot Production website]
* [https://testpilot.stage.mozaws.net/ Firefox Test Pilot Stage website]
* [https://testpilot.dev.mozaws.net/ Firefox Test Pilot Dev website]
* [https://testpilot-static.dev.mozaws.net/ Firefox Test Pilot Static-Dev website]

== 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;" | 08/05/2015
|style="text-align:center;" | -
|-
| Study documentation/specs received from developers
|style="text-align:center;" | 07/04/2016
|style="text-align:center;" | -
|-
| QA - Test plan creation
|style="text-align:center;" | 08/02/2016
|style="text-align:center;" | -
|-
| QA - Test cases/Env preparation
|style="text-align:center;" | -
|style="text-align:center;" | -
|-
| QA - Nightly Testing
|style="text-align:center;" | -
|style="text-align:center;" | -
|-
| QA - Aurora Testing
|style="text-align:center;" |  
|style="text-align:center;" |  
|-
| QA - Beta Testing
|style="text-align:center;" |  
|style="text-align:center;" |
|-
| Release Date
|style="text-align:center;" |  
|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
|-
| Test case execution || TestRail
|-
| Bugs management || Bugzilla/GitHub (mainly)
|}

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

== Risk analysis ==

{| class="wikitable" style="width:60%"
|-
! Risk areas !! Mitigation
|-
| External dependencies on experiments || We should do an end-to-end test to see how experiments are integrated and behave when they are installed from Test Pilot.
|}

= References =
* [https://wiki.mozilla.org/Test_Pilot Test Pilot Wiki]
* [https://public.etherpad-mozilla.org/p/testpilot-planning-20160706 Meeting Notes]
* [https://github.com/mozilla/testpilot/issues Test Pilot site or add-on] 
* [https://wiki.mozilla.org/Test_Pilot/Experiment_Pipeline Experiment Pipeline]
* [https://wiki.mozilla.org/Test_Pilot/2016Q3 Test Pilot/2016Q3]
* [https://wiki.mozilla.org/Test_Pilot/2016Q4 Test Pilot/2016Q4]
* [https://invis.io/Q77S1H6ZC Mockups - late June 2016]
* [https://trello.com/b/TjEN1biU/test-pilot Test Pilot Trello board]

= Testcases =
== Overview ==
* Summary of testing scenarios

== Test Areas ==
{| class="wikitable" style="width:80%"
|-
! Test Areas !! Covered !! Details
|-
| Private Window
|style="text-align:center;" | Yes ||
|-
| Multi-Process Enabled
|style="text-align:center;" | Yes ||
|-
| Multi-process Disabled
|style="text-align:center;" | Yes ||
|-
| Theme (high contrast)
|style="text-align:center;" | Yes ||
|-
| '''UI'''
||  ||
|-
| Mouse-only operation  
|style="text-align:center;" | Yes ||
|-
| Keyboard-only operation  
|style="text-align:center;" | No ||
|-
| Display (HiDPI)
|style="text-align:center;" | Yes || Testing on 4k resolution monitor.
|-
| Interraction (scroll, zoom)
|style="text-align:center;" | Yes ||
|-
| Usable with a screen reader  
|style="text-align:center;" | No || e.g. with NVDA
|-
| Usability and/or discoverability testing   
|style="text-align:center;" | ? || Is this feature user friendly

|-
| '''Help/Support'''
||  ||
|-
| Help/support interface required   
|style="text-align:center;" | TBD || Make sure link to support/help page exist and is easy reachable.
|-
| Support documents planned(written)  
|style="text-align:center;" | TBD || Make sure support documents are written and are correct.

|-
| '''Install/Upgrade'''
||  ||
|-
| Feature upgrades/downgrades data as expected   
|style="text-align:center;" | Yes ||
|-
| Does sync work across upgrades   
|style="text-align:center;" | Yes || The add-on is not kept after sync on another device for the same Fx account.
|-
| Requires install testing    
|style="text-align:center;" | Yes || The add-on can be installed from Test Pilot homepage or trough ".xpi" file.
|-
| Affects first-run or onboarding     
|style="text-align:center;" | Yes || The add-on displays a notification at startup when there are new experiments available.
|-
| 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;" | ? || Testing was not conducted by SV QA Eng team.
|-
| Telemetry correctness testing   
|style="text-align:center;" | ? || Testing was not conducted by SV QA Eng team.
|-
| Server integration testing   
|style="text-align:center;" | ? || Testing was not conducted by SV QA Eng team.
|-
| Offline and server failure testing   
|style="text-align:center;" | ? ||
|-
| Load testing   
|style="text-align:center;" | ? || Testing was not conducted by SV QA Eng team.

|-
| ''' 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;" | Yes || Tested with other experiments installed.  

|-
| ''' 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;" | No ||
|-
| Survey of many sites for compatibility   
|style="text-align:center;" | No ||

|-
| ''' 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;" | Yes ||
|}

== Test suite ==
* Full Test suite - [https://testrail.stage.mozaws.net/index.php?/suites/view/54&group_by=cases:section_id&group_order=asc Test Pilot Full Functional (TestRail)]
* Smoke Test suite -* Regression Test suite - TBD

= Bug Work =
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1290601 Tracking bug]
* Found issues list - [https://docs.google.com/spreadsheets/d/1wkMhNtl-g7cy0c4Esu_bdpbB1E0cO5uWq1ad-6g_dZ4/edit#gid=421655835 QA Eng found issues]
* Bugzilla logged bugs - TBD

= 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 />
* Full Functional & Smoke testing - [https://testrail.stage.mozaws.net/index.php?/runs/overview/3 TestRail run results]


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

== Checklist ==
{| class="wikitable" style="width:60%"
|-
! Exit Criteria !! Status !! Notes/Details
|-
|  Testing Prerequisites (specs, use cases)
| style="text-align:center;" | {{mdone|}}  
| style="text-align:center;" |
|-
|  Testing Infrastructure setup
|style="text-align:center;" | No ||
|-
|  Test Plan Creation
| style="text-align:center;" | {{mdone|}} ||
|-
|  Test Cases Creation
|style="text-align:center;" | {{mdone|}} ||
|-
|  Full Functional Tests Execution
|style="text-align:center;" | {{mprog|}} ||
|-
|  Smoke Tests Execution
|style="text-align:center;" |  ||
|-
|  Automation Coverage ||
|style="text-align:center;" |
|-
|  Performance Testing
|style="text-align:center;" |  ||
|-
|  All Defects Logged || ||
|-
|  Critical/Blockers Fixed and Verified || ||
|-
|  Daily Status Report (email/etherpad statuses/ gdoc with results) || ||
|-
|  Metrics/Telemetry||
|style="text-align:center;" | N/A
|-
|  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
|}