Apps/QA/OWA Extension: Difference between revisions

From MozillaWiki
< Apps‎ | QA
Jump to navigation Jump to search
 
(37 intermediate revisions by the same user not shown)
Line 1: Line 1:
== OWA Extension ==
'''NOTE: The extension is no longer going to be supported post completion of the [https://wiki.mozilla.org/Web_Apps_integration Web Apps Integration to Desktop] feature. See that feature under QA to see up to date testing on that Firefox web apps feature. This wiki exists for historical purposes of past testing on the extension.'''
 
== Owners ==


{| style="width: 90%; margin: 0 0 1em 1em"
{| style="width: 90%; margin: 0 0 1em 1em"
Line 13: Line 15:
|}
|}


=== ''Quick Start Guide''<br> ===
== Quick Start Guide  ==


Here is a quick start guide to help you dive right in to Open Web Apps:  
Here is a quick start guide to help you dive right in to Open Web Apps:  


#Download and install the extension - Latest built can be found [http://people.mozilla.com/~dclarke/openwebapps/Extension/latest/ here]  
#Download and install the extension - Latest built can be found [http://people.mozilla.com/~dclarke/openwebapps/Extension/latest/ here]  
#Install apps - Sample apps can be found [https://apps.mozillalabs.com/appdir/ here]  
#Install apps - Sample apps can be found on the [https://apps.mozillalabs.com/appdir/ App Directory] or [https://apps-preview.mozilla.org/ Marketplace]
#View the Dashboard - Apps can be found by clicking the 'Apps' button at the bottom right of your browser or by going [https://myapps.mozillalabs.com/ here]
#View the Dashboard - Apps can be found by clicking the 'Apps' button at the bottom right of your browser or by going [https://myapps.mozillalabs.com/ here]


Once you have apps installed, you can launch them by clicking on them in the Dashboard. You can re-arrange the app icons and you can delete them from the Dashboard as well. You can also go to 'about:apps' (type this without the quotes in the URL bar) and launch apps there, view the manifest or delete apps.
Once you have apps installed, you can launch them by clicking on them in the Dashboard. You can re-arrange the app icons and you can delete them from the Dashboard as well. You can also go to 'about:apps' (type this without the quotes in the URL bar) and launch apps there, view the manifest or delete apps.


=== ''Testing Initiative'' ===
== Testing Initiative  ==
 
==== Focus  ====
 
*Extension (installing, deleting and launching apps)
*Dashboard
*App Sync
*Web Activities/Intents (not Q4)<br>


The testing of the OWA extension will focus on the extension itself (for example, installation/deletion/compatibility and the mozApps.* api), on the dashboard (for example, adding/removing apps), on App Sync and on web activities. The idea is to determine the requirements/specifications of the extension and create manual test cases that will test the basics. Initially, the test cases will be subject to a great deal of changes depending on the requirements and will need to be kept up to date. This applies to the automation as well where keeping the automated test cases in sync with their corresponding manual test cases is essential. Further testing can be done using exploratory methods or a more advanced set of test cases. A proper way of getting apps that can be used for testing will be needed.
=== Scope  ===


The basic iteration of the testing process will hopefully be as follows:  
The following list summarizes the major areas of testing for OWA extension:


#Tester will install the latest build of the OWA extension<br>
* Extension Installation Processes (e.g. Install, Uninstall, Update)
#Tester will verify any bugs that have been resolved on the latest extension build
* MozApps API
#Tester will run automation tests to make sure no regressions have occured
* Apps Lifecycle (e.g. Installation, Launching, Using, Deleting)
#Tester will test using manual test cases and exploratory testing as well -- Once automation is in place, the tester can run the automation for the basic functionality testing
* Dashboard
#Tester will file new bugs as necessary
* App Sync
#Tester will create new test cases as necessary and make sure the current test cases are up to date<br>
* Other Areas


<u>'''NOTE''':&nbsp;The extension will be available and will be needed at launch but eventually it will be built into the browser. Therefore, some of the test cases developed might not be needed anymore when this occurs. </u>
Future areas of concern include the following:


==== Test Cases  ====
* Web Activities/Intents


