QA/Browser Technologies: Difference between revisions
| (121 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
= | = <b><i>Browser Technologies QA Team </i></b> Overview= | ||
As mobile and Web Services become more prominent in the mozilla project, QA continues to strive to cover and test the projects forthcoming. The current projects with coverage include Mobile Firefox, Test Pilot, Firefox Sync, Jetpack, and Web API's | |||
=Team Details= | |||
The QA team of Web services and mobile, coordinates a various set of tasks from feature test development to release testing on different platforms. Since many of these groups are still under 2 years old, there are still developmental progress with automation support and conducted processes. In addition, there are some outsourced work that run nightly smoketests and bug verifications on an ongoing basis. | |||
==Team== | |||
{{:QA/Browser_Technologies/Team}} | |||
* [[QA/Browser_Technologies/2010-07- | == Team Pages == | ||
{| class="fullwidth-table" | |||
|- | |||
| style="background:#EFEFEF; | '''Team''' | |||
| style="background:#EFEFEF; | '''Homepage''' | |||
|- | |||
| Mobile QA | |||
| [https://wiki.mozilla.org/QA/Fennec https://wiki.mozilla.org/QA/Fennec/NativeUI] | |||
|- | |||
| Services QA | |||
| [https://wiki.mozilla.org/QA/Browser_Technologies/Services https://wiki.mozilla.org/QA/Browser_Technologies/Services] | |||
|- | |||
| Web API QA | |||
| [https://wiki.mozilla.org/QA/Browser_Technologies/WebAPI https://wiki.mozilla.org/QA/Browser_Technologies/WebAPI] | |||
|} | |||
=Status= | |||
* Fennec (Firefox): 6.0 (android) targeting release 3rd week of August 2011 | |||
* Firefox Sync: -- | |||
* Test Pilot: -- | |||
* Jetpack: -- | |||
* Firefox Home: -- | |||
=Calendar= | |||
* Browser Technologies QA [http://www.google.com/calendar/embed?src=m42o9ivukgvpn17bvalf4iv0mk%40group.calendar.google.com&ctz=America/Los_Angeles Events & Meetings Calendar] | |||
=Meetings= | |||
Bi-Monthly Status Meetings | |||
Dial In: 800-707-2533 (pin 369) Conf #265 | |||
Every other Thursday at 11:00 AM Pacific/ 02:00 PM Eastern / 18:00 PM UTC | |||
Zombocom Conference Room (3rd Floor) | |||
[irc://irc.mozilla.org/planning irc.mozilla.org #qa] for backchannel | |||
* [[QA/Browser_Technologies/LastMeeting| Last Meeting]] | |||
* [[QA/Browser_Technologies/NextMeeting| Next Meeting]] | |||
* [[QA/Browser_Technologies/Meeting-Template|Meeting Template]] | |||
{| class="wikitable collapsible" style="width: 100%" | |||
! 2012 | |||
|- | |||
| | |||
* [[QA/Browser_Technologies/2012-04-05|2012-04-05]] | |||
* [[QA/Browser_Technologies/2012-03-22|2012-03-22]] | |||
* [[QA/Browser_Technologies/2012-03-08|2012-03-08]] | |||
* [[QA/Browser_Technologies/2012-02-23|2012-02-23]] | |||
* [[QA/Browser_Technologies/2012-01-26|2012-01-26]] | |||
|} | |||
{| class="wikitable collapsible collapsed" style="width: 100%" | |||
! 2011 | |||
|- | |||
| | |||
* [[QA/Browser_Technologies/Meetings/2011-12-13|2012-01-24 (Mobile Only)]] | |||
* [[QA/Browser_Technologies/Meetings/2011-12-13|2011-12-13 (Mobile Only)]] | |||
* [[QA/Browser_Technologies/2011-12-01|2011-12-01]] | |||
* [[QA/Browser_Technologies/Meetings/2011-11-29|2011-11-29 (Mobile Only)]] | |||
* [[QA/Browser_Technologies/2011-11-17|2011-11-17]] | |||
* [[QA/Browser_Technologies/2011-11-15|2011-11-15 (Mobile Only)]] | |||
* [[QA/Browser_Technologies/2011-11-03|2011-11-03]] | |||
* [[QA/Browser_Technologies/2011-11-01|2011-11-01 (Mobile Only)]] | |||
* <strike>2011-10-20 No Meeting</strike> | |||
* [[QA/Browser_Technologies/2011-10-06|2011-10-06]] | |||
* [[QA/Browser_Technologies/2011-08-25|2011-08-25]] | |||
* [[QA/Browser_Technologies/2011-08-11|2011-08-11]] | |||
* [[QA/Browser_Technologies/2011-07-28|2011-07-28]] | |||
* [[QA/Browser_Technologies/JulyWorkWeek2011|July Work Week 2011]] | |||
* [[QA/Browser_Technologies/2011-07-14|2011-07-14]] | |||
* [[QA/Browser_Technologies/2011-06-30|2011-06-30]] | |||
* [[QA/Browser_Technologies/2011-06-16|2011-06-16]] | |||
* <strike>2011-06-02 No Meeting</strike> | |||
* [[QA/Browser_Technologies/2011-05-19|2011-05-19]] | |||
* <strike>2011-05-05 No Meeting</strike> | |||
* [[QA/Browser_Technologies/2011-04-21|2011-04-21]] | |||
* [[QA/Browser_Technologies/2011-03-10|2011-03-24]] | |||
* [[QA/Browser_Technologies/2011-03-10|2011-03-10]] | |||
* [[QA/Browser_Technologies/2011-02-24|2011-02-24]] | |||
* [[QA/Browser_Technologies/2011-02-10|2011-02-10]] | |||
* [[QA/Browser_Technologies/2011-01-27|2011-01-27]] | |||
* [[QA/Browser_Technologies/2011-01-13|2011-01-13]] | |||
|} | |||
{| class="wikitable collapsible collapsed" style="width: 100%" | |||
! 2010 | |||
|- | |||
| | |||
* [[QA/Browser_Technologies/2010-12-16|2010-12-16]] | |||
* [[QA/Browser_Technologies/2010-12-02|2010-12-02]] | |||
* [[QA/Browser_Technologies/2010-11-18|2010-11-18]] | |||
* [[QA/Browser_Technologies/2010-11-04|2010-11-04]] | |||
* [[QA/Browser_Technologies/2010-10-07|2010-10-07]] | |||
* [[QA/Browser_Technologies/2010-09-23|2010-09-23]] | |||
* [[QA/Browser_Technologies/2010-09-09|2010-09-09]] | |||
* [[QA/Browser_Technologies/2010-08-26|2010-08-26]] | |||
* [[QA/Browser_Technologies/2010-08-12|2010-08-12]] | |||
* [[QA/Browser_Technologies/2010-07-29|2010-07-29]] | * [[QA/Browser_Technologies/2010-07-29|2010-07-29]] | ||
* [[QA/Browser_Technologies/2010-07-15|2010-07-15]] | * [[QA/Browser_Technologies/2010-07-15|2010-07-15]] | ||
| Line 24: | Line 112: | ||
* [[QA/Browser_Technologies/2010-05-06|2010-05-06]] | * [[QA/Browser_Technologies/2010-05-06|2010-05-06]] | ||
* [[QA/Browser_Technologies/2010-04-22|2010-04-22]] | * [[QA/Browser_Technologies/2010-04-22|2010-04-22]] | ||
|} | |||
=Team Goals= | |||
* [https://intranet.mozilla.org/QA/Q42011_QAgoals#Browser_Technology_QA_Goals Q4 2011] | |||
* [https://intranet.mozilla.org/QA/Q32011_QAgoals#Browser_Technology_QA_Goals Q3 2011] | |||
* [https://intranet.mozilla.org/QA/Q22011_QAgoals#Browser_Technology_QA_Goals Q2 2011] | |||
* [https://intranet.mozilla.org/QA/Q12011_QAgoals#Browser_Technology_QA_Goals Q1 2011] | |||
= | =Current Projects= | ||
<onlyinclude> | |||
This section should contain a list to the active current team project page. The section will be included as part of the top level QA organization page. | |||
; | {| class="fullwidth-table" | ||
| style="background:#EFEFEF; width:33%" | '''Project''' | |||
| style="background:#EFEFEF; width:66%" | '''Description''' | |||
|- valign="top" | |||
|[[QA/Fennec/Milestones/10.0| Fennec 10.0 Test Plan]] | |||
|Mobile Firefox QA site summarizing Test Strategy, Feature set, assignments, Milestone Testplans, and schedules | |||
|- | |||
|[[QA/Weave_Test_Plan| Firefox Sync Test Plan]] | |||
|Firefox Sync site (both extension and Integrated feature) summarizing Test strategy, testcases, Milestone testplans, and schedules | |||
|- | |||
|[[QA/Test_Pilot_Test_Plan| Test Pilot Test Plan]] | |||
|Test Pilot QA site summarizing Test strategy, testcases, Milestone testplans, and schedules | |||
|- | |||
|[[QA/Jetpack| Jetpack Test Plan]] | |||
|Jetpack QA site summarizing Test strategy, testcases, Milestone testplans, and schedules | |||
|- | |||
|[https://wiki.mozilla.org/Home/Features/qaplan| Firefox Home 2 Test Plan] | |||
|Firefox Home 2 (aka Iphone Sync App) site summarizing Test strategy, testcases, Milestone testplans, and schedules | |||
|- | |||
|[xxx|Web APIs Test Plans] | |||
|Web APIs home page summarizing test pages to support upcoming APIs for mobile | |||
|} | |||
</onlyinclude> | |||
= Evolving Projects = | |||
This section should contain a list of Upcoming Projects across different teams. | |||
===Fennec=== | ===Fennec=== | ||
{| class="fullwidth-table" | |||
|- | |||
| style="background:#EFEFEF; width:33%" | '''Project''' | |||
| style="background:#EFEFEF; width:66%" | '''Description''' | |||
|- valign="top" | |||
| [https://spreadsheets.google.com/ccc?key=0AhE7m4JB2j6tdEJFZ3NoZkRoRTM3TTRpQll3UjZLYnc&hl=en&authkey=CPiPp9IK#gid=4 Device Compatibility Test Plan] | |||
| Tracks Tests and Full device list of compatibility with Mobile Firefox | |||
|- | |||
=== | | [[QA/Fennec/NativeUI/WebsiteCompatibility|Website Compatibility Test Plan]] | ||
| Tracks top Website compatibility with Mobile Firefox | |||
|- | |||
| [https://spreadsheets.google.com/ccc?key=0AocUyLHteCtSdDJrNkZFaE1kUktlUGItRktJXzB5ZVE&hl=en&authkey=CLz_9McK#gid=1 Performance Benchmarking Test Plan] | |||
| Tracking performance benchmarking numbers for Startup times and Page Loads | |||
|- | |||
| [https://wiki.mozilla.org/QA/Browser_Technologies/Mobile_Unit_Testing_Addon Mobile Addon for Unit Testing Automation] | |||
| Project to run unit tests via a test-harness addon and disperse via crowdsourcing techniques | |||
|} | |||
===Jetpack=== | ===Jetpack=== | ||
===Test | {| class="fullwidth-table" | ||
|- | |||
| style="background:#EFEFEF; width:33%" | '''Project''' | |||
| style="background:#EFEFEF; width:66%" | '''Description''' | |||
|- valign="top" | |||
| [[QA/Jetpack|Selenium 2 Automation For Addons Builder Test Plan]] | |||
| Creating Selenium 2 Automation tests for Addons Builder | |||
|} | |||
=Community Contribution= | |||
'''Anyone can participate.''' There are several ways in which '''YOU''' can participate: | |||
* File bugs | |||
* Triage bugs (confirm existing bugs and assign them to the right buckets) | |||
* Help test new features | |||
* Write test cases | |||
* Plan new features testing | |||
* Help others who want to get involved. | |||
=== | =Resources= | ||
==== Reference Links ==== | |||
add links to pertinent wiki pages, blogs, dev project pages, internet sites etc. If team has a number of projects, then it may be more appropriate to list reference links that are specific to the project in the project page itself. | |||
==== Documentation ==== | |||
add link to any permanent documentation for the team or projects | |||
*Mobile | |||
** [https://wiki.mozilla.org/QA_SoftVision_Team/Mobile documentation for ramp up and possible tasks] | |||
Latest revision as of 23:14, 28 March 2013
Browser Technologies QA Team Overview
As mobile and Web Services become more prominent in the mozilla project, QA continues to strive to cover and test the projects forthcoming. The current projects with coverage include Mobile Firefox, Test Pilot, Firefox Sync, Jetpack, and Web API's
Team Details
The QA team of Web services and mobile, coordinates a various set of tasks from feature test development to release testing on different platforms. Since many of these groups are still under 2 years old, there are still developmental progress with automation support and conducted processes. In addition, there are some outsourced work that run nightly smoketests and bug verifications on an ongoing basis.
Team
The Browser Technologies mission is two-fold, we aim to improve the quality of Firefox and finely tune it for mobile devices as well as drive the testing efforts for all the Mozilla Labs projects, web services and web apps. As Mobile, Web Services, Labs, and Web Apps become more prominent in the Mozilla project, QA continues to strive to cover and test the projects forthcoming.
| Photo | Name | Location | IRC |
| Aaron Train atrain@mozilla.com |
Canada | AaronMT #mobile | |
| Tony Chung | United States | tchung #qa, #sync, #mobile, #openwebapps | |
| Tracy Walker | United States | tracy #qa, #sync, #labs | |
| Owen Coutts | United States | ocoutts #qa, #sync, #mozmill, #interns | |
|
John Hammink | United States | jhammink #qa, #webapi, #b2g |
| Kevin Brosnan | United States | kbrosnan #mobile | |
| Martijn Wargers | Netherlands | mw22 #mobile, #qa, #developers | |
|
Naoki Hirata | United States | nhirata #mobile, #qa, #fxhome |
| John Morrison | United States | jrgm #qa, #sync, #identity |
Team Pages
| Team | Homepage |
| Mobile QA | https://wiki.mozilla.org/QA/Fennec/NativeUI |
| Services QA | https://wiki.mozilla.org/QA/Browser_Technologies/Services |
| Web API QA | https://wiki.mozilla.org/QA/Browser_Technologies/WebAPI |
Status
- Fennec (Firefox): 6.0 (android) targeting release 3rd week of August 2011
- Firefox Sync: --
- Test Pilot: --
- Jetpack: --
- Firefox Home: --
Calendar
- Browser Technologies QA Events & Meetings Calendar
Meetings
Bi-Monthly Status Meetings
Dial In: 800-707-2533 (pin 369) Conf #265 Every other Thursday at 11:00 AM Pacific/ 02:00 PM Eastern / 18:00 PM UTC Zombocom Conference Room (3rd Floor) irc.mozilla.org #qa for backchannel
| 2012 |
|---|
| 2011 |
|---|
|
| 2010 |
|---|
Team Goals
Current Projects
This section should contain a list to the active current team project page. The section will be included as part of the top level QA organization page.
| Project | Description |
| Fennec 10.0 Test Plan | Mobile Firefox QA site summarizing Test Strategy, Feature set, assignments, Milestone Testplans, and schedules |
| Firefox Sync Test Plan | Firefox Sync site (both extension and Integrated feature) summarizing Test strategy, testcases, Milestone testplans, and schedules |
| Test Pilot Test Plan | Test Pilot QA site summarizing Test strategy, testcases, Milestone testplans, and schedules |
| Jetpack Test Plan | Jetpack QA site summarizing Test strategy, testcases, Milestone testplans, and schedules |
| Firefox Home 2 Test Plan] | Firefox Home 2 (aka Iphone Sync App) site summarizing Test strategy, testcases, Milestone testplans, and schedules |
| Web APIs Test Plans] | Web APIs home page summarizing test pages to support upcoming APIs for mobile |
Evolving Projects
This section should contain a list of Upcoming Projects across different teams.
Fennec
| Project | Description |
| Device Compatibility Test Plan | Tracks Tests and Full device list of compatibility with Mobile Firefox |
| Website Compatibility Test Plan | Tracks top Website compatibility with Mobile Firefox |
| Performance Benchmarking Test Plan | Tracking performance benchmarking numbers for Startup times and Page Loads |
| Mobile Addon for Unit Testing Automation | Project to run unit tests via a test-harness addon and disperse via crowdsourcing techniques |
Jetpack
| Project | Description |
| Selenium 2 Automation For Addons Builder Test Plan | Creating Selenium 2 Automation tests for Addons Builder |
Community Contribution
Anyone can participate. There are several ways in which YOU can participate:
- File bugs
- Triage bugs (confirm existing bugs and assign them to the right buckets)
- Help test new features
- Write test cases
- Plan new features testing
- Help others who want to get involved.
Resources
Reference Links
add links to pertinent wiki pages, blogs, dev project pages, internet sites etc. If team has a number of projects, then it may be more appropriate to list reference links that are specific to the project in the project page itself.
Documentation
add link to any permanent documentation for the team or projects
