$driver.session_id
=> "efac972c-941a-499c-803c-d7d008749bad"

Why is selenium webdriver appending bad to the session_id?

execute_script %(UIATarget.localTarget().frontMostApp().mainWindow().elements().firstWithPredicate("name contains[c] 'some text'").name())

Android should not have to set APP_PATH. APK_PATH should be used for Android and APP_PATH for iOS.

Appium now returns secure when searching for textfield tag. This is a great change however ruby_lib has to be updated because the existing search of (textfield + secure) will now be transformed into (textfield + secure + secure).

• jlipps/appium@2cd097a

Appium supports XPath index now so we don't have to get all elements from the server to find a particular index on the client.

Methods to update

• first_ele
• last_ele appium/appium#444
• ele_index

s_text text should only return the first match. Appium will currently send all matches.

au.getElementByXpath('text[contains(@text, "sometext")]')

NoMethodError: undefined methodkeys' for nil:NilClass` error on Selendroid

appium_lib-0.3.7/lib/appium_lib/android/helper.rb:69:inblock in run'`

Appium provides detailed information in origValue which is promptly discarded by selenium-webdriver. Dynamically patch selenium-webdriver to output meaningful error messages.

When ruby_lib is used in a repl, the default wait of 30 seconds is too long.

find is unable to locate elements that aren't attached to the main window.

find should search webview first and skip it if it doesn't exist.

UIAWebView

• $driver.window_handles see hybrid apps wiki
  • execute_script 'au.mainApp.windows().length' window 0 is the main window. window 1 is another window. webviews are usually .windows()[windowIndex].scrollViews()[0].webViews()[0]
• find_element :name, 'name' will search in webviews so that should be called if the regular name method returns no results.
• find_elements :tag_name, :text also searches into webviews.
• text is empty on webview text. name and value are filled in.
• xpath "text[contains(@name, 'legal')]" works.

execute_script 'UIATarget.localTarget().frontMostApp().windows()[0].scrollViews()[0].webViews().length'

text_include text
text text_exact

It's helpful for a console to have global methods so there's no driver prefix required. In production though, it'd be nice to use the driver object directly and have zero global methods.

appium/appium#512

Add a helper method to easily check if an element exists or not. It should return true or false.

> alert_accept
post /element
{
    :using => "xpath",
    :value => "//button[last()]"
}
post /ele

Workaround: find_element(:link_text, 'Yes').click

Selendroid requires a new mode.

driver.extend Selenium::WebDriver::DriverExtensions::HasTouchScreen
https://github.com/DominikDary/selendroid/issues/27

flick speed is either :normal or :fast

Setting APP_PATH once isn't a great user experience. There should be a way to dynamically switch the app path to run iOS and Android within the same run.

.click should be included in the Ruby debug logs

the alert methods are also missing in debug logs.

Individual methods shouldn't require if $os == :android or if $os == :ios. OS specific code should be located in a dedicated file.

button_click 'sign in' button('sign in').click

jlipps/appium@4acb7da
jlipps/appium@3a0e086

Selendroid launch is supported however that's not very useful if commands can't be issued.

txt method to search all text.

find_elements :xpath, "//*[contains(@text, 'sign in')]"

See https://github.com/appium/ruby_lib/blob/master/lib/appium_lib/element/android/generic.rb#L57

The existing JavaScript in iOS for generic.rb in ruby_lib doesn't search all elements and needs to be rewritten.

Appium's getTree method works.

bc1cdb1 relies on classNameMatches which doesn't work that well. Instead multiple exact class searches should be performed.

This issue is specific to Android.

page is only implemented for Android.

appium/appium#449 is merged so these methods should work on Android now.

• textfields
• s_texts
• buttons

Pry defines an inspect method.

name( element_name ) find_element :name, element_name
names( element_name )``find_elements :name, element_name

appium/appium#310

Also rename AppiumLib module to Appium

duration value must be greater than or equal to 0.5 or less than 60

mobile :swipe, startX: 0.85, endX: 0.3, startY: 0.85, endY: 0.3, duration: 0.5

Change start/end to get different results.

Automated testing should ensure the commands work. It'll be possible to automate the tests once Sauce Labs launches Android support on the hosted service.

appium/appium#509 (comment)

strings.xml can be recreated from an APK and used to search for strings. This means tests won't fail when text changes as is currently the case with uiautomator.

• Tasks
  • Java jar that generates strings.xml from an APK
  • Parse jar output into Ruby
  • Enable client side mapping of key pairs to string text.

# populate the resource method.
load_resources_from_apk 'path/to/apk'

# find element using the resource id 'sign in'
find_element :name, r('sign in')

• label == name (label is not currently included in the page output)
• class is type
• name is really id. id/ prefix should be removed.
• text is found via link_text and accessed using the text attribute (no change required in page)
  and there are some more differences compared to uiautomator.
• https://github.com/DominikDary/selendroid/wiki/Finding-Elements#locating-elements