Fennec/NativeUI/ProjectPlan

Concept Review [Toronto Offsite]

Testing

Break down completed features

P0

Panning Perf - nhirata

Tabbed browsing -jhammink

Reloading a page - kbrosnan

Session History - Tony

P1

App Updates - nhirata

native awesomebar (backend) - kbrosnan

Visual Awesomebar (UI) - kbrosnan

Viewport work - Martijn

Native Bookmarking - Aaron

Preferences - Aaron

Default Android Browser Preferences

Text Size (reformat text on zoom) - Martijn

Default zoom (on page load)

Open Pages in overview

Text encoding -nhirata

Block popups - Aaron

landscape-only

home page - Aaron

privacy settings

enable geolocation - jhammink

remember passwords - Tony

password manager/form fill - Tony

Prompt Dialogs - Aaron

Download notifications - Aaron

html5 video controls - Tony

Security Lock on Awesomebar -

UI for handling <select> interaction (select forms, dropdowns) - Martijn

door hangers -jhammink (e.g. geolocation, etc)

Platform and other related Work IME - nhirata

extension mananger startup regression -nhirata

l10n - nhirata

Layout Transform API - jhammink

Jsreftest-jhammink

Update Snippets - nhirata

Ts Expanded RSS - nhirata

Flash/Plugins - nhirata

JS ARM v6 - nhirata

readibility-jhammink

Addons for testing - Martijn

re-enable xpi in toolkit

P2

Redesign of the crash reporter - nhirata

History, visited links - Tony

Sharing - Aaron

Search Engines - Tony

touch events - Martijn

Sync - Tracy/Tony

clean up mobile XPCOM components - no testing

forward button - Aaron

Assign people to create testplans

What made previous test-plans good, what was bad, how can we improve

Identifying this is a good chance for a Process restart

pros / cons of previous process

Features landing every other day, revised bugflow/process?

Identifying a community involvement plan

Work with Marketing and Communications for internal dogfooding<-- Alex Keybl is your guy.

Testday activities, focus on P0, P1, P2's features, and verify bug fixes

Come up with a quick and dirty testplan [kevin]

Continue using mobile newsletter for bi-monthly test ideas

Current sources:

QMO

Planet

Android-mailing list

Mobile

BT

Blogs

Future sources

LinkedIn Test Forums and Groups

Facebook pages

Moz QA Twitter, or Marketing Mobile Account

SUMO

IAMA Reddit / r/Android

Talk about automation strategy for a Java Application

Ask, what's possible to do? (eg. we know robotium works (to a certain degree), only if everything is inside Eclipse.. but more problematic if running out of the app)

We know Clint's team is building classes out under it.

Work with Clint's team to figure out also what we want

Continue to look at the Mochitest framework for the backend code

Get a proof of concept/smoketest for first version

Roadmap with incremental features (and tests implemented accordingly) with upcoming versions.

Doing an audit for litmus test clean up / Case Conductor

A plan is in the works: have waverley run existing Fennec suite against Native, and mark failed/unclear tests for future auditing

Making adding test cases and new features more modular (eg. splitting up Panning and zooming into seperate section)

For new features, (eg. Fx10 has WebGL), create a WebGL as a seperate category

Idea: have a set of core BFTs and smoketest. have a seperate set of features category, and pick and choose which lands into regression test suites

Start with a Litmus Clone, then scrub and choose

Tracking testing coverage (like desktop)

primarily feature tracking. So more communication and awareness of Desktop Team in their approach

Website and Device compatibility

Leverage uTest to work on website compatibility for XUL vs NativeUI

Determing coverage on older devices, low end Arm 7 devices?

When Arm6 device lands, we should look at testing performance on those

Comparison of a site against latest released XUL and NativeUI (major regressions?)

OS coverage for UI : 2.1, 2.2 (Froyo), 2.3 Gingerbread, 3.+ (Honeycomb) 4.+ (ICS)