B2G/QA/Gaia Test Plan/Template

1. Introduction 1.1 Purpose: See https://wiki.mozilla.org/Gaia/Clock

�

2. Resource Plan 2.1 People on Project

Role Owner Dev refer to : https://wiki.mozilla.org/Modules/FirefoxOS QA refer to : https://wiki.mozilla.org/B2G/QA_Overview#Team_Members UX see https://wiki.mozilla.org/Gaia/UXTeam

2.2 HW/SW Specification/Requirements: HW: Testing will be conducted on the Aries (Sony Compact Z3C) and the Flame device. Headphones; 2 and 3 prong types : see https://en.wikipedia.org/wiki/Phone_connector_%28audio%29#TRRS_standards Headphones; bluetooth w/ AVRCP : https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Audio.2FVideo_Remote_Control_Profile_.28AVRCP.29

� 3. Test Strategy 3.1 Major Test Area Strategy: Unit test Dev driven : https://github.com/mozilla-b2g/gaia/tree/master/apps/clock/test/unit Smoke test https://moztrap.mozilla.org/manage/cases/?filter-suite=241 ( Done daily) Specific smoke tests : https://moztrap.mozilla.org/manage/case/1772/ Manual Functionality test https://moztrap.mozilla.org/manage/cases/?filter-suite=684 Exploratory testing : <mapping link> Test cases based on ACC Automation Integration test https://github.com/mozilla-b2g/gaia/tree/master/apps/clock/test/marionette Automation End-to-end tests https://github.com/mozilla-b2g/gaia/tree/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/clock Security test : security team does the testing : https://wiki.mozilla.org/Security/Reviews/Gaia/clock Stress test : No current stress test Possible to add to MTBF : https://wiki.mozilla.org/QA/Automation/Projects/MTBF https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Automated_testing/MTBF_tests Performance test Raptor testing https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Automated_testing/Raptor dashboard : https://raptor.mozilla.org/ l10n test RTL : https://moztrap.mozilla.org/manage/cases/?filter-suite=974 3.2 Test Deliverables: Test Cases Outcome of test case runs: Maybe wiki the test run and have a link in the email and paste in here? 3.3 Dependencies/Risk: dependencies on SNTP (default settings) : http://mxr.mozilla.org/mozilla-central/source/b2g/app/b2g.js#928 possibly with QC’s XPCOM for some QC hardware; May need to configure QC file dependencies on settings app dependencies on system clock 3.5 Scope: In scope: clock application and interactions with the system. Out of scope : underwater testing 3.4 Signoff/Exit Criteria: zero blocker bugs for 2.6 ui-review + 4. References 4.1 Repositories: Gaia : https://github.com/mozilla-b2g/gaia/tree/master/apps/clock 4.2 Bugs tracking features: No new features in 2.6 4.3 Specs/Design Diagrams: https://mozilla.app.box.com/applications/1/864504610 4.4 Scrum : No scrum for Clock 4.5 Meeting Notes: No meetings for Clock 4.6 Supplemental Documentation 4.6.1 Terminology 4.7 Project Schedule https://wiki.mozilla.org/Firefox_OS/Releases/2.6 4.8 Test Outline https://public.etherpad-mozilla.org/p/test-outline-clock 4.9 Test Cases 4.9.1 Clock ACC Matrix https://docs.google.com/spreadsheets/d/1Tk8xW2oT9qvs5cFXf5XMGnEnWDAmgKINtWJU_USpRNo/edit#gid=0

4.9.2 Moztrap Test Cases https://moztrap.mozilla.org/manage/cases/?filter-suite=684

5. Glossary: