The document provides tips for developing automated tests for the Boot to Gecko (B2G) mobile operating system. It outlines components of B2G like the emulator and build environment. It demonstrates starting the emulator, sending commands, and debugging. An existing WebAPI test is code walked through and run in the emulator. Participants are instructed to develop a new automated WebAPI test for B2G using Marionette that runs in the emulator. Contact information is provided for those interested in contributing.

2. Make Sure Your Code Works:
How to Craft Automated Tests for B2G
Henrik Skupin and Rob Wood
September 8-9th, 2012
Warsaw, Poland

3. Welcome
• Introductions: Henrik Skupin, Rob Wood
• Goalof our session: Each participant will develop an
automated test for B2G
• Doany of our participants have experience
developing automated tests? (Not a prerequisite)

4. Automated Tests
Tips for successful automated test development:
• Clearly define test scope and test cases
• Keep tests simple, independent, and leave the
environment in the state in which it was found
• When a test fails, clearly define why in the log
• Use the framework to your advantage
• Know when to automate and when not to
• Code well and follow style guidelines

5. Components
• B2G
• WebAPI
• Gonk
• Marionette
• B2G device emulator
• B2G build environment

6. B2G Device Emulator
Demonstration:
• How to start the emulator
• Sending commands to the emulator (telnet)
• Debugging the emulator using ADB

7. Test Walk-Thru
Demonstration:
• Code walk-thru of an existing WebAPI test
• Running an existing WebAPI test in the emulator

8. Hands-On
Hacking session for participants:
• Develop a new B2G WebAPI automated test that
uses Marionette and runs in the device emulator
(test case details will be provided)
• Attach the finished test to the specified Bugzilla issue

9. Contact Us
Interested in contributing? Contact us!
https://wiki.mozilla.org/Auto-tools/Automation_Development
Rob Wood
rwood@mozilla.com
Henrik Skupin
hskupin@mozilla.com

10. Thank You