Apps/QA/Native Install Android

Android Native Install (Soup)

QA Lead:	Aaron Train
Lead Developer:	Anant Narayanan

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: https://github.com/anantn/soup

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

Introduction

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 addons.mozilla.org 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

Risks

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
• Cross-platform compliance to iOS using a PhoneGap solution

Milestones

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
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

Major Milestones / Stories			Date
Native installation and management capabilities			ETA End of Oct

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

Priority	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
P2	Ability to navigate the Open Web Applications store on live site
P3	(Future) BrowserID login to utilize Mozilla Sync API's to sync Open Web Applications

Test Plan

Automation

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.

Not Testing

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

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

Github Repostory

Issues

• Set up an OrientationEventListener -- (Phonegap.xml is missing)
• Supply a drawable resource and label for org.mozilla.labs.WEBAPP intent

Documents / Links

Documentation

• Mobile Application User Flow (Design document)

Links

• Test Cases Document
• GitHub Repository
• Apps Overview - Main
• Android (PhoneGap) and Apps Questions