Apps/QA: Difference between revisions

Revision as of 19:49, 27 January 2012

Overview

Purpose of this page is to provide a level of communication / information flow across the different QA Teams to allow for the testing of the HTML5 Web Store. The purpose of this page is not to explain QA team structure, provide status or provide a background into HTML5 web apps in general.


QA Lead	David Clarke
QA Automation:	Henrik Skupin
QA Mobile:	Aaron Train, James Bonacci
QA MarketPlace:	Zac Campbell, Krupa Raj, Marlena Compton
QA OWA Extension:	Jason Smith

General Purpose Docs:
Open Web Apps User Study

Meeting Notes

Deprecated

https://mozqa.sync.in/apps-qa-2011

Meetings

Dial in

 # 650-903-0800 or 650-215-1282 x92 Conf# 315 (US/INTL)
 # 1-800-707-2533 (pin 369) Conf# 315 (US)
 # irc.mozilla.org #qa for backchannel
 # Vidyo Room: WarpCore

The Open WebApps QA meeting is being held each monday morning. For notes of previous meetings please check the references below:

2011

Q4/11

Project	Lead QA	Status QA	Q4 Plan
MarketPlace OWA	Krupa Raj	on track / blocked / at risk	QA/Marketplace
Native Install Android	Aaron Train	In Progress	Native Install Android
OWA Extension	Mohamed Dabbagh	on track / blocked / at risk	QA/Extension
HTML5 Shim	David Clarke	on track / blocked / at risk	QA/Quarterly_Plan

The plan for Q4 is to deliver an app infrastructure capable of supporting 10's of thousands of users. We aim to do this by executing on the following concepts.

Test Reuse across the different software delivery platforms. Meaning unit tests should run across firefox+extension, ie (9/10), chrome, firefox.
Market Place testing will be purely selenium based, and will execute test cases across Android Devices as well as the desktop.
Android Native Application will most likely be a manual effort, but we will work towards devising a strategy that makes sense as time permits.
Load Testing. The relevant pieces of the platform that need to be tested are the following: WebApps Web Service, Receipt Verification, App Sync Service. * There is a need to verify browserid can handle the load.
Mozmill Automation across desktop. This is an easy win for reliability, but still requires a fair amount of work to get a set of tests written / shared API's etc.

Sprint 1.

Need experts in writing mozmill tests, so we can focus on other parts of the infrastructure
Need to have clear goals from the QA Leads as how we intend to execute on the company strategy.

Android Testing: On Hold until software delivery.

Exploration into load testing.
1. Investigate tool set required for the driving / reporting of load within our test infrastructure.
2. Any ability to cache images

Q3/11

Goal for Q3 is to release a 1.0 version of the HTML5 Web Apps Store. There are a few different products that will be shipping simultaneously, but there will be some that can be tested separately.

Project	Lead Developer	Spec Reviewed	When can we begin testing?	Test Strategy
MarketPlace OWA	Wil Clouser	No	09/??/2011	MarketPlace
Native Install Android	Anant Narayanan	No	End of October 2011	Native Install Android
Dashboards	Dan Walkowski	Yes	9/??/2011	Dashboards
OWA Extension	Anant, Shane, (Mike Hanson)	No	09/??/2011	OWA Extension
WebAPI's	Ian Bicking / Mike Hanson	No	Continuous Change / Integration	OWA WebAPI

Community

What is cool about WebApps ?

 This is the latest and greatest web technologies on the market.  
 The development team is delivering a mind blowing experience, and we are hoping to do the same in QA

How do I get involved ?

 Well join up in irc #openwebapps, or #automation.  
 Contact myself dclarke@mozilla.com

Where do we need help ?

 Everywhere.  :) 
 Manual Testing, Automation (mobile, desktop), Javascript

Technologies we are running with ?

 Javascript, HTML5, Mozmill, Selenium, Jstestnet, Doctestjs.  
 If you are looking to help out, improve your skills. 
 Feel free to contact and we will get you dialed into the project.

Bugs

Relevant Bugzilla Queries / Tracking Bugs

Architecture

Legend

Client possibly initiates a browserID session
1. Client goes to the marketplace, and a browserid login is presented
Client goes to the marketplace
Client initiates an install off an app
1. Navigator.mozApps.install
App is installed, user opens app
Twitter app is launched
Twitter app verifies the receipt that was presented.
Apps Sync occurs ad-hoc manner, still unsure as to the schedule.

The basics behind open webapps architecture is to allow for HTML5 apps to flourish. To do that a few things infrastructure pieces need to be in place.

Firefox needs to support navigator.mozApps
HTML5 App Managmement in case no OWA Extension is installed.
Store needs to support both the issuing of payment receipts as well as the verification of receipt information
Apps Need to be able to run from the desktop or in browser.
The navigator.mozApps is the javascript object that will manage installing / removing apps
Iframes are used to manage the communication channel between the Application Repo and the Dashboard
Application Sync is managed through a separate API.

References

Apps/Architecture

Revision as of 19:48, 27 January 2012 (view source) Jsmith (talk \| contribs) No edit summary ← Older edit		Revision as of 19:49, 27 January 2012 (view source) Jsmith (talk \| contribs) (→‎References) Newer edit →
Line 230:		Line 230:
	== References ==		== References ==

	* [[Architecture]]		* [[Apps/Architecture]]

Apps/QA: Difference between revisions

Revision as of 19:49, 27 January 2012

Overview

Meeting Notes

Deprecated

Meetings

Dial in

Q4/11

Q3/11

Community

Bugs

Relevant Bugzilla Queries / Tracking Bugs

Dashboard

Marketplace

Extension

Soup

AppSync

Architecture

References

Navigation menu

Search