|
|
| Line 170: |
Line 170: |
| |- | | |- |
| | Private Window | | | Private Window |
| |style="text-align:center;" | || | | |style="text-align:center;" | || Certain test are performed in a private window |
| |- | | |- |
| | Multi-Process Enabled | | | Multi-Process Enabled |
| |style="text-align:center;" | || | | |style="text-align:center;" | || Enabled by default |
| |- | | |- |
| | Multi-process Disabled | | | Multi-process Disabled |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |-
| |
| | Theme (high contrast)
| |
| |style="text-align:center;" | ||
| |
| |- | | |- |
| | '''UI''' | | | '''UI''' |
| Line 185: |
Line 182: |
| |- | | |- |
| | Mouse-only operation | | | Mouse-only operation |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |- | | |- |
| | Keyboard-only operation | | | Keyboard-only operation |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |- | | |- |
| | Display (HiDPI) | | | Display (HiDPI) |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |- | | |- |
| | Interaction (scroll, zoom) | | | Interaction (scroll, zoom) |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |-
| |
| | 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''' |
| Line 213: |
Line 201: |
| | Support documents planned(written) | | | Support documents planned(written) |
| |style="text-align:center;" | || Make sure support documents are written and are correct. | | |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 ''' | | | ''' 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. | | || || 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 | | | Permissions |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |-
| |
| | 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 ''' | | | ''' Web Compatibility ''' |
| Line 302: |
Line 214: |
| |- | | |- |
| | Testing against target sites | | | Testing against target sites |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| |- | | |- |
| | Survey of many sites for compatibility | | | Survey of many sites for compatibility |
| |style="text-align:center;" | || | | |style="text-align:center;" | || To be tested |
| | |
| |-
| |
| | ''' 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;" | ||
| |
| |} | | |} |
|
| |
|