A set of test cases is being created that focuses on manual testing strategies. The test cases document is actively being updated and can be found [https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdDh2RG1HQ2p5R1pmLUliWDVwS3dPWWc&hl=en_US#gid=1 here]. This document is split up into spreadsheets relating to a function/area to test. If there are any questions, comments or additions (other test cases you think are valuable but are not in the document) please feel free to contact [mailto:dclarke@mozilla.com David Clarke] or [mailto:jsmith@mozilla.com Jason Smith].
=== Testing Requirements and Development Processes ===


There are quite a few questions that should be answered in order to have a good understanding of what the functionality of the extension and apps will be like. Answering these questions is crucial in having a solid set of manual test cases. The list of questions is being tracked [https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdGt0Z194Rm5MMGpGYWdzOXk5cVphU2c&hl=en_US#gid=0 here]. Please feel free to update the document and add any other questions or answer some of the questions there already.
The following list summarizes major testing requirements and development processes for the OWA Extension:


<u>Native App Generation<br></u>
# Determine extension requirements and specifications
# Create manual test cases for basic sanity coverage
# Developing automated test cases for manual test cases
# Exploratory testing of each major part of OWA Extension
# Exploratory testing of using the apps on the web and native
# Creation of complex manual scenario testing


Native app generation just means allowing the user to install apps natively on their machine. This is equivalent to installing a program or application. If you would like to check it out, please follow these steps (advanced) or simply install one of the extensions from [http://people.mozilla.com/~dclarke/openwebapps/Extension/ here]:<br>
Important Notes:  


**NOTE: Github links are out of date. Need to find links to point to mozilla central versions of the links.**
* Requirements are highly volatile, so manual and automated test cases need to be constantly kept up to date.
* Extension will eventually be built into browser, so some test cases may not be needed anymore in the long run


#Install the addon-sdk (from github as the release version will not work) - https://github.com/mozilla/addon-sdk<br>
=== Bug Tracking/Reporting  ===
#Download the oauthorizer package into the packages folder of the addon-sdk - https://github.com/mozilla/oauthorizer<br>
#Clone the openwebapps project - https://github.com/mozilla/openwebapps<br>
#In a terminal, cd into the addon-sdk folder and type: bin\activate (windows) or source bin/activate (linux)<br>
#cd into openwebapps/addons/jetpack<br>
#Type: cfx run - '''Note:''' Currently, using a release version of FF that is less than FF9 will cause an error relating to the icon. Therefore, either use FF9 (currently in beta) or use nightly or aurora by including the --binary command and passing in the path to firefox (.exe for windows) nightly/aurora (ex: cfx --binary="c:\Program Files\Nightly\firefox.exe" run).<br>


==== Test Accounts  ====
Bugs are reported under the "Web Apps" product in the "Extension" component. Below summarizes important links for viewing and reporting extension bugs.


This will have test accounts that can be used for testing Open Web Apps. <br>
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Web%20Apps Report a Web Apps Bug]
*[https://bugzilla.mozilla.org/buglist.cgi?list_id=2530529;resolution=---;resolution=DUPLICATE;query_format=advanced;component=Extension;product=Web%20Apps Extension Bugs]


==== <u></u>Extension Builds<u></u>  ====
Note: See [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ How to Write a Proper Bug] on how to report bugs.


The latest builds for the OWA extension can be found [http://people.mozilla.com/~dclarke/openwebapps/Extension/ here]. The builds are created whenever a commit is made to the openwebapps github repo. The format is openwebapps-&lt;commit id&gt;-&lt;date&gt;.xpi. For automation, openwebapps.xpi within the 'latest' folder is used to avoid making changes to the addon.ini file for every test run. To build the extension yourself from the github repository, please do the following:<br>
Note: A tracking bug was used for tracking the alpha release of the extension in the past.


#git clone http://github.com/mozilla/openwebapps
=== Build Verification Process ===
#cd openwebapps<br>
#make xpi (this will build the xpi file and place it in your current directory)


You can drag the xpi file to your Firefox window to install it. You can also host the file on the web and the user would just click on the xpi file to install it to their Firefox.
The following summarizes the build verification process for the extension:


==== Bug Tracking/Reporting  ====
# Install the latest build of the OWA extension
# Verify any bugs that have been resolved on the latest extension build
# Run automation tests to make sure no regressions have occurred
# Run manual test cases and exploratory testing to capture possible regressions
# File new bugs as necessary
# Update test case document by adding and modifying existing test cases and removing obsolete test cases


This section will contain a list of all the bugs that we have filed or are tracking. Bugs are being logged in the Web Apps product in Bugzilla. Below is a quick link to the product to file a bug. There is also a tracking bug for the extension that is being used to track the progress of work and what needs to be done for an alpha release.
=== Automation  ===


*[https://bugzilla.mozilla.org/show_bug.cgi?id=710337 Extension Tracking Bug]
The automation efforts will revolve around automating the manual test cases using mozmill. Since currently there is not much to work with, a basic skeleton framework is being looked into that can hopefully hold common API's that will be used when automating the test cases.<br>
*[https://bugzilla.mozilla.org/buglist.cgi?priority=P1&priority=P2&field0-0-0=blocked&classification=Server%20Software&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&type0-0-0=equals&value0-0-0=710337&product=Web%20Apps&component=Extension P1 and P2 Bugs]
*[https://bugzilla.mozilla.org/enter_bug.cgi?product=Web%20Apps Web Apps Product - Bugzilla]


<u>Bug Reporting Format:</u>
A demo test run was created with MozMill that installs an app, runs the app, closes the app and then deletes it. The patch for the demo test can be found [https://bugzilla.mozilla.org/show_bug.cgi?id=690493 here]. Henrik Skupin is going to write a blog post about OWA&nbsp;automation and will include a demo that runs this script.


Of course there are multiple ways of reporting a bug and what information to include or format to use can vary, this is just one way that is currently being used. Once you find a bug relating to Apps, you can do the following:
==== Test Server  ====
 
*Test the issue on all supported platforms
*Choose the right component under the Web Apps product in Bugzilla
*Choose the proper severity
*Select which OS the problem occurs for
*If you know who the issue should be assigned to, select the person from the 'Assignee' field. However, this is best left to the triage team if you are not sure.
*Enter a summary of the problem - Be specific and include all relevant information. For example, "Apps do not launch" is not a very effective summary. However, saying 'Apps do not launch from the&nbsp;Dashboard without having the apps extension installed"&nbsp;is a much better summary
*In the Description field:
**Enter a very detailed description of the problem and include any relevant information or observations
**Enter very detailed 'Steps to Reproduce' - This should be easy to follow and detailed enough that any person could reproduce the issue exactly as stated
***If possible, you should attach the xpi file you used to reproduce the problem. Alternately, you can say the following: 'Extension can be found at http://people.mozilla.com/~dclarke/openwebapps/Extension/ and look for <xpi file you used that contains the commit ID and the date>'
**Optionally, you could enter 'Alternate Steps to Reproduce' to show the different ways the problem occurs
**Enter the 'Actual Result' - Enter what happens right after the user performs the last step in the steps to reproduce
**Enter the 'Expected Result'
*Add any attachments as necessary
**This could include screenshots (highly recommended), videos or any files that you think are useful/helpful
 
=== ''Automation''  ===
 
The automation efforts will revolve around automating the manual test cases using mozmill. Since currently there is not much to work with, a basic skeleton framework is being looked into that can hopefully hold common API's that will be used when automating tthe test cases.<br>
 
A demo test run was created with MozMill that installs an app, runs the app, closes the app and then deletes it. The patch for the demo test can be found [https://bugzilla.mozilla.org/show_bug.cgi?id=690493 here]. Henrik Skupin is going to write a blog post about OWA&nbsp;automation and will include a demo that runs this script.<br>
 
==== Test Server<br> ====


An already existing nodejs server was modified to host test apps that we can use for load and smoke testing. To use the test server, please follow these steps (in linux):  
An already existing nodejs server was modified to host test apps that we can use for load and smoke testing. To use the test server, please follow these steps (in linux):  
Line 130: Line 104:
#A webpage will be shown that contains all the test apps
#A webpage will be shown that contains all the test apps
<center>[[Image:Test Server Screenshot.png|border|center|673x383px|Test Server Screenshot.png]]<br></center>  
<center>[[Image:Test Server Screenshot.png|border|center|673x383px|Test Server Screenshot.png]]<br></center>  
'''How It Works:'''  
'''How It Works:'''  


Line 137: Line 112:
*If there is a problem with the page formatting, it's most likely because the icon pic used for the app is not compatible. The icon pic must be 128x128px in order to show up properly in the test server and in the Dashboard. You can use software such as gimp to adjust the pic size.<br>
*If there is a problem with the page formatting, it's most likely because the icon pic used for the app is not compatible. The icon pic must be 128x128px in order to show up properly in the test server and in the Dashboard. You can use software such as gimp to adjust the pic size.<br>


=== ''Documents and Links ''  ===
== Native Apps and Extension Builds ==


===== QA Related<br> =====
=== Native App Generation ===


[https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdDh2RG1HQ2p5R1pmLUliWDVwS3dPWWc&hl=en_US#gid=0 Test Cases Document]  
Native app generation just means allowing the user to install apps natively on their machine. This is equivalent to installing a program or application. If you would like to check it out, please follow these steps (advanced) or simply install one of the extensions from [http://people.mozilla.com/~dclarke/openwebapps/Extension/ here]:<br>


[https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdGt0Z194Rm5MMGpGYWdzOXk5cVphU2c&hl=en_US#gid=0 OWA&nbsp;Extension/Apps Questions]  
#Install the addon-sdk (from github as the release version will not work) - https://github.com/mozilla/addon-sdk<br>
#Download the oauthorizer package into the packages folder of the addon-sdk - https://github.com/mozilla/oauthorizer<br>
#Clone the openwebapps project - https://github.com/mozilla/openwebapps<br>
#In a terminal, cd into the addon-sdk folder and type: bin\activate (windows) or source bin/activate (linux)<br>
#cd into openwebapps/addons/jetpack<br>
#Type: cfx run
 
=== Extension Builds ===
 
The latest developer builds for the OWA extension can be found [http://people.mozilla.com/~dclarke/openwebapps/Extension/ here]. For the faker extension builds, go [http://people.mozilla.com/~dclarke/openwebapps/Extension-Faker/ here].
 
The developer builds are created whenever a commit is made to the openwebapps github repo. The format is openwebapps-&lt;commit id&gt;-&lt;date&gt;.xpi. For automation, openwebapps.xpi within the 'latest' folder is used to avoid making changes to the addon.ini file for every test run. To build the extension yourself from the github repository, please do the following:<br>
 
#git clone http://github.com/mozilla/openwebapps
#cd openwebapps<br>
#make xpi (this will build the xpi file and place it in your current directory)
 
You can drag the xpi file to your Firefox window to install it. You can also host the file on the web and the user would just click on the xpi file to install it to their Firefox.
 
== Important Documents and Links  ==
 
=== QA  ===
 
[https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdDh2RG1HQ2p5R1pmLUliWDVwS3dPWWc&hl=en_US#gid=0 Test Cases Document]
 
[https://docs.google.com/spreadsheet/ccc?key=0AiZoGR-iOAlUdEJwelZRMW01LWN1RUFpT1hsWkt0Rnc March 1st Test Run]
 
[https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdGt0Z194Rm5MMGpGYWdzOXk5cVphU2c&hl=en_US#gid=0 Extension and Apps Questions]  


[http://people.mozilla.com/~dclarke/openwebapps/Extension/ OWA Extension Builds]  
[http://people.mozilla.com/~dclarke/openwebapps/Extension/ OWA Extension Builds]  


[https://bugzilla.mozilla.org/show_bug.cgi?id=698879 Extension Tracking Bug]  
[[Apps/QA/OWA_Extension/Test Framework | Test Framework]]
 
[https://bugzilla.mozilla.org/show_bug.cgi?id=690899 Marketplace Tracking Bug]  


[https://bugzilla.mozilla.org/buglist.cgi?list_id=1576542&short_desc=extension%20app%20apps%20dashboard&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&short_desc_type=anywords&component=OpenWebApps&product=Mozilla%20Labs General Tracked Bugs]  
[https://bugzilla.mozilla.org/buglist.cgi?list_id=1576542&short_desc=extension%20app%20apps%20dashboard&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&short_desc_type=anywords&component=OpenWebApps&product=Mozilla%20Labs General Tracked Bugs]  
Line 155: Line 155:
[https://addons-dev.allizom.org/en-US/apps/ Firefox Store Apps Staging Server]
[https://addons-dev.allizom.org/en-US/apps/ Firefox Store Apps Staging Server]


===== Information/Tracking  =====
=== Information/Tracking  ===


[https://docs.google.com/document/d/1Q5SJsLmMLQZPGCn7gqErEqkJ6hJ42RbSYqPeAZ775Vw/edit?disco=AAAAAD4pDbs Dashboard Spec Document]  
[https://docs.google.com/document/d/1Q5SJsLmMLQZPGCn7gqErEqkJ6hJ42RbSYqPeAZ775Vw/edit?disco=AAAAAD4pDbs Dashboard Spec Document]  
Line 165: Line 165:
[https://wiki.mozilla.org/Apps/Overview Apps Overview - Main]  
[https://wiki.mozilla.org/Apps/Overview Apps Overview - Main]  


[https://wiki.mozilla.org/Apps/WebRT WebRT] - Useful information (can be used to create more test cases)
[https://wiki.mozilla.org/Apps/WebRT WebRT]


[https://github.com/mozilla/openwebapps Apps Github Repository]  
[https://github.com/mozilla/openwebapps Apps Github Repository]  
Line 171: Line 171:
[https://github.com/mozilla/openwebapps/blob/develop/docs/ACTIVITIES.md Web Activities/Intents]
[https://github.com/mozilla/openwebapps/blob/develop/docs/ACTIVITIES.md Web Activities/Intents]


===== Explore  =====
=== Explore  ===


[https://apps.mozillalabs.com/appdir/ Sample Apps (for demo)]  
[https://apps.mozillalabs.com/appdir/ Sample Apps (for demo)]  


[https://addons-dev.allizom.org/en-US/firefox/ Firefox Store Staging Server]<br>
[https://addons-dev.allizom.org/en-US/firefox/ Firefox Store Staging Server]<br>
=== ''Infrastructure Requirements''<br>  ===
'''Alternate Build Generation and Hosting'''
*A people.mozilla.com account has been created where the xpi file for the OWA extension will be placed as needed:&nbsp;mdabbagh@people.mozilla.com<br>
*Developers or testers can make builds and place them there (for example, a bug is fixed and a quick check is needed using the developer's local code)
*Allows customization of builds
<u>Getting&nbsp;Started:</u>
To get started and to upload xpi files, you first need a people.mozilla.com account. Please follow [https://intranet.mozilla.org/ShellServer this link] in order to setup the account and to learn how to upload/download files.
''If you only want to download the xpi files, please go [http://people.mozilla.com/~dclarke/openwebapps/Extension/ here]. If you would like an xpi file (extension) built, please send an email to mdabbagh@mozilla.com or ping mdabbagh in IRC (#qa, #openwebapps, #automation). You can also build the file yourself by following the instructions [https://github.com/mozilla/openwebapps here] (please use linux, Ubuntu for example, instead of Windows. It's much easier).''
<br>Marketplace instance managed by Al, limited access.

Latest revision as of 04:37, 5 March 2012

NOTE: The extension is no longer going to be supported post completion of the Web Apps Integration to Desktop feature. See that feature under QA to see up to date testing on that Firefox web apps feature. This wiki exists for historical purposes of past testing on the extension.

Owners
QA Lead: Jason Smith
Lead Developer: Mike Hanson

Quick Start Guide

Here is a quick start guide to help you dive right in to Open Web Apps:

  1. Download and install the extension - Latest built can be found here
  2. Install apps - Sample apps can be found on the App Directory or Marketplace
  3. View the Dashboard - Apps can be found by clicking the 'Apps' button at the bottom right of your browser or by going here

Once you have apps installed, you can launch them by clicking on them in the Dashboard. You can re-arrange the app icons and you can delete them from the Dashboard as well. You can also go to 'about:apps' (type this without the quotes in the URL bar) and launch apps there, view the manifest or delete apps.

Testing Initiative

Scope

The following list summarizes the major areas of testing for OWA extension:

  • Extension Installation Processes (e.g. Install, Uninstall, Update)
  • MozApps API
  • Apps Lifecycle (e.g. Installation, Launching, Using, Deleting)
  • Dashboard
  • App Sync
  • Other Areas

Future areas of concern include the following:

  • Web Activities/Intents

Testing Requirements and Development Processes

The following list summarizes major testing requirements and development processes for the OWA Extension:

  1. Determine extension requirements and specifications
  2. Create manual test cases for basic sanity coverage
  3. Developing automated test cases for manual test cases
  4. Exploratory testing of each major part of OWA Extension
  5. Exploratory testing of using the apps on the web and native
  6. Creation of complex manual scenario testing

Important Notes:

  • Requirements are highly volatile, so manual and automated test cases need to be constantly kept up to date.
  • Extension will eventually be built into browser, so some test cases may not be needed anymore in the long run

Bug Tracking/Reporting

Bugs are reported under the "Web Apps" product in the "Extension" component. Below summarizes important links for viewing and reporting extension bugs.

Note: See How to Write a Proper Bug on how to report bugs.

Note: A tracking bug was used for tracking the alpha release of the extension in the past.

Build Verification Process

The following summarizes the build verification process for the extension:

  1. Install the latest build of the OWA extension
  2. Verify any bugs that have been resolved on the latest extension build
  3. Run automation tests to make sure no regressions have occurred
  4. Run manual test cases and exploratory testing to capture possible regressions
  5. File new bugs as necessary
  6. Update test case document by adding and modifying existing test cases and removing obsolete test cases

Automation

The automation efforts will revolve around automating the manual test cases using mozmill. Since currently there is not much to work with, a basic skeleton framework is being looked into that can hopefully hold common API's that will be used when automating the test cases.

A demo test run was created with MozMill that installs an app, runs the app, closes the app and then deletes it. The patch for the demo test can be found here. Henrik Skupin is going to write a blog post about OWA automation and will include a demo that runs this script.

Test Server

An already existing nodejs server was modified to host test apps that we can use for load and smoke testing. To use the test server, please follow these steps (in linux):

Setup:

  1. git clone git://github.com/mozilla/openwebapps.git
  2. cd openwebapps
  3. Type: 'git submodule init' and then 'git submodule update'
  4. Make sure to have node installed - If not, you can get it from here. You can also follow one of the methods here.

Run:

  1. cd site/tests/
  2. Type: 'node run.js' - All necessary servers will start
  3. Launch the URL after 'Testing server started, to run tests go to:' and replace index.html with appstore.html
  4. A webpage will be shown that contains all the test apps
Test Server Screenshot.png

How It Works:

It's just a nodejs server that creates a separate server for each app that we have and hosts the necessary files within each server. The directory where the apps are stored is in site/tests/apps and each app has a folder within this directory.If you would like to add apps, all you have to do is add a folder within the apps directory and place the necessary files within that folder (please look at repo under site/tests/apps/ for examples). Please note the following:

  • The manifest file must be called: manifest.webapp (this should be changed within the code to be more dynamic)
  • If there is a problem with the page formatting, it's most likely because the icon pic used for the app is not compatible. The icon pic must be 128x128px in order to show up properly in the test server and in the Dashboard. You can use software such as gimp to adjust the pic size.

Native Apps and Extension Builds

Native App Generation

Native app generation just means allowing the user to install apps natively on their machine. This is equivalent to installing a program or application. If you would like to check it out, please follow these steps (advanced) or simply install one of the extensions from here:

  1. Install the addon-sdk (from github as the release version will not work) - https://github.com/mozilla/addon-sdk
  2. Download the oauthorizer package into the packages folder of the addon-sdk - https://github.com/mozilla/oauthorizer
  3. Clone the openwebapps project - https://github.com/mozilla/openwebapps
  4. In a terminal, cd into the addon-sdk folder and type: bin\activate (windows) or source bin/activate (linux)
  5. cd into openwebapps/addons/jetpack
  6. Type: cfx run

Extension Builds

The latest developer builds for the OWA extension can be found here. For the faker extension builds, go here.

The developer builds are created whenever a commit is made to the openwebapps github repo. The format is openwebapps-<commit id>-<date>.xpi. For automation, openwebapps.xpi within the 'latest' folder is used to avoid making changes to the addon.ini file for every test run. To build the extension yourself from the github repository, please do the following:

  1. git clone http://github.com/mozilla/openwebapps
  2. cd openwebapps
  3. make xpi (this will build the xpi file and place it in your current directory)

You can drag the xpi file to your Firefox window to install it. You can also host the file on the web and the user would just click on the xpi file to install it to their Firefox.

Important Documents and Links

QA

Test Cases Document

March 1st Test Run

Extension and Apps Questions

OWA Extension Builds

Test Framework

General Tracked Bugs

Firefox Store Apps Staging Server

Information/Tracking

Dashboard Spec Document

Apps Sync Spec

Apps Wiki

Apps Overview - Main

WebRT

Apps Github Repository

Web Activities/Intents

Explore

Sample Apps (for demo)

Firefox Store Staging Server

Retrieved from "https://wiki.mozilla.org/index.php?title=Apps/QA/OWA_Extension&oldid=403740"