38
edits
Compatibility/Test Plan: Difference between revisions
Jump to navigation
Jump to search
update
(→Environment: Added Android version) |
(update) |
||
| Line 12: | Line 12: | ||
=== Overall Status === | === Overall Status === | ||
[LANDED] [[Compatibility/Mobile_Testing_Surveys#US|US]], [[Compatibility/Mobile_Testing_Surveys#France|France]] | [LANDED] [[Compatibility/Mobile_Testing_Surveys#US|US]], [[Compatibility/Mobile_Testing_Surveys#France|France]], [[Compatibility/Mobile_Testing_Surveys#India|India]] | ||
[NOT LANDED] | [NOT LANDED] [[Compatibility/Mobile_Testing_Surveys#Germany|Germany]], [[Compatibility/Mobile_Testing_Surveys#Taiwan|Taiwan]], [[Compatibility/Mobile_Testing_Surveys#Indonesia|Indonesia]], [[Compatibility/Mobile_Testing_Surveys#Hong_Kong|Hong Kong]], [[Compatibility/Mobile_Testing_Surveys#Singapore|Singapore]], [[Compatibility/Mobile_Testing_Surveys#Poland|Poland]], [[Compatibility/Mobile_Testing_Surveys#UK|UK]], [[Compatibility/Mobile_Testing_Surveys#Russia|Russia]] | ||
== Testing Summary == | == Testing Summary == | ||
| Line 24: | Line 24: | ||
Testing will be performed on following: | Testing will be performed on following: | ||
* Android devices: Phone: | * Android devices: Phone: 7.x | ||
* Browser: Firefox Nightly, Release and Chrome | * Browser: Firefox Nightly, Release and Chrome | ||
=== Specifications === | === Specifications === | ||
* QA Engineering team will run Exploratory and Web Compatibility testing on a single OS/Platform (Android | * QA Engineering team will run Exploratory and Web Compatibility testing on a single OS/Platform (Android 7.x or above for Android client). | ||
* The focus will be towards the latest official OS on the market. | * The focus will be towards the latest official OS on the market. | ||
* By Exploratory testing we understand “An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests”. | * By Exploratory testing we understand “An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests”. | ||
| Line 39: | Line 39: | ||
Any issues that fall into one or more of the following categories: | Any issues that fall into one or more of the following categories: | ||
* "Desktop site instead of mobile site" | * "Desktop site instead of mobile site" | ||
* " | * "Site is not usable" | ||
* "Video doesn't play | * "Design is broken" | ||
* "Video or audio doesn't play" | |||
Or any other issue observed, will be logged using the webcompat.com form and the test will be considered FAIL. | Or any other issue observed, will be logged using the webcompat.com form and the test will be considered FAIL. | ||