Welcome to the SV Mobile Team wiki page.
This page is considered a ramp up page and gives a centralization of our tasks. Please contact one of us before changing the content of the page.
This page is considered a ramp up page and gives a centralization of our tasks. Please contact one of us before changing the content of the page.
Contents
MANAGEMENT AND COMMUNICATION
Project Updates
Hot Projects
Meetings
IRC
Mailing Lists
- firefox-qe@mozilla.com
- dev-quality@mozilla.com
- dev-platform@mozilla.com
Blogs
- most contributers have blogs and a lot of information can be found out by watching these blogs
- list of most important blogs:
- Planet Mozilla – http://planet.mozilla.org
- QMO Community - http://quality.mozilla.org/community
- QMO News - http://quality.mozilla.org/category/qmo-news/
- Planet Firefox - http://planet.firefox.com/
REGULAR CYCLE QA FENNEC TEAM SCHEDULING
Day/Week | Monday | Tuesday | Wednesday | Thursday | Friday |
---|---|---|---|---|---|
Week 1 | Merge day RC testing if needed General tasks |
Beta 1 testing - sign-off | Aurora Sign Off Nightly - first look |
Aurora Sign Off | General tasks Aurora new features sign-offs |
Week 2 | General tasks | Beta 2 testing - sign-off | General tasks | General tasks | General tasks |
Week 3 | General tasks | Beta 4 testing - sign-off (Day 1 of testing) | Beta 4 testing - sign-off (Day 2 of testing) | General tasks | General tasks |
Week 4 | General tasks | Beta 6 testing - sign-off | General tasks | General tasks | General tasks |
Week 5 | General tasks | Beta 8 testing - sign-off | General tasks | General tasks | General tasks |
Week 6 | General tasks | Beta 10 testing - sign-off | General tasks | RC testing - sign-off | General tasks |
BETA TESTING DETAILS
1. Beta 1 & 8 testing (week 1 & 5)
- Process and documents
- Create the Testplan and test runs for the current beta build
- Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 2 x ARMv7 phone API 11, 1 x ARMv7 phone API 9 and x86 phone
Testing Matrix:
Device | ARMv7 tablet | ARMv7 phone API 11 | ARMv7 phone API 9 | x86 |
---|---|---|---|---|
Phone | N/A | 2 phones | 1 phone | 1 phone |
Tablet | 2 tablets | N/A | N/A | N/A |
- Check Android Permissions - ARMv7 tablet, phone and x86
- Bug Verification - verify all introduced fixes
- L10 Spot Check - check that the main parts of the app are localized
- Run Appthwack - API 11
2. Beta 2,6,10 testing (week 2,4,6)
- Process and documents
- Create the Testplan and test runs for the current beta build
- Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 2 x ARMv7 phone API 11, 1 x ARMv7 phone API 9 and x86 phone
- Check Android Permissions - ARMv7 tablet, phone and x86
- Bug Verification - verify all introduced fixes
- L10 Spot Check - check that the main parts of the app are localized
- Results Beta 2
- Results Beta 6
- Results Beta 10
3. Beta 4 testing (week 3)
- Process and documents
- Fennec Features tracking
- Create the Testplan and test runs for the current beta build
- Run Smoketests - basic functions covered - 1 x ARMv7 tablet, 1 x ARMv7 phone API 11, 1 x ARMv7 phone API 9, and x86 phone
- Check Android Permissions - ARMv7 tablet, phone and x86
- Bug Verification - verify all introduced fixes
- L10 Spoot Check - check that the main parts of the app are localized
- Run Appthwack - API 11
- Run BFTs - all features tests covered
- Results Beta 4
3. Beta features sign-off (week 5)
- Process and documents
- Feature owners monitor new fixes + perform additional testing (weeks 1 -> 5)
- Feature owners analyze remaining issues and do a final assessment on quality of the Beta features
- Feature owners send final sign-off email for Beta features to dev leads & Kairo & Lawrence? (Friday week 5 or Monday week 6 latest)
4. Aurora Signoff (week 1)
- Process and documents
- Create the Testplan and test runs for the current beta build
- Run Smoketests - basic functions covered - 1 x ARMv7 tablet, 1 x ARMv7 phone API 11, 1 x ARMv7 phone API 9, and x86 phone
- Check Android Permissions - ARMv7 tablet, phone and x86
- Bug Verification - verify all introduced fixes
- L10 Spot Check - check that the main parts of the app are localized
- Run Appthwack - API 11
- Run BFTs - all features tests covered
- Results Beta 4
5. Release Candidate (week 6)
- Process and documents
- Create the Testplan and test runs for the current beta build
- Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 3 x ARMv7 phone and x86 phone
- Check Android Permissions - ARMv7 tablet, phone and x86
- Bug Verification - verify all introduced fixes
- L10 Spot Check - check that the main parts of the app are localized
- Run Appthwack - API 11
- Results RC
GENERAL TASKS DETAILS
1. Bug Verification
- Branches: Nightly, Aurora, Beta
2. Bug Investigations
- NI/ Regression Window wanted
3. Bug Triage
4. Feature testing
- Channel
- Nightly - https://wiki.mozilla.org/QA/Fennec/42
- Nightly - Draft documentation is created and Exploratory is performed to shake out most bugs
- Aurora - https://wiki.mozilla.org/QA/Fennec/41
- Aurora - Test Plan is created, Test Cases are created and Run
- Beta - https://wiki.mozilla.org/QA/Fennec/40
- Beta - Bug Verification for additional fixes, and final Exploratory/Regression testing
- Nightly - https://wiki.mozilla.org/QA/Fennec/42
- Owners are assigned to each feature as early as possible
- Owners are responsible for testing and signing off on their features
5. Component Watch
- Major components split among team members
- Owners will cover: triage of new Unconfirmed bugs, investigation of bugs, and verification of fixes in certain area
- Considered a lower priority area with not much time spent on it
6. SmokeTesting & Exploratory
- Nightly
- Aurora
Automation using Robocop
- Robocop is a java based testing framework. Robocop is an extention of the Android Robotium test tool with features needed to perform automation on Firefox for Android builds.
- Here is a small walktrough to setup the enviroment and start running the automated tests
- Resources where you can read more about how to set up the enviroments, run and create automated tests using Robocop:
- Here is some information about writing Robocop tests.
- Here is a set of guidelines that need to be followed in order to receive a positive review on a patch
- Here is a quick guide in setting up a pandaboard in order to run automation on it