Download to read offline
Uploaded byvodqancr
PPTX, PDF186 views
Tests supporting multiple mobile platforms
The document discusses requirements for automating tests across multiple mobile platforms and proposes a framework to address these requirements. It recommends using Cucumber as the test framework, Calabash as the driver, and Ruby as the implementation language. The framework uses a single test layer that invokes a single flow while respective libraries handle user actions. It has a page object model architecture with loose coupling between layers. A demo is provided and benefits highlighted include support for multiple contributors and replacing/removing utilities.
Related topics:
More Related Content
What's hot
Viewers also liked
Similar to Tests supporting multiple mobile platforms
Tests supporting multiple mobile platforms
- 1. Support Automation forMultiple Mobile Platforms Prasad Kalgutkar & Nikhil Jain vodQA NCR
- 2. Agenda... Requirements for mobileautomation Eureka! And the concept is... Demo of the concept Take-aways of the session! 2
- 3. Requirements for mobileautomation Fast pace adoption of mobile technology 3
- 4. Requirements for mobileautomation Rapid evolution of tools & libraries 4
- 5. Requirements for mobileautomation Support for different platforms 5
- 6. Requirements for mobileautomation A Flexible framework in all aspects 6
- 7. A thought tomeet our requirements Single Test Layer ⇒ Invokes single flow implementation ⇒ Respective library do user actions 7
- 8. Technologies chosen for solution The Stack! ■Rake as an executor ■ Cucumber as the Framework ■ Calabash as automation drivers ■ Ruby as the implementation language Other Needs! ■ Tests run on Devices / Emulators / Simulators ■ Strong foundation of Object Oriented Programming!! 8
- 9. Demo Believe what yousee!! 9
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. Calls to serviceof Page Objects... 1 5
- 16.
- 17. Elements for useraction 1 7
- 18.
- 19. Magical code ofDriver 1 9
- 20. Take-aways... Single Test Layer NoMirror Scenarios Supports Multiple Contributors Agnostic of implementation Plug-n-Play of Utilities Add/Update new versions of utilities Replace/Remove existing utilities Futuristic approach Muscle power of OOPs Loosely coupled components 2 0
- 21. THANK YOU Nikhil Jain jnikhil@thoughtworks.com -------------------------------------------------------------------- PrasadKalgutkar prasadk@thoughtworks.com