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!

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

Outline/structure of the Session

  • Why Automate all the things?

  • hmm, title is self explainatory, but why it's necessary?

  • I am BA, how it will help me?

  • I am QA, how it will help me?

  • Some of my experinces in project.

  • Well, It's not role specific..! It's for everyone .. 

  • How I will benefit from this?

  • Think, Learn and automate all the things!

Learning Outcome

  •  When you repeat, think!

  •  Try to find, if you can automate something around it!

  •  Stay calm and automate all the things!  

                          

 

Target Audience

anyone who will love to ease mundane tasks!

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Niranjan N V
    By Niranjan N V  ~  2 years ago
    reply Reply

    Hi Priti,

    Thanks for the submission.

    It would be great if you can highlight/share  the speific techniques  you had tried in "Automation".

     

    Also, may be if you can give breakup of time, it might help.

     

    Regards

    Niranjan

    • Priti Biyani
      By Priti Biyani  ~  2 years ago
      reply Reply

      Hi Niranjan, 

      Thanks for going through propsal.

      I haven't used any special technique in regular work. What I did is, tried to adopt one of the principle of Agile, "automate all the things!".

      What I meant by this is, in regular manual testing, we do tend to repeat some actions, where we miss out on somethings and result becomes unambiguos. To avoid this human error, it is always beneficial to automate such things. 

      There is cost overhead involved in creation and maintence of such things. But it's always helpful to automate, as it speeds up task, less error prone(if you test properly ;) ) and you learn along side!   

      I have shared my thoughts on this here: http://pritibiyani.github.io/blog/2014/11/25/automate-all-things/.


      This technique is not role specific, it's a thinking we should adopt. For BA, the repeatative task would be different and so for PM. But there is always way of automating or doing things faster.

       

      I am planning to show:

      1. Some of examples where we could have automated, but we don't. We just rely on exisitng tools and dont be agile!
      2. How it's easy to automate such things!
      3. What are different ways where you could think, you can automate! 
      4. Some of the examples(form filling bookmarklets, using scripts, selenium etc.)
      5. How simple tools such as alfred, chrome profiles, can be useful!
      6. How it helped me and hence team! 

       

  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Priti,

        Thanks much for the submission.  Could you please provide some concrete examples of learnings that you will address?  Also, automation can be very expensive and fragile, especially as you go up the pyramid.  How do you address that?

    Best,

    Joel

    • Priti Biyani
      By Priti Biyani  ~  2 years ago
      reply Reply

      Hi Joel,

      I have shared my learnings and my experience here:  http://pritibiyani.github.io/blog/2014/11/25/automate-all-things/.

      I do not want to address test pyramid, it's about general practice we should be following to ease any tasks and drudgery. I have enjoyed doing this apart from test suite we have! This will not only help you speed up tasks but also give you better insights.


  • 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 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.

  • 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!).

  • 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 sailee
    keyboard_arrow_down

    UI Automation : Safety Net to Trap Net!!

    sailee
    sailee
    Radhakrishnan
    Radhakrishnan
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    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?