QA/TDAI/Mobile Test Framework Meeting: Difference between revisions

Jump to navigation Jump to search
Line 43: Line 43:
*** Most platforms seem to have some sort of "tethered" development mode that provides the support we need
*** Most platforms seem to have some sort of "tethered" development mode that provides the support we need
*** Verified this approach on WinMO/WinCE mochitests
*** Verified this approach on WinMO/WinCE mochitests
*** Could be a promising mechanism if we use our own serial interfaces with the devices to get around limitations that provider specific methods have (for instance, use our own protocol over serial rather than active sync so we can have more devices per host in the WinMO/WinCE case)
*** Gets around issues with wifi in the building
** '''DISADVANTAGES'''
** '''DISADVANTAGES'''
*** Seems more portable to depend on wifi access, since devices tend to support that
*** At least in WinMo/WinCE case activesync tethering has not proved to be reliable enough for large scale automation
*** At least in WinMo/WinCE case activesync tethering has not proved to be reliable enough for large scale automation
*** Host to device mapping might constrain us unnecessarily (especially if it requires a 1:1 mapping rather than a 1:many)
*** Host to device mapping might constrain us unnecessarily (especially if it requires a 1:1 mapping rather than a 1:many)


''Other Ideas?''
''Other Ideas?''
Confirmed users
3,816

edits

Navigation menu