Apps/QA/Native Install Android

From MozillaWiki
< Apps‎ | QA
Jump to: navigation, search

Android Native Install (Soup)

QA Lead: Aaron Train
Lead Developer: Harald Kirschner

Quick Start Guide

Here is a quick start guide to get you to install a signed copy of the latest version for install in Android of the native open web apps application:

Github Repository:

Build instructions

  1. Clone the Git repository
  2. Download the Android SDK
  3. Import the project into Eclipse
  4. Configure the project properties to target Android API Level 8 (Android 2.2 (Froyo))
  5. Build and Run

Compile and build 'Soup' from the Android project (targeting Android API Level 8). Enable 'Install form Unknown Sources' on your Android device under Application Settings. Once installed, you may find the application in the Android application launcher.

Join us on #openwebapps and #QA

Prebuilt Android Package Binaries


This quarter we will see emerge the essential Mozilla application store marketplace and native Android open web application management application. The application will be built using PhoneGap utilizing cross-platform languages such as HTML/CSS and JavaScript, and using APIs provided by Apps JavaScript API and to provide a list of installable applications. In essence, upon completion of a transaction (wether it be installing a free or paid open web application), the result of the install action is to download and install an open web application to the users Android home screen. Invoking an open web application will launch its associated web site in a WebKit runtime.

Mobile Technologies

Native Android Application

  • Support for installable applications
    • The Android application understands what a web application is, and helps one manage ones list of applications
      • Application metadata storage
      • Installation query/management API
  • Support for permission requests
    • When an application is installed, it can request a number of permissions at once
  • Installed Open Web Applications
    • When one invokes an open web application, it invokes in a chrome-less window providing the appearance of a traditional Android application
  • Support for purchasable applications
    • Ability to cycle through and purchase applications through PayPal transactions
  • BrowserID sign-on
    • Single point BrowserID sign-in providing transition from dashboard to market


With such an assemblage of utility as described from the requirements, there are multiple negative risks:

  • Deliverance of dependancy of deployed market with curated applications
  • Deliverance of PayPal integration to support the handling of paid applications
  • BrowserID integration
  • AppSync integration and utilization
  • Cross-platform compliance to iOS using a PhoneGap solution


Testing of the native Android application must focus on a variety of modules that comprise the specified requirements including native installation capabilities and launching of associated open web applications in a chromeless window. In essence, we should extract all requirements and specifications from the application to create manual regression test cases. Exploratory methods and smoke-tests should also cover a more advanced set of test cases. A proper sandboxed environment should be used for testing.

The testing process involves:

  1. Tester should install (if builds are hosted) or compile latest code from this Github repository; alongside Bugzilla.
  2. Tester will verify any bugs that have been resolved with the associated build
  3. (Tester will run automation tests to make sure no regressions have occurred)
  4. Tester will run using manual test cases and exploratory testing as well
  5. Teser will file new bugs as necessary
  6. Tester will create new test cases as necessary and make sure the current test cases are up to date

NOTE: A new product will be created on Litmus, and test-run will be created on Litmus in order to run the manual suite of tests.

Soup for Android

Major Milestones / Stories
Native installation and management capabilities Q4 2011
Implement device permissions TBD

Soup base code on WebKit

Major Milestones / Stories
Implements navigator.mozApps Done
Talks to AppSync service Q4 2011
Integrates with BrowserID Q4 2011
Provide simple "about:apps" app list Q4 2011
Packaged as a PhoneGap app Q4 2011
Solves pre-auth problem Q4 2011

Test Cases

A set of test cases are being created that focus on manual testing strategies. The main functionality document being used to aid in the creation fo the test cases can be found here. The document is split up into worksheets relating to a function/area to test. Questions regarding this document should refer to Aaron (irc:AaronMT).

There are quite a few questions that should be answered in order to have a good understanding of the requirements and full capabilities are of the Android application. Answering these questions is crucial in having a solid set of manual test cases. The list of questions is being tracked here. Please feel free to update the document and add any other questions or answer some of the questions there already.

Release Criteria

Developer Preview

 Release Invariant
P1 Installation and management capabilities for Open Web Applications
P1 Successful launch of associated Open Web Application into WebKit (Chromeless) window
P1 Ability to purchase free and paid Open Web Applications through using PayPal
P1 Ability to navigate the Open Web Applications store on live site
P1 BrowserID login to utilize Mozilla Sync API's to sync Open Web Applications

Post Developer Preview - Q1 2012

 Release Invariant

Test Plan

Manual Testing

What do we test

What we do not test

  • Fennec front-end integration with Navigator.MozApps JavaScript Open Web Apps API interactions (i.e., installing, managing, uninstalling and granting permissions to web-apps)


Currently there is no automation in the testing of the native Android application. Efforts are involved in investing Robotium as a candiate for utility and test creation.

Release Management

Entry Criteria

  1. Builds & staging are available for testing with the features to be QA'ed
  2. QA has all the details including specs and scope of details to be verified

Exit Criteria

  1. All the features targeted for Phase I have been QA'ed
  2. All P1's, P2's, Blocker and Critical bugs have been verified by QA or have been marked [QA-] as not needing verification
  3. QA has apprised stakeholders on IRC or through E-Mail of the testing performed, and the outstanding bug list
  4. Stakeholders from QA, Dev and Product have met to discuss pre-release readiness of the release
  5. All stakeholders have signed off on the release
  6. QA runs sanity tests after push to Android market

Test Cases

Mobile App User Integration Flow

  • Native Android application on Android Market
  • Buying Etherpal (Free Application)
  • First-time BrowserID user
  • Native Android application on Android Market
  • Buying Evernote (after having bought a free application)
  • Returning BrowserID user
  • First-time PayPal user

Bug Tracking


Bugzilla Queries

Github Repostory



The following is the current list of tasks being worked on. Please feel free to take any task that is not already claimed or if you would like to help, please contact the person under the 'Assigned' column.

Task Description
Determine specifications/requirements for the application and Open Web Apps to use as reference for manual test cases In Progress All the available documentation that is being used to track the progress the of the extension and to aid in creating test cases can be found below under Documents/Links. AaronMT P1
Create manual test cases for the application In Progress Manual test cases will be tracked here, and questions will be tracked here AaronMT P2
Start testing the native Android application Blocked Akin to the OWA extension, there is currently not much that is ready to be tested. Eyeing repository awaiting further commits. Have approached Anant, to request a schedule or timeline but none was provided. AaronMT P1

Documents / Links



Testing Related