At the BEGINNING Of the project: Yay!! Lets automate and cover all test scenarios!! Lets work towards increasing the test coverage !!smile

After 1 year: Regression suite is too bulky!! I can't maintain it anymore!! Its too flaky!! frown

Does this conversation ring a bell? Well, this is a common scenario in projects. The UI test automation starts as a saftey net and then becomes a trap net! 

Heavy Functional tests layer → Long execution time → Low confidence → Problem of Maintainence

 

This talk will address these problems in an Agile project. Some solutions that worked in our team. How working as a Team would help prevent these problem?

 

 
27 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

 

  • Common mistakes in a life of TEST.
  • Preventation is better than cure! 
  • Test automation is a TEAM responsibilty not only QA responsibilty.
  • What will a QA do then? 

 

Learning Outcome

Pragmatic approach towards test automation

Looking at a bigger picture of test automation

Importance of test pyramid.

How testing should be more of collaborative effort than an individual effort

Target Audience

Quality Analyst, Developer, Agile team

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Sailee,

         Thanks much for the submission.  Have you delivered this presentation before?  If so, could you please link to a deck or video.

    What do you think are one or two concrete things that attendees to your sessions could apply to their work the next week?

    Best,

    Joel

    • sailee
      By sailee  ~  2 years ago
      reply Reply

      Hey Joel,

      I haven't delivered this presentation before. I am writing a blog around the same though. 

      The talk intends to :

      1. Make the audience retrospect on their current automation approach. 
      2. Also, it will widen their prescepctive around test automation. It would mean in coming days they won't directly jump upon writing a UI tests but think about the right layer the tests should be covered in. 
      3. This will also help them reduce test duplication across layers.(this will be a longer outcome of the process)
      4. Also, this talk promotes the AGILE ideology of WORKING AS A TEAM. 
      • Joel Tosi
        By Joel Tosi  ~  2 years ago
        reply Reply

        Hi Sailee,

           Thanks much for the update.  As this is a new presentation for you, perhaps we could simplify the talk down some?  If it is an experience report, then we can look at it slightly different.  If it is a talk, then I would suggest focusing more on that problem statement - UI Automation is too easy and causes problems; if you find yourself going down that road - here is how you know and here is what to do about it.

        Does that make sense?  It would give your presentation a more direct, cleaner feel I believe.

        Let me know if that helps any

        Best,

        Joel

  • Niranjan N V
    By Niranjan N V  ~  2 years ago
    reply Reply

    Hi Sailee,

    Thanks for the topic submission. Is your talk is based on experience.

    It might be good idea based on your  experience if you can mention, what quantified results, this practice has yielded?

     

    Best regards

    Niranjan

     

     

    • Radhakrishnan
      By Radhakrishnan  ~  2 years ago
      reply Reply

      Hi Niranjan,

      Thanks for the comment. 

      I have worked on a project where we had just one UI level test but a lot of tests on the lower layers. On that project, we were able to go to production every day. This practice has helped in achieving CD without compromising quality. 

      In the talk, we would share our current experiences as well. 

      - Radhakrishnan

       

      • Jerry Rajamoney
        By Jerry Rajamoney  ~  2 years ago
        reply Reply

        Hi,

        It will be really great if you could share data before and after this approach so that the participants can get more value

        Thanks,

      • Niranjan N V
        By Niranjan N V  ~  2 years ago
        reply Reply

        Hi Radhakrishnan,

        Thanks for the response. If you have any data to back up the improvementseen in CD,  it would be good.

        most of the audience would  be keen to know the quantifiable data.

        Regards

        Niranjan

        • sailee
          By sailee  ~  2 years ago
          reply Reply

          Hey Niranjan,

           

          Thanx for your valuable inputs.

          We were planning to incorporate data around how number of UI tests affect delivery. Also,how frequently we can deploy to production by just tweaking around our frameworks.

           

          - Sailee & Radha (pairing)


  • Liked Niranjan N V
    keyboard_arrow_down

    Mr.Agile Leader - “ Develop People or Solutions”

    Niranjan N V
    Niranjan N V
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    Based on my experience of coaching/ training agile teams for 5 years, one of the important reasons for agile teams are impacted, is the personal leadership style of Agile Leaders(Scrum Master, Senior Managers etc) . I have summarized following, factors or impediments for creating effective agile teams

    • The agile teams effectiveness depends on personal leadership style of agile leaders(Scrum Masters, Senior Management etc)
    • Often Agile leaders focus more on “delivering solutions” than “developing people”.
    • Agile leader need not specify work requirements, all that team needs is - empowerment, autonomy to work.
    • The agile team needs more support through mentoring, coaching from agile leaders to exhibit the culture “Being Agile” than “Doing Agile”.
    • Agile leaders need not be an Expert to coach agile teams.
    • Agile teams needs to be taught on Identifying Problem, Problem solving skills and corrective actions and demonstrate steady, small and continuous improvement.

     

    My inspiration to write here, is derived from the book “ Managing Excellence” by David Bradford and Allan Cohen, and reading blogs, articles along with my own experience.

     

    The entire presentation will be done in “Pecha Kucha Style” with less words and more background pictures, in each slide. The most of the message is conveyed through pictures. The presenter will talk maximum 30 secs on each slide. The slides keep changing automatically after 30 secs, so that presenter continues the discussion in the next slide automatically

  • Sriram Narayan
    Sriram Narayan
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:

    1. Why plan-driven IT projects are a bad idea why we need value-driven projects instead
    2. Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
    3. Why IT budgeting needs to change from being project-based to being team-capacity based
  • Anand Bagmar
    Anand Bagmar
    schedule 2 years ago
    Sold Out!
    60 mins
    Case Study
    Intermediate

    The key objectives of Organizations 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 and Enterprises need to implement to enable CD. Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful.

    Testing in Organizations on the CD journey is tricky and requires a lot of discipline, rigor and hard work. In Enterprises, the Testing complexity and challenges increase exponentially.

    In this session, I am sharing my vision of the Test Strategy required to make successful the journey of an Enterprise on the path of implementing CD.

  • Liked Vinod Kumaar R
    keyboard_arrow_down

    Build it like sports teams

    Vinod Kumaar R
    Vinod Kumaar R
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Is it easy to get a crash course in football by Pele or Maradona for a week and produce a world cup winning football team?

    Answer is NO. Then why do lots of people in the corporate world think of hiring scrum trainers & expert developers to train their team for a week and then expect their team to undergo a transformation at a magical scale?

    German football team made it a point to transform their team and it took them a lots of years before they were able to reach the pinnacle. A quick side by side comparison of what is causing agile transformation to fail.

    Vision

    Football: Someone was there owning this entire transformation, the German football association spent a lot of time identifying talent in their teens and groomed them.

    Office: In the corporate world switching jobs every few years have become common, but there is no passing on of the context, resulting in the new person taking charge, starting from all over again, as well as frustrating existing good performers who have to rebuild the perception.

    Infrastructure

    Football: Players expecting state of the art training facilities, fitness programs and new shoes are not a luxury, it is a necessity.

    Office: Computers have become so cheap compared to the salaries, yet the policy of providing the best tools and good work environment are archaic.

    Coach vs Management

    Football: Coaches are given their due powers to help the team achieve the goal. It is very easy for anyone to comment on how professionals should play their game, there would be no use adhering to the metrics if the team cannot win. Winning is the only measure for management.

    Office: Often coaches are seen as part of the management or management tries to heavily influence coaching which results in a team which will work either for metrics or to please higher ups without the actual result that it had aimed for.

    Training

    Football: Just the ability to kick the ball does not make a footballer. Training will be introduced to increase physical strength & stamina, better mental wellness, injury prevention, tactics and strategy.  A heavy investment is made in the training facilities.

    Office: In the software industry a generation is about 2-3 years. Computer science degrees are nowhere near what is state of the art in the industry. At many places the on boarding process is either very shallow or not up to date with the recent developments, leaving people to learn most of the things hard way. Given too many things to learn and the information overload, this results in inefficient learning and application of knowledge on the job. We need to prepare people to find answers that are not available on Google.

    Team composition

    Football: Rookies don’t learn by watching greats from the bench, instead they play along with the veterans. Every sports team makes sure to have the right composition with a mix of rookies, emerging players and veterans. That is how they sustain a winning team.

    Office: Architects and Leads often do not code or are not part of the team every day, this means that most of the time the team just looks up to for advice or waits for reviews. There should be a good mix of people at all experience level so that there are enough people to try new things, enough people who have mastered few things and enough people who challenge change.

    Above all – Persistence

  • Liked Gautam Rege
    keyboard_arrow_down

    Don't test your code!

    Gautam Rege
    Gautam Rege
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Testing is overated. Let's correct that statement - "Manual Testing is overrated". In this this talk, I plan to take you on whirlwind tour of why an Agile outfit does not need manual testing at all and how to get fantastic Quality Assurance without manual testing.

    In this talk - I outline a agile process with a difference - everyone is a developer and a tester. However, there is no dedicated QA people. In fact, this process does not require anyone other than the developers and one process/product owner.

    Development using a central repository like Github that is integrated with a Continuous Integration service (like Travis, CircleCI or Semaphore) and further integrated with a Code Quality checker like Code Climate or Pull Review is part of the automation trick. Then comes the development processes like pull request between branches (enabling peer code review) and Automated Deployment to a staging server.

    Finally, the pixel perfection or meeting product specificaiton via Project Management tools (which are integrated with the Code repository) gives the product owner (or the client) complete confidence in not just the functionality but also the quality of the code. 

    This approach can be applied to evolving products too and I discuss how to work in short sprints that always keep changing and guarantee that "The product owner gets the money's worth and the development team gets their works worth!".

     

  • KK Sure
    KK Sure
    Sheril Jebasingh
    Sheril Jebasingh
    schedule 2 years ago
    Sold Out!
    20 mins
    Case Study
    Intermediate

    Traditionally, in software development, user experience (UX) wasn't valued as much as developing of the software itself. But this has changed rather radically. However, creating an enriching user experience in an agile fashion is still challenging. Most of the agile engineering practices in use are around building software but seldom address UX. When building a product in an agile fashion, UX in an incremental fashion becomes important.

    In this talk, we will present our experience of creating UX in an incremental fashion for a virtual wallet. We will also talk about the different challenges we faced such as, educating various stakeholders on the value of incremental UX, building collaboration between developers and experience designers and abstracting design components, along with the solutions we devised to tackle these challenges.

  • Sneha Kadam
    Sneha Kadam
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

  • Krishnan Nair
    Krishnan Nair
    KK Sure
    KK Sure
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    We've come far in our journey of Agile as a software development methodology. From stand-ups to showcases to sprint planning meetings to burn-ups (or downs), we've got it down pat when it comes to processes to follow to be considered Agile. However this heads-down, process defined agile, often hinders real agility required to meet business needs. Is doing a three hour sprint planning meeting every week the most important thing to do when you have to get a minimal-viable-product out in the market? How much of automated functional testing should you do when you know that your product's beta version is only going to validate assumptions of your business idea? Should you write tests at all? There is no formulaic answer.

    In this talk, KK and Krishnan will talk about their experience of how much Agile is too much Agile. We look at how to find the right balance between following agile practices and being responsive to your business. How much agile is too much and how less is too less?

    We will do this by looking at:

    • A couple of successful agile adoption stories
    • Look at why agile was successful in the contexts above
    • Discuss why this success will limit us if we are not careful
    • Talk about a start-up and how the things that led to success in the first 2 stories limited us in the start-up context
    • Look at approaches to understand what agile practices/processes to follow to be business agile
    • Close by summarizing the challenges facing agile (as we see it) and how success in process agility will limit us in business agility
  • Liked Chirag Doshi
    keyboard_arrow_down

    1000 Words - Illustrating Project Challenges with Visuals

    Chirag Doshi
    Chirag Doshi
    schedule 2 years ago
    Sold Out!
    80 mins
    Workshop
    Intermediate

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).

  • Priti Biyani
    Priti Biyani
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    We do have test pyramid in our project to gain confidence on the code we will be delivering. We have also smoke tests, which will give us quick feedback. Still I'm saying Automate all the things!

    What??

    Well, yes! In agile world, there is a theme of ruthless automation. But in my opinion, we don’t push this principle nearly enough.

     

    In this talk, I will share some of my expereinces and some interesting things which we never thought we could automate. Yes, We can automate everything!

  • Pooja Salpekar
    Pooja Salpekar
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    “When deploying and administering large infrastructures, it is still common to think in terms of individual machines rather than view an entire infrastructure as a combined whole. This standard practice creates many problems, including labor-intensive administration, high cost of ownership, and limited generally-available knowledge or code usable for administering large infrastructures.”— Steve Traugott and Joel Huddleston

    Server infrastructure has traditionally lagged far behind our development practices in terms of code quality, testing, continuous integration and continuous development.

    When you write your Chef recipes or Puppet manifests or any other CM, you are coding, and every code is prone to defects. All of us understand the benefits of test-driving the application code. The same applies to your infrastructure code. Testing becomes even more significant in case of deployments spanning large clusters of nodes.

    Test-driving allows the infrastructure teams to have confidence that their configuration changes are being applied as intended across many different systems, and having the intended effect. This allows the whole system to be trusted, and then updated without fear for introducing breaking changes or otherwise causing instability.

    The objective is to cover agile lifecycle of infrastructure code and provide a quick demo of how to test drive infrastructure management code. 

  • Liked Sreedevi Vedula
    keyboard_arrow_down

    Infrastructure As Code - The secret sauce for Continuous Delivery

    Sreedevi Vedula
    Sreedevi Vedula
    schedule 2 years ago
    Sold Out!
    60 mins
    Demonstration
    Intermediate

    Developing Infrastructure as Code as a practice is increasingly adopted by organizations that want to have Continuous Delivery. Infrastructure As Code requires treating infrastructure as code, applying the same development techniques that one uses to build application software. This talk discusses the need for having infrastructure as code, the several frameworks available in this space (like Puppet, Chef, Ansible), what they bring to the table and the philosophical differences between them and the testing tools and frameworks available to test infrastructure as code. The concepts would be supported by snippets of infrastructure code written for an open source application.

  • Liked Radhakrishnan
    keyboard_arrow_down

    Use it to test it

    Radhakrishnan
    Radhakrishnan
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Given you have a PRODUCT to test

    When you start testing it

    Then STOP testing it

    And start USING it


    In this talk I would like to address how important it is for the whole team to use to product to see the good, the bad and the ugly side of the product you are building which are otherwise unknown to the team until they go live.

  • Shiwangi Prasad
    Shiwangi Prasad
    schedule 2 years ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    As a tester in an agile model of software development team, I felt the need to have an automated mechanism of getting fast feedback on my growing application. This talk is to share my learnings on the set up, configuration and various processes followed in this automation. The benefits of having a CI and automated test runs, their set ups will be shown through a demo.

     

  • Liked Sreedevi Vedula
    keyboard_arrow_down

    The Practical Pyramid

    Sreedevi Vedula
    Sreedevi Vedula
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    An Ideal Test Pyramid is an invaluable technique to succeed with agile. However, it is challenging to have this ideal pyramid in practical projects for several conditions in the projects, like legacy code bases. To have a good test pyramid, several best practices of software development need to be followed. This talk discusses the practices that help in implementing test pyramid and the challenges faced by many teams in doing that and suggestions on how to overcome them.