Auto-tools/Projects/Android Parts Bucket: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 29: Line 29:
# Take the agent from <objdir>/build/mobile/sutagent/android/sutAgentAndroid.apk and install it on the device using adb.
# Take the agent from <objdir>/build/mobile/sutagent/android/sutAgentAndroid.apk and install it on the device using adb.
# Use the agent to install your fennec build onto the device. (bear's code, in a bug that I can't find at the moment).
# Use the agent to install your fennec build onto the device. (bear's code, in a bug that I can't find at the moment).
# download a firefox linux trunk build and drop it into a "firefox" dir at the same level as your unpacked test packages.
# Download a Firefox Linux trunk build and drop it into a "firefox" dir at the same level as your unpacked test packages.
# Unpack a firefox linux trunk test build and copy the bin/ directory onto the firefox directory you unpacked (steps 4 and 5 allow you to run the httpd.js webserver for the tests)
# Unpack a Firefox Linux trunk test build and copy the bin/ directory onto the firefox directory you unpacked (steps 4 and 5 allow you to run the httpd.js webserver for the tests)
# Run the tests setting --deviceIP to your device, --remote-webserver to the IP address of your linux machine --xre-path to the firefox directory and whatever other parameters you want per test type (logging, chunking, etc).
# Run the tests setting --deviceIP to your device, --remote-webserver to the IP address of your Linux machine --xre-path to the firefox directory and whatever other parameters you want per test type (logging, chunking, etc).

Revision as of 05:05, 20 July 2010

Welcome to the Android parts bucket. Here you can find all the pieces of the automation that you need to wire together in order to establish a walking talking test dummy.

SUTAgent

  • Android sutagent checked in to m-c
  • Will be available in packaged tests under bin/ directory once bug 563095 is fixed (currently in review).

Devicemanager.py

  • Available in m-c AND in talos (currently, talos is not up to date, use the one in m-c).
  • For unittests, the devicemanager will be packaged into the test packages

Heartbeatmonitor/heartbeatdaemon

  • These are in the remote-testing repo with their assorted scripts. You need everything from the buildbotscripts directory at the moment.
  • Status: undergoing final testing

Mochitest Plain

  • All changes in, ready to go

Mochitest Other

Reftest, JSReftest, Crashtest

  • bug 573694 - about to go into review eta in review July 20.

XPCShell

  • Work not begun. These have not proved to be important tests to the mobile developers so they have been prioritized last. ETA: 1-2 weeks once work begins. Status: we have the code used to run these on winmo, we need to update it to work on Android. Since Android is more "unix-y" it will be much easier to make these run than it was to get them to run on winmo.

To put an android unit test together

  1. Build Android in m-c
  2. Take the agent from <objdir>/build/mobile/sutagent/android/sutAgentAndroid.apk and install it on the device using adb.
  3. Use the agent to install your fennec build onto the device. (bear's code, in a bug that I can't find at the moment).
  4. Download a Firefox Linux trunk build and drop it into a "firefox" dir at the same level as your unpacked test packages.
  5. Unpack a Firefox Linux trunk test build and copy the bin/ directory onto the firefox directory you unpacked (steps 4 and 5 allow you to run the httpd.js webserver for the tests)
  6. Run the tests setting --deviceIP to your device, --remote-webserver to the IP address of your Linux machine --xre-path to the firefox directory and whatever other parameters you want per test type (logging, chunking, etc).
Retrieved from "https://wiki.mozilla.org/index.php?title=Auto-tools/Projects/Android_Parts_Bucket&oldid=239325"