B2G/QA/Device Test Plan/NewOEMBuild
From MozillaWiki
< B2G | QA | Device Test Plan
Contents
Test Plan
Introduction
This test plan is a test plan for testing new devices and some of the things to look out for. This is a guideline; there may be more to test depending on the feature of the phone.
Design Documentation/Background Research
Listed are the related documentation for testing:
Module Owners
- List of Firefox OS Modules/Dev Owners (link) - in case you need to ask questions regarding the new features of the component.
- Firefox OS functional teams breakdown (link)
- QA owners for Firefox OS components (link)
Requirements:
Specs:
Tips and Tricks for testing:
- https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks
- https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler
OS Diagrams
Schedule Milestones
Hardware Requirements
- A desktop machine capable of running ADB is necessary for testing for getting debug information and flash the device.
- Mobile device
- OEM Build
Mobile Device
- New Device
- New OEM build
Software Requirements
- ADB
- OEM Flashing tool and Driver
- OS to support OEM Flashing tool and driver
Strategy
- smoke test testing
- target testing for interface between hardware and software
- Exploratory testing
- Crash Report Testing
Test Deliverables / Deliverables
OEM build to build; blob to send to releng/dev to update
- The backup folder is tar/xz'ed and then placed behind a password protected file server to hand off to releng. A bug is created and the sha512 is included in the bug: Ex:
- tar cvf backup-leo.tar backup-leo
- xz -ze backup-leo.tar
- openssl dgst -sha512 <Path/to/file>
Dependencies/Risk
We are in the hands of the vendor in order to have vendor fixes.
OEM Build Testing
- Run through : https://wiki.mozilla.org/B2G/QA/Device_Test_Plan/NewDevice
- Verify : Crash Reporter
- Run through smoke testing
Build w/ Blob
- pull blob (not all devices need to do this. Nexus devices does not )
- clone the B2G repo : git clone https://github.com/mozilla-b2g/B2G.git b2g
- configure the B2G repo : ./config.sh tarako
- adb root
- adb remount
- cd b2g/device/qcom/<device code name>/
- see various devices : https://github.com/mozilla-b2g?query=device-
- sudo ./extract-files.sh
- cd ../../../
- sudo chown -R <user> backup-<device code name>
Note: I found that sometimes without the proper permissions on both ends not all the files will get pulled.
- build with blob
- get back to the b2g project directory
- git pull
- ./repo sync
- ./build.sh -j1
- ./flash.sh
- Run through : https://wiki.mozilla.org/B2G/QA/Device_Test_Plan/NewDevice
- Verify : Crash Reporter
- Run through smoke testing
Signoff/Exit Criteria
No major bugs that are on the vendor side.