QA/DownloadPanel DropMarker: Difference between revisions

Jump to navigation Jump to search

QA/DownloadPanel DropMarker (view source)

Revision as of 14:01, 21 September 2016

17,786 bytes added ,  21 September 2016
Undo revision 1148570 by AdiFlorinescu (talk)
No edit summary
(Undo revision 1148570 by AdiFlorinescu (talk))
Line 1: Line 1:
'''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
|-
| 09/20/2016|| 1.0 || Adrian Florinescu || Initial Draft
|}
= Overview =
== Purpose ==
The redesign of the Download Manager with additional changes to the Content Handling is documented from the test point of view in [https://wiki.mozilla.org/QA/Content_Handling Content_Handling TestPlan]. Working and landing the finished or in progress work is done in stages which cover a reduced area. This test plan cover such a stage which is part of the Download Panel UX Redesign.
== Scope ==
This wiki details the testing that will be performed by the project team for the Content Handler 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 ==
• EPM (Manager: [mailto:vchen@mozilla.com Vance Chen])
* [mailto:wehuang@mozilla.com Wesly Huang]
• UX (Manager: [mailto:hhsu@mozilla.com Harly Hsu])
* [mailto:bmao@mozilla.com Bryant Mao]
* [mailto:chuang@mozilla.com Carol Huang] - Visual Designer
* [mailto:mochen@mozilla.com Morpheus Chen]
• Front End (Manager [mailto:ehung@mozilla.com Evelyn Hung])
* [mailto:selee@mozilla.com Sean Lee]
* [mailto:yliao@mozilla.com YiFan Liao]
• Platform (Manager: [mailto:btian@mozilla.com Ben Tian])
* [mailto:alchen@mozilla.com Alphan Chen]
* [mailto:echuang@mozilla.com Eden Chuang]
* [mailto:wiwang@mozilla.com Will Wang]
• QA (Manager: [mailto:atsai@mozilla.com Al Tsai])
• QA (Lead: [mailto:brindusa.tot@softvision.com Brindusa Tot])
• QA
* [mailto:whsu@mozilla.com William Hsu]
*[mailto:adrian.florinescu@softvision.ro Adrian Florinescu]
*[mailto:ovidiu.boca@softvision.ro Ovidiu Boca]
*[mailto:roxana.leitan@softvision.ro Roxana Leitan]
*[mailto:simona.badau@softvision.ro Simona Badau]
= Testing summary =
== Scope of Testing ==
=== In Scope ===
As specified in the Overview section, The DownloadPanel Dropmarker is a small redesign section of a bigger redesign and refactoring project: see [meta] Firefox Download Panel UX Redesign). The work contained in this small section surrounds the dropmarker area and some additional visual enhancements. The development tracking issues are the following: 1269962 , 1282689 , 1297039 , 1297657 , 1298276 , 1299712.
# Signoff Smoke Testing
# Functional Testing
# Regression testing
# Usability testing
=== Out of Scope ===
Following areas/features are considered out of scope and will not be considered as testing zones to be handled in this test plan.
# Scan security hole (Security team will deal with it. If any patches exist security concern, we will add "sec-review" flag on the bug)
# Download manager features: this set of features handles mostly visual changes and it brings reduced functionality adjustments, therefore from functionality point of view, QA will only check if regressions have crept with the new design adjustments.
# Performance testing will also not be covered since it is not seen as a risk for this stage.
= Requirements for testing =
== Environments (TBC)==
* Linux
* OS X 10.10
* Windows 7 x 32
* Windows 10 x64
= Test Strategy =  
= Test Strategy =  
== Test Objectives ==
== Test Objectives ==
Line 11: Line 83:
|-
|-
| 2 || Download panel :: Overview || Verify the number of maximum download items displayed || Max numbers of download items displayed at the same time: 5 || Manual || Eng Team
| 2 || Download panel :: Overview || Verify the number of maximum download items displayed || Max numbers of download items displayed at the same time: 5 || Manual || Eng Team
|-
| 3 || Download panel :: Summary section || Verify the summary section for Multiple Files information in Downloads Panel || 1. New Icon in summary section <br /> 2. Format change of downloading/completeness status <br /> 3. ETA format is changed to Xm XXs left <br /> 4. Show the overall network speed. <br /> *UX spec, https://mozilla.invisionapp.com/share/4Y6ZZH1E8#/screens/156737043 || Manual || Eng Team
|-
|-
| 4 || Download panel :: Show All Downloads || Verify "Show All Downloads" session in Downloads Panel || 1. - A new button for dropdown menu to display the three new features. <br />  - Clear List  <br />  - Open Downloads Folder <br />  - Download Settings <br />  - Display “Show All Downloads” section when the mouse hover on the summary section. This only happens when the extra summary section is shown. <br /> *UX spec, https://mozilla.invisionapp.com/share/4Y6ZZH1E8#/screens/156737044  || Manual || Eng Team
| 4 || Download panel :: Show All Downloads || Verify "Show All Downloads" session in Downloads Panel || 1. - A new button for dropdown menu to display the three new features. <br />  - Clear List  <br />  - Open Downloads Folder <br />  - Download Settings <br />  - Display “Show All Downloads” section when the mouse hover on the summary section. This only happens when the extra summary section is shown. <br /> *UX spec, https://mozilla.invisionapp.com/share/4Y6ZZH1E8#/screens/156737044  || Manual || Eng Team
|-
|-
| 5 || Download status || Verify all download status || The download status information for each item in download panel is redesigned. Here are new statuses. <br /> - Starting <br /> - Downloading <br /> - Complete <br /> - Pause <br /> - Cancelled <br /> - Failed <br /> - Deleted || Manual || Eng Team
|-
| 6 || Downloads remaining time || Verify downloads remaining time on the downloads button  || The remaining time on download indicator is removed || Manual || Eng Team
|-
| 7 || Animation and downloads remaining time || Verify animation and downloads remaining time on the downloads button || 1. The remaining time on download indicator is removed <br /> 2. An animation to notify a user whenever a download is completed while a user is downloading multiple files. <br /> 3. Show an alert icon on the downloads button when a download fails || Manual || Eng Team
|-
| 8 || File handling flow || Verify the new UI and flow || 1. While a non-previewable link is clicked, no Open/save dialog is popped up <br /> 2. The add-on or plugin is the default handler after installation if it registers as a content handler || Manual || Eng Team
|-
| 9 || Protocol Handling Flow || Verify the new UI and flow || Pop-up possible protocol handlers or request OS to handle it, while click a protocol link has no default handler || Manual || Eng Team
|}
|}


Line 74: Line 157:
|-
|-
| Bugs management || Bugzilla
| 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
== Testing risks and mitigation ==
=== TESTING RISK ===
Risks can be organized into these categories.
* '''Test planning and scheduling''' : It may occur when there is no separate test plan, but rather highly incomplete and superficial summaries in other planning documents. Also, test plans are often ignored once we are written. Regarding the schedule, the schedule of testing is often inadequate for the amount of testing that should be performed in TDC, especially when testing is primarily manual.
* '''Stakeholder involvement''' : The wrong mindset would introduce wrong thought of testing, having wrong testing expectations, and having stakeholders who are inadequate committed to and supporting of the testing effort. Therefore, we must align expectations with reality between stakeholders before we kick off testing.
* '''Process integration''' : It often occurs when testing and engineering processes are poorly integrated. We sometimes take a "one-size-fits-all" approach taken to testing, regardless of the specific needs of the project.
* '''Test communication risk''' : This problems often occurs when test documents are not maintained or inadequate communication.
=== RISK MITIGATION ===
QA team would like to use following flow to address risk.
* '''Risk Identification''': Risks can be identified using a number of resources. E.g., project objectives, risk lists of past projects, prior knowledge, understanding of system architecture or design, prior bug reports, and complaints. For example, if certain areas of the system are unstable and those areas are being developed further in the current project, it should be listed as a risk. It is good to document the identified risks in detail so that it stays in project memory and can be clearly communicated to project stakeholders.
* '''Risk Prioritization''' : If a risk is fully understood, it is easy for us to prioritize a risk by two measures. (1) Risk Impact and (2) Risk Probability are applied to each risk. Risk Impact is estimated in tangible terms or on a scale (e.g., 10 to 1 or High to Low). Risk Probability is estimated somewhere between 0 (no probability of occurrence) and 1 (certain to occur) or on a scale (10 to 1 or High to Low).  For each risk, the product of Risk Impact and Risk Probability gives the Risk Magnitude. Sorting the Risk Magnitude in descending order gives a list in which the risks at the top are the more serious risks and need to be managed closely.
* '''Risk Treatment''' : Each risk in the risk list is subject to one or more of the following Risk Treatments.
*# <small>'''Risk Avoidance''' : For example, if there is a risk related to a new feature, it is possible to postpone this feature to a later release.</small>
*# <small>'''Risk Transfer''' : For example, if the risk is insufficient security testing of a feature, it may be possible to borrow the other expertise (Engineer) to perform the security testing.</small>
*# <small>'''Risk Mitigation''' : The objective of Risk Mitigation is to reduce the Risk Impact or Risk Probability or both. For example, if the QA team is new and does not have prior system knowledge, a risk mitigation treatment may be to have a knowledgeable team member join the team to train others on-the-fly.</small>
*# <small>'''Risk Acceptance''' : This happens when there is no viable mitigation available due to reasons such as resources. For example, if all testers are at the same place, risk acceptance means no another QA resource. When holiday comes, some tests will be stopped and it may be a concern in the project.</small>
= References =
* UX Specification : https://mozilla.invisionapp.com/share/4Y6ZZH1E8
* MANA : https://mana.mozilla.org/wiki/display/PM/Content+Handling+Enhancement
* QA test strategy: https://docs.google.com/document/d/1YK5ePlHa3QfvaVhF4eYy922CmAt1Hkw3cWbYaOZm9AI/edit?usp=sharing
* Meta: [https://bugzilla.mozilla.org/show_bug.cgi?id=1269956 Bug 1269956 [meta<nowiki>]</nowiki> Firefox Download Panel UX Redesign]
= Testcases =
== Overview ==
* Test cases on [https://docs.google.com/spreadsheets/d/1q7BWJkeRohs9CQ3TMaPDTTHoYFlB3ircbzrLo9s-eAw/edit?pref=2&pli=1#gid=906476437 Google doc]
  Note: UX spec is not yet finalized, and test cases are waiting for review.
        Therefore, test cases will be made public later. Sorry for any inconvenience!
== 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;" | NO ||
|-
| '''UI'''
||  ||
|-
| Mouse-only operation 
|style="text-align:center;" | YES ||
|-
| Keyboard-only operation 
|style="text-align:center;" | NO ||
|-
| Display (HiDPI)
|style="text-align:center;" | NO ||
|-
| Interraction (scroll, zoom)
|style="text-align:center;" | YES ||
|-
| Usable with a screen reader 
|style="text-align:center;"| N/A || e.g. with NVDA
|-
| Usability and/or discoverability testing 
|style="text-align:center;" | YES || UX team will help with it
|-
| '''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;" | N/A ||
|-
| Does sync work across upgrades 
|style="text-align:center;"| YES ||
|-
| Requires install testing   
|style="text-align:center;" | YES || separate feature/application installation needed (not only Firefox)
|-
| Affects first-run or onboarding   
|style="text-align:center;"| N/A ||
|-
| Does this affect partner builds? Partner build testing 
|style="text-align:center;"| N/A ||
|-
| ''' 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;"| N/A ||
|-
| Network proxies/autoconfig 
|style="text-align:center;"| N/A ||
|-
| ESR behavior changes 
|style="text-align:center;"| N/A ||
|-
| Locked preferences 
|style="text-align:center;"| N/A ||
|-
| ''' Data Monitoring '''
||  ||
|-
| Temporary or permanent telemetry monitoring 
|style="text-align:center;"| N/A || List of error conditions to monitor
|-
| Telemetry correctness testing 
|style="text-align:center;"| N/A ||
|-
| Server integration testing 
|style="text-align:center;"| N/A ||
|-
| Offline and server failure testing 
|style="text-align:center;"| N/A ||
|-
| Load testing 
|style="text-align:center;"| N/A ||
|-
| ''' 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;"| N/A ||
|-
| Comprehensive API testing 
|style="text-align:center;"| N/A ||
|-
| Permissions 
|style="text-align:center;" | YES ||
|-
| Testing with existing/popular addons
|style="text-align:center;" | YES ||
|-
| ''' 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;" | YES || Security team will help with it
|-
| Privilege escalation testing
|style="text-align:center;" | NO ||
|-
| Fuzzing 
|style="text-align:center;" | NO ||
|-
| ''' 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;" | NO ||
|-
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS 
|style="text-align:center;" | NO ||
|-
| Interaction of this feature with other browser features 
|style="text-align:center;" | NO ||
|}
== Test suite ==
Full Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1q7BWJkeRohs9CQ3TMaPDTTHoYFlB3ircbzrLo9s-eAw/edit#gid=906476437 link]
Smoke Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1q7BWJkeRohs9CQ3TMaPDTTHoYFlB3ircbzrLo9s-eAw/edit#gid=203870728 link]
Regression Test suite - Link with the gdoc - if available/needed.
= Bug Work =
Meta: [https://bugzilla.mozilla.org/show_bug.cgi?id=1269956 Bug 1269956 - [meta<nowiki>]</nowiki> Firefox Download Panel UX Redesign]
== Logged bugs ( blocking [https://bugzilla.mozilla.org/show_bug.cgi?id=1269956 1269956 ] ) ==
<bugzilla>
    {
        "blocks":[1269956],
        "include_fields": "id, priority, component, assigned_to, summary, status, target_milestone"
    }
</bugzilla>
== Bug Verification  (blocking [https://bugzilla.mozilla.org/show_bug.cgi?id=1269956 1269956 ]) ==
<bugzilla>
    {
        "blocks":[1269956],
        "resolution":"FIXED",
        "include_fields": "id, priority, component, assigned_to, summary, status, target_milestone"
    }
</bugzilla>
= 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 [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Full Test suite, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing 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;" | {{mprog|}}
| style="text-align:center;" |
|-
|  Testing Infrastructure setup
|style="text-align:center;" | NO ||
|-
|  Test Plan Creation
| style="text-align:center;" | {{mprog|}} ||
|-
|  Test Cases Creation
|style="text-align:center;" |  {{mprog|}} ||
|-
|  Full Functional Tests Execution
|style="text-align:center;" |  {{mnotstarted}}
|style="text-align:center;" | 
|-
|  Automation Coverage
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  Performance Testing
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  All Defects Logged
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  Critical/Blockers Fixed and Verified
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  Daily Status Report (email/etherpad statuses/ gdoc with results)
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  Metrics/Telemetry
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  QA Signoff  - Nightly Release
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  QA Aurora - Full Testing
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  QA Signoff  - Aurora Release
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  QA Beta - Full Testing
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|-
|  QA Signoff  - Beta Release
|style="text-align:center;" | {{mnotstarted}}
|style="text-align:center;" |
|}
|}
AdiFlorinescu
584

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1148571"

Navigation menu