The document discusses the automation of mobile applications using Calabash for both Android and iOS, emphasizing the advantages such as cross-platform support and the use of Ruby with Gherkin syntax. It outlines the installation process, launching tests, and the framework's capabilities while addressing the advantages and disadvantages of the implementation. Additionally, it suggests avoiding code duplication and highlights the integration of Calabash with server-side operations, ending with a link to a related blog for further resources.

1. Calabash Andoird + Calabash iOS
automated testing of mobile applications

2. Is it time to automate?

3. Tools
Android iOS
Calabash Android Calabash iOS
MonkeyTalk Frank
Robotium UIAutomation
Selendroid KeepItFunctional
UIAutomator ios-driver

4. Which tool to choose?

5. Which tool to choose?
The key factors
● Ruby on Rails server
● Cross-platform support (Android, iOS)
● framework updatability
● running on real devices

6. Calabash. Adavantages.
● Calabash Android
● Calabash iOS
● Ruby
● Gherkin Syntax (Cucumber style)
● Calabash Android last updated - 26 days ago
● Calabash iOS last updated - a month ago
● Testing on the real devices

7. Calabash iOS. Installation
# Install calabash ios gem
$ gem install calabash-cucumber
# Generate a features dir
$ bundle exec calabash-ios gen
# Install calabash.framework to .xcodeproj
$ calabash-ios setup

8. calabash-ios gen

9. calabash-ios setup
● Generates calabash scheme for iOS project.
● Connects calabash.framework to our project (testing
server)

10. Runnig tests. iOS
To run on physical device:
● BUNDLE_ID=com.anadea.***
● DEVICE_ENDPOINT=http://192.168.100.85:37265
The launch command:
$ bundle exec cucumber

11. Calabash Android. Installation
# Install calabash Android gem
$ gem install calabash-android
# Generate a features dir
$ bundle exec calabash-android gen

12. calabash-android gen

13. Running tests. Android
The launch command:
$ bundle exec calabash-android run <path_to_apk>

14. Duplicate ourselves
iOS
sign_up.feature
sign_up_steps.rb
sign_up_screen.rb
Android
sign_up.feature
sign_up_steps.rb
sign_up_screen.rb

15. Design of the applications
iOS Android

16. WTF...

17. What to do?
● install gems on the server side
● split PageObject into moduls
● stick together calabash-ios & calabash-android launchers

18. Stick

19. Split into moduls

20. Modified scheme
iOS + Android
sign_up.feature
sign_up_steps.rb
ios
sign_up_screen.rb
android
sign_up_screen.rb

21. The launch commands
iOS
cucumber CLIENT_PLATFORM=IOS
Android
calabash-android run <path_to_apk>
CLIENT_PLATFORM=Android

22. The advantages of implementation
● there is no duplicate code (*.feature, *_steps.rb)
● possibility of easy access to objects via ActiveRecord
● emulation of the second client working on the server side

23. The disadvantages of implementation
● different launch commands (cucumber, calabash-android run)
● it is not possible to work in the debug mode, provided by calabash (remedy is
binding.pry :) )

24. Getting rid of disadvantages
CALABASHER
(include calabash-ios & calabash-android)

25. Visit our blog for more great tips:
anadea.info/blog