schedule 05:15 PM - 06:00 PM place Grand Ball Room 1 people 3 Attending

We all in the voyage to test effectively always think about test automation & let me tell you, its no less crucial & important than production app code. Its a code/framework/architecture built to test your app code and catch some of app defects. This when placed in an eco-system of continuous integration & deployment takes a next level of importance.

I have been fortunate enough to have had my share of failures & eventually learn out of it while automating. In this session, I wish to take my audience through the importance of automation in Agile, the essentials to think of while deciding the tools and also take some tangible take-aways while writing automation code.

The take-aways will be some technical inputs which have immensely helped me to build flexible frameworks for delivery of enterprise products. The aspects this take-aways will touch are on the pressings issues an automation tester face around test data management, code modularization, defining the clarity on responsibilities of different modules/classes written in an automation framework.

This session will be a good dialogue supported with some live demos for better understanding & overall making us think to stay away from the obvious failures.

 
2 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The structure I plan to do is,

  1. Clear the objective & bring in a crucial perspective of having automation at heart of software delivery. Its as important as app code!
  2. My experience in travel domain for web & mobile app delivery. This also in context of being Agile Tester!
  3. The different challenges and the propose solution for it, (I will take this as a case-study mostly in travel domain)
    1. Test Data Management
    2. Emphasis for inclusivity of testers. Make Automation as your live documentation so even manual testers OR business feels the connect & value addition.
    3. Emphasis on Code Modularization for different components of automation.
      • Driver & its responsibilities.
      • Utilities & Support tasks/patches
      • Try moving towards Page Objects with clearly defined services.
    4. Open mind to refactoring.
    5. Try to write tests for your core framework utilities! This is an important aspect.
  4. Also, seed in some thoughts of how to pitch in for the criticality of automation & getting approved capacity in some rigid organization. This is the most important struggle of a tester.

Learning Outcome

Any one attending the session will surely take below mentioned points & should be able to apply in their corresponding project contexts,

  1. Everyone should feel convinced of automation is not a by product & should be treated well.
  2. A manual tester, project manager would be able to understand the importance of automation in software delivery & how crucial when done in Agile.
  3. An automation coder(Dev or QA), should be able to related some of the challenges they definitely face & apply the learnings suggested in the session.
  4. Anyone doing client consulting should be able to explain the criticality of having a well written, maintainable automation framework & how it eventually helps in delivery.
  5. Continuous Integration demands automation safety nets & this session just adds the right weightage to inculcate good practices!

Target Audience

Manual testers; Automation coders; PMs; Tech leads

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
    • Prasad Kalgutkar
      By Prasad Kalgutkar  ~  1 year ago
      reply Reply
      The alignments have gone for a toss for some reason.. I will update it

       

  • Prasad Kalgutkar
    By Prasad Kalgutkar  ~  1 year ago
    reply Reply

    Hi Anand,

    Yes. I agree. We can shrink it to the 45 minutes slot.

    I have delivered this topic in another conference (Global Test Retreat) within the 45 minutes slots. And I got a sufficient time to have audience interaction as well.

    The overall feedback for the topic was positive as a lot of the audience could relate to the content and points. I will upload the slides & share the link for you.

    And,

    I have mentioned about having demos in my above summary, however, I am uncertain of it as I was able to deliver the intent without it. I will keep you posted if I think of any apt demos to support my talk. Also, I generally video record the demo & play them to avoid on stage glitches.

  • Anand Bagmar
    By Anand Bagmar  ~  1 year ago
    reply Reply

    90 min may be too long for a case study ... attendees may loose interest. how do you plan to keep them engaged throughout the 90 min? Another thought - can you compress this session into 45 min (without losing value from what you intend to cover)?


  • Priti Biyani
    Priti Biyani
    Consultant
    ThoughtWorks
    schedule 1 year ago
    Sold Out!
    90 mins
    Case Study
    Intermediate

    These days we find most of the apps are being developed across different platform, iOS, android, windows and to keep the user base which uses web, mobile web and websites. 

    When apps are being developed for cross domains, most of the functionality provided by the app is very similar, varying thing is PLATFORM. 

     In rapid development cycle, where there are tools which allows you to write once and reuse across multiple platforms, makes development very faster. 
    But at the same time, if we have different automation suite for different platforms, it becomes very difficult to keep a pace with ongoing functionality. 
    This is the exact problem we faced, and the solution we came up with is "One Page to test them all! -A cross platform mobile automation framework! "

     

    Page Object Model

    Well, Page Object Model was again a natural fit for this framework. Most implementations of POM recommend different POMs for each platform. But we wanted to have a single Page Object Model for all the 3 platforms to ensure maximum code reuse and reduce overall time spent in adding new automation.
     

    Single Page Object Model across platforms

    This was complicated because we had native screens as well as webview screens and so it was not possible to use the same Page Object. To solve this, we introduced abstractions for the elements on the screen and encapsulated the respective native driver implementations.

    This also allowed us to implement common automation tasks in one place for e.g waiting for new pages to load, so that this code is not repeated across multiple step definitions and platforms. This helped us move to thinking in higher domain level concepts than in terms of low level UI interactions.

    So, in summary, we write our tests for one platform and run them for all with an abstraction layer in place.

     

     

  • Liked Adam Carmi
    keyboard_arrow_down

    Adam Carmi - Advanced Automated Visual Testing With Selenium

    Adam Carmi
    Adam Carmi
    Co-Founder and VP R&D
    Applitools
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Automated visual testing is a major emerging trend in the dev / test community. In this talk you will learn what visual testing is and why it should be automated. We will take a deep dive into some of the technological challenges involved with visual test automation and show how modern tools address them. We will review available Selenium-based open-source and commercial visual testing tools, demo cutting edge technologies that enable running cross browser and cross device visual tests at large scale, and show how visual test automation fits in the development / deployment lifecycle.

    If you don’t know what visual testing is, if you think that Sikuli is a visual test automation tool, if you are already automating your visual tests and want to learn more on what else is out there, if you are on your way to implement Continuous Deployment or just interested in seeing how cool image processing algorithms can be, this talk is for you!