@DylanLacey have a look at this, it's a gotcha of working with sim paths. My iOS SDK version might be '7.0', but the directory might be '7.0.3', or '7.0.3-64', so I changed this to use the directory finder from settings.js, and to throw a warning if there are multiple dirs. Unfortunately this change makes the unit tests rather impractical since it really depends on getting the status of the filesystem, so I added a new functional test and removed the unit tests.
Also verified tests pass now on 6.1, 7.0, and 7.1 with these changes
`mobile: pullFile {:path => '/Some/Path'}` fetches a file relative to
the root of the device's filesystem.
`mobile: pullFile {:path => '/Applications/Some.app'}` fetches a file
relative to the root of that Application's .app directory, adding in the
GUID.
Fixes#2010, #1807
Every entry in `Capabilities.capabilityConversions` is now used to
convert capabilities into the args array.
Change version to versionVersion.
Change device to platformName
Stop aliasing platformVersion to version in Capabilities.js
Change from tag_name to class_name for u\_i\_catalog, simple\_test,
cucumber tests.
Changed to iOS 7.1 in u\_i\_catalog, simple\_test, cucumber tests.
Changed `capabilities` to `desired_caps` to avoid some weirdo
collisions.
Remove Debugging output from Cucumber.
Add example of send\_keys as an action chain for u\_i\_catalog.
Squashed commits:
[fba9410] Making sure toLowerCase() is still used for chrome.js
[0cbfa68] We don't need toLowerCas() for app argument, as it is used for passing CFBundleIdentifier, fixes#2131
Originally, scroll scrolls insider the first ScrollView. However, most of our ScrollViews is CollectionView, or TableView. So, we got error that the ScrollView could not found, although there are multiple "ScrollViews".
We also need to able to scroll insider different scrollviews.
- relies on xpath support for ios pull request
- adds support under the '-real xpath' locator strategy
- deprecates the original xpath strategy, which will be replaced in 1.0
- because we have no way to get a dom fragment starting from an element,
this strategy will only work for root-level queries
Jonathan Lipps