Confirmed users
3,376
edits
Mobile/Fennec Unittests/Remote Testing: Difference between revisions
Jump to navigation
Jump to search
Mobile/Fennec Unittests/Remote Testing (view source)
Revision as of 15:11, 10 May 2010
, 10 May 2010→Requirements / Setup
| Line 23: | Line 23: | ||
Now that you have verified you can connect, the next step is to start writing python code. We have a library (devicemanager.py) which allows you to do common (file and process) operations across the telnet interface. | Now that you have verified you can connect, the next step is to start writing python code. We have a library (devicemanager.py) which allows you to do common (file and process) operations across the telnet interface. | ||
== Assumptions == | |||
Since we developed this for Mozilla Fennec and Firefox on remote devices, we have made some assumptions which you should be aware of. | |||
* / for all platforms, even windows | |||
** Our agents will convert / to \ if the device uses \. This can cause confusion in commands with arguments such as a browser with http://url. We special case the :// type arguments, so keep that in mind. | |||
* /tests is available as the root of everything | |||
** To simplify things, we assume that /tests is a valid path. If it isn't, we special case that in the agent (as seen in the python agent). In our automation scripts, we rely on /tests for log file paths, profile directories, application, and data. | |||
* install application to /tests/appname | |||
** The existing automation scripts depend on your application (Fennec/Firefox) to be installed in /tests/<appname> (ex. /tests/fennec.) This decision helped simplify things. This is done by pushing and unzipping the application package file to the /tests directory. | |||
* default telnet port is 20701, data channel is 20700. | |||
** in the past we started with 20720, but as we evolved, we have standardized on 20701. We have a data channel defined on port 20700 for the heartbeat and output of some commands (like exec and unzp.) This is important since our integration with buildbot depends on this for monitoring device state. | |||
== Available Agent Commands == | == Available Agent Commands == | ||