Behavior Driven Development - Creating a Robust Mobile Test Framework using Appium, Cucumber-JVM & Page Objects

For teams developing & maintaining mobile apps for both Android & iOS platforms, functional testing is a huge challenge. With the advent of Agile practices, behavior driven testing has gained more popularity. The current process of updating apps over the air is very easy, raising users’ expectations of new features delivered sooner.

Appium has made it easier for teams to test their apps for multiple platforms. However, it alone cannot solve the challenges around implementing behavior driven development & frequent UI/functionality updates. So we created a robust Test Framework combining the best features of Appium, Cucumber-jvm & Page Objects.

Cucumber-jvm is a key tool in implementing BDD. Page Objects is a framework design approach for maintaining & accessing components & controls spread across test scenarios. Appium provides a JSON bridge that allows test cases to be written once, and run for multiple mobile platforms. Integrating the powerful features of these 3 tools, we can create a powerful framework that is easy to setup, use, scale and maintain.


Outline/Structure of the Demonstration

* Introduction to Appium, Cucumber-jvm and Page Objects (5 mins)

* Need for integrating Page Objects with Appium (5 mins)

* Benefits of Integrating Cucumber-jvm with Appium (5 mins)

* Live Demo of working test cases in Appium, Cucumber-jvm and Page Objects (15 mins)

Learning Outcome

After this session, mobile developers & testers will have a better understanding of user behavior requirements & how to apply them in the test life cycle. Testers will gain knowledge on how to setup Appium & Cucumber-jvm and optimize their tests by using Page Objects.

Target Audience

all Agile Enthusiasts :-), QA, Dev, Scrum masters and managers

schedule Submitted 8 years ago

  • Anand Bagmar

    Anand Bagmar - Enabling Continuous Delivery (CD) in Enterprises with Testing

    60 Mins
    Case Study

    The key objectives of any organization is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!

    In such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury!

    There are various practices that organizations need to implement to enable CD. Changes in requirements (a reality in all projects) needs to be managed better. Along with this, processes and practices need to be tuned based on the team capability, skills and distribution.

    Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful. But, this is tricky and requires a lot of discipline, rigor and hard work by all the team members involved the product delivery.

    All the challenges faced in smaller organizations get amplified when it comes to Enterprises. There are various reasons to this - but most common reasons are - scale, complexity of the domain, complexity of the integrations (to internal / external system), involvement of various partners / vendors, long product life-cycles, etc.

    In such situations, the Testing complexity and challenges also increase exponentially!

    Learn, via a case study of an Enterprise, a large Bank, the Testing approach required to take them on the journey to achieving CD.

  • Prasad
    schedule 8 years ago
    Sold Out!
    45 Mins
    Experience Report

    With business agility the new watchword in senior management circles, more and more enterprises are looking for ways to adopt ‘agile’ into their technology practices. However, such an initiative needs to go beyond the mere adoption of agile in a few projects. To successfully implement enterprise IT agility, organizations need to understand the impact of agile across functions and groups, develop frameworks to sustain agile, empower teams across the board to work in an agile fashion, and invest in the right infrastructure. A strategic roadmap based on these considerations can help organizations infuse agile into their practices, processes and systems, thereby achieving true benefits of agile – faster returns, better quality and quicker time-to-market.

    This session  discusses the critical factors for an effective roadmap to implementing enterprise IT agility. It also outlines how these factors contribute to a successful enterprise IT agility strategy.

  • Om Prakash Bang

    Om Prakash Bang - Agile Business Analyst and Product Backlog Management

    45 Mins

    Agile Product development with Scrum is based on completing a set of User Stories within a time-box called a sprint. Stories describing user functionality. Conversatin with customer is the means of elaborating requirement. looks simple, right?

    Only User Stories are enough for product development? If not, what all other documents are necessary and how these are progressively elaborated? 

    What's required before agile team start sprinting? What are the challenges while transitioning from waterfall to agile related to product requirement?

    What's the role of Business Analyst in agile? BA moving into an agile team, moving to Product Owner? Can Business Analyst and Product Owner co-exist?


  • Smita Mishra

    Smita Mishra - Agile Tester : Change of mindset

    Smita Mishra
    Smita Mishra
    QAZone Infosystems
    schedule 7 years ago
    Sold Out!
    45 Mins


    How you think defines how you act.  Agile is more of a people practice than huge technical methodology. 

    In traditional setup with waterfall methodology where each phase of the projects are serially aligned and more often than not take longer, testing is slow paced and quite reactionary. When moving to an agile setup, it requires a paradigm shift in the mindset. 

    Its important to open our minds towards not only learning more technical but also soft skills and inspire our teams to do so too. Moving from competition to collaboration (with developers), moving from mere bug finding to bug investigation, moving to exploratory testing.

    Emphasis is laid on team members and interactions instead of processes and tools. The idea is to encourage testers to think more about Agile as mentioned in Agile Manifesto than getting blindly into agile projects.

  • Vineet Patni

    Vineet Patni - Lean - Agile: The Eternal Siblings

    30 Mins

    What came first - Lean or Agile? It's a chicken-and-egg question for many. And then, there are beliefs that these two are separated twins.

    If you think that Lean software development and Agile are the same, think again!

    There are both difference and similarities in the Lean and Agile principles and practices.

    During this talk, we will discuss on how Agile and Lean are related or different. Or are they two different names of the same thing? how the principles of Lean and Agile can be leveraged in order to create complex software solutions at enterprise level.