e802105a7b
changelog and bump to 0.11.2 for publish
2013-10-29 14:41:16 -07:00
8a1d43497c
changelog and bump to 0.11.1 for publish
2013-10-29 12:33:07 -07:00
8bf8db3dc6
changelog and bump for publish 0.11.0
2013-10-23 11:27:19 -07:00
3373f2ec46
upgrade npm packages
2013-10-17 10:30:12 -07:00
651f4ff13a
move instruments-client into bin/ and rename helpfully
2013-10-17 10:30:12 -07:00
af930d11a9
move appium bin into bin/
2013-10-17 10:30:11 -07:00
30b9ee4047
move authorize-ios into bin
2013-10-17 10:30:11 -07:00
31c49f590d
move server-related stuff into lib/server
2013-10-17 10:30:11 -07:00
3eee9d8a61
move code into lib/ like a normal node project
2013-10-17 10:30:10 -07:00
0f9ecc0e4b
upgrade linter and ignore un-linted files rather than specifying linted files
2013-10-17 10:30:08 -07:00
a8797e06e6
changelog and bump version for publish 0.10.4
2013-10-15 15:22:36 -07:00
63bd9f7556
changelog and bump for publish 0.10.3
2013-10-14 09:51:51 -07:00
3b103c81a9
changelog and bump to 0.10.2 for publish
2013-10-11 16:00:53 -07:00
5965ef39fd
Android mobile :reset now uses adb uninstall/pm install
...
The old clean.apk approach to resetting state doesn't work well. Using
instrumentation means the app is running when the data is deleted. It's better
to use the standard adb install/uninstall commands.
To make this faster, the apk is pushed to the device once (/data/local/tmp/) and
then installed from that location on each reset. Using the regular adb install
command is slow due to the file transfer speed.
Before uninstalling the app, it's stopped to prevent crashes. Some apps don't
like to be uninstalled while running.
2013-10-09 15:21:21 -04:00
d0827d6b25
bump version and changelog for 0.10.1
2013-09-27 17:33:27 +01:00
7a258149db
changelog and bump version to 0.10.0 for publish
2013-09-27 10:56:19 +01:00
bdbe933d1a
changelog and bump for publish 0.9.1
2013-09-16 19:07:18 +02:00
37f4a95f7b
update yiewd example again
2013-09-15 11:18:36 +02:00
d82449e0d2
update yiewd example with new yiewd syntax
2013-09-15 11:18:35 +02:00
e5eb9f100d
fix issue with touch/click on android getting wrong params
2013-09-09 10:18:50 -07:00
e6c85cbcad
changelog and bump to 0.9.0 for publish
2013-09-05 17:50:30 -07:00
06424765d4
add a yiewd example for node
2013-09-04 17:56:38 -07:00
e06f798297
make sure we use new yiewd
2013-09-04 15:52:25 -07:00
c3e1da7b98
use monocle-js instead of monocle.js
2013-09-04 14:22:32 -07:00
f69a604f1d
changelog and bump to 0.8.5 for publish
2013-08-14 17:35:43 -07:00
f9f2a0f338
changelog and bump to 0.8.4 for npm publish
2013-08-13 16:44:53 -07:00
8b947cf9f5
bump and update to v0.8.3 for npm publish
2013-08-06 09:50:15 -07:00
ddd5d6dba5
Issue #853 : XML Info plists are now accepted.
...
Signed-off-by: Matt Isaacs <misaacs@gilt.com >
2013-07-26 18:46:59 -04:00
e9cc66197a
changelog and bump for publish 0.8.2
2013-07-20 14:28:46 -07:00
1d4c05029d
changelog and bump for npm publish 0.8.1
2013-07-19 17:05:22 -07:00
0c1eba53f2
changelog and bump for publish 0.8.0
2013-07-03 11:20:31 -07:00
37150b594c
use streams instead of data events for chromedriver subproc
2013-07-01 17:33:51 -07:00
370b7e5282
make chrome device proxy to chromedriver instead of using atoms
2013-07-01 17:33:51 -07:00
120bb68132
changelog and bump for publish 0.7.3
2013-06-14 17:17:41 -07:00
a0a8155f0c
changelog and bump for publish 0.7.2
2013-06-14 17:11:09 -07:00
478dfb6740
add authorize_ios binary so npm users can run authorize
2013-06-14 17:01:44 -07:00
055dcdf7ef
update changelog and bump for publish 0.7.1
2013-06-06 13:56:10 -07:00
713e6402b7
changelog and bump for npm publish 0.7.0
2013-06-05 19:21:53 -07:00
674d1e2667
changelog and bump to 0.6.1 for npm publish
2013-05-31 15:38:16 -07:00
192667fd50
Clean up functional tests for alert detection removing the need for
...
the telnetclient package.
Style change
2013-05-29 17:39:46 -05:00
5d7cc06ae8
Added changes to notify websocket listeners of alert dialogs.
...
One thing to keep in mind: iOS and Android treat dialogs differently. iOS "system" dialogs can be triggered from the application under test as well as from external sources (the system). However, Android treats dialogs as any other window. So, to make this work, the bootstrap app looks for windows with the package name of "com.android.systemui". These are dialogs that the system has instantiated, but not the app.
So, for example, if we had the same application written on both platforms, and they both had a login screen, and you click on the login button without putting in a username. On iOS, you would be notified if they used a standard system dialog, and you would not be notified on Android. However, if the system put up a low battery dialog, it would be detected on both systems.
So... The main reason for implementing this is to stop failing tests from unintentional dialogs appearing during an overnight test.
Updated call signiture to instruments.
2013-05-28 13:11:36 -05:00
324a8c7274
changelog and bump for publish 0.6.0
2013-05-24 13:00:49 -07:00
bd4fbad873
fixed minor rebase issue by adding comma.
2013-05-16 10:48:41 +01:00
f5c6abfa4a
incorrect version of ws supplied. updated to 0.4.25
2013-05-16 09:47:45 +01:00
8267234279
Android Works on Windows (must use --no-reset)
2013-05-14 07:51:13 -07:00
3a4d1566d3
bump to 0.5.1 and changelog for npm publish fix
2013-05-14 01:18:48 -07:00
d6420c3fe9
bump to 0.5.1 and changelog for npm publish
2013-05-14 00:12:11 -07:00
d03ea5376c
Windows Support for building and installing Android Bootstrap
2013-05-13 11:40:25 -07:00
316f1b6085
Bumped required node-idevice to 0.1.2
2013-05-09 15:55:47 -07:00
08abb2bd1a
Initial work in iOs installation.
2013-05-09 15:55:47 -07:00
Jonathan Lipps