Mobile/Fennec TestDev

What is TestDev and Fennec

Fennec TestDev is a part of the Fennec project aimed at bringing automation to Fennec specific areas (such as panning, tabs, bookmarks). Automation will be using existing automation frameworks that Firefox uses, but new test cases that are specific to Fennec.

Have a Question?

Not quite sure how to get involved? Have some great ideas? Maybe something isn't clear or you have a better suggestion? Feel free to contact me and I can point you in the right direction!

Contact Info:

• email: jmaher at mozilla dot com
• irc: jmaher

Areas to focus on

• TODO: research or note methods of automation (browser-chrome, chrome, reftest) that ideally should be used. Also any examples or external tools that we need.

• Tabs - bug 485855 (browser-chrome)

The tabs UI is new and unique to Fennec. We have different limitations and display issues to work with. This project is UI automation to cover the basic tab functionality, UI handling of the tabs and browser interaction.

• Bookmarks - bug 486490 (browser-chrome)

Just like the tabs, the Bookmark UI in Fennec is new and unique to Fennec. A lot of work has been done to make this mobile and small screen friendly. We have most of the functionality of the Firefox bookmarks, but a different user flow. This project entails writing UI automation to cover the bookmark usage scenarios, layout, functionality, and edge cases.

• Preferences - bug 489158 (browser-chrome)

In Fennec we have a limited amount of Preferences and options as compared to Firefox. These require us to navigate the UI to display the preferences pane and turn on/off the preferences. It is a simple UI compared to Firefox. This project utilizes the UI to automate the viewing, editing, and testing of the preferences.

• Panning / Zoom - bug 489160 (browser-chrome)

Fennec has a whole new UI to accommodate the stylus method of input rather than a mouse. With this UI, we allow panning (dragging the screen around) as well as double click to zoom in/out. There are also special pan states to view the tab pane and config pane. This creates a whole set of interesting test cases since this is the core navigation method for the mobile browser.

This project focuses heavily on UI automation and will most likely be done in browser-chrome, but could end up utilizing other tools or test methods. This is a challenging project since there is potential for a lot of test cases and harder to solve problems like verifying the pan or zoom is accurate.

• Download Manager - bug 489161 (browser-chrome)
  • Verify panning in list of downloaded items
  • Verify large amount of items in download list
  • Verify searching (including softkeyboard)
  • Verify clearlist button works as expected

• Awesome bar / Search providers / History - bug 489163 (browser-chrome)
  • Verify Awesome Bar displays history/bookmarks
  • Verify we can use the search providers that we have by default
  • Verify clear history removes history and retains bookmarks

• Tel protocol and integrated phone support
  • Verify support of the tel: protocol
  • Verify we send the correct phone number and handle error conditions

• Notification bar prompts
  • Test Password prompt (remember, yes, no)
  • Test Geolocation prompt (remember, yes, no)

• Hardkeys on N810
  • Verify Full screen button
  • Verify dpad navigation (up, down, left, right, center)
  • Verify ESC key

• Hardkeys on HTC Touch Pro
  • Verify screen rotation

• Performance
  • dev team is working on this, TBD

Other TestDev related todo's

• Clearly define methods for:
  • Excluding test cases from the Firefox tree
  • Creating unique test cases for Fennec that only run on Fennec

• Follow up on existing Unittest bugs and get resolution (either in workarounds, or fixes)
  • Mochitest bug 473558
  • Chrome bug 473562
  • Reftest bug 473564
  • XPCShell TBD

References

• Mochitest
• Browser-chrome
• Mochitest-chrome
• Reftest

• Fennec Automation
• Building Fennec