In this talk, I will speak about the process and strategies on how can one analyze and select the right tools for test automation. We will look at some tools and processes that help to select the tools, frameworks, libraries, etc.

I will demonstrate some helpful extensions and tools that will be very handy and useful during the process

This process can be carried out before every test automation project or engagement. The selection of the right tools will help throughout the process of automation and will help to avoid delays, changes, re-work, incomplete automation, etc. and will save a lot of time, effort and resources for the organization.

The session is designed for anyone in the Software Testing industry and the knowledge received from this session can be implemented right away in any of the upcoming or existing test automation projects.

 
 

Outline/Structure of the Talk

  1. What is an Automation Tool
  2. Why is the selection of the right tools is important
  3. What happens if this analysis is not done
  4. Strategies and process
  5. Requirements analysis
  6. Categorization
  7. Analysis of basic, technical and business requirements
  8. How to check the technology stack of the application
  9. Features and support
  10. How to create a list
  11. How to filter the list and shortlisting process
  12. Comparison-charts & scorecards
  13. Retrospective analysis
  14. POC (Proof of concept) and Tips

Learning Outcome

  1. Participants will get awareness on different strategies and processes involved to select the right tools for automation
  2. How to plan well in advance to avoid issues later in test automation projects
  3. Attendees will be equipped with the knowledge and process of selecting the right tools for test automation
  4. Participants can implement this knowledge right away in any of their upcoming automation projects

Target Audience

Anyone in the field of Software Testing

Prerequisites for Attendees

Basic knowledge of STLC (Software Testing Life Cycle) will help

schedule Submitted 1 week ago

Public Feedback

comment Suggest improvements to the Speaker
  • Shubhodaye H G
    By Shubhodaye H G  ~  2 days ago
    reply Reply

    Very useful... Can't wait for June... :) !!! I am sure each one of the tester will be interested in this topic... As software getting more and more complex testing will only adds to further complexity by x times...  I am glad that you bought this topic ! 

  • Kayleigh Jenkins
    By Kayleigh Jenkins  ~  6 days ago
    reply Reply

    Must needed topic for any project in quality perspective and I am sure Naveen can do it with ease.

  • Alan Phillips
    By Alan Phillips  ~  1 week ago
    reply Reply

    I really liked the topics chosen, and i am looking forward to it.

    All the best!

  • Emma Brown
    By Emma Brown  ~  1 week ago
    reply Reply

    It's a challenge to choose the best testing tool for my team. Hope I can have more insights from your talk, Raghav. 

  • Agustin Mancebo
    By Agustin Mancebo  ~  1 week ago
    reply Reply

    That's all I need right now. Thank you for the upcoming topic, Raghav. 

  • Saman Thomas
    By Saman Thomas  ~  1 week ago
    reply Reply

    Such an interesting and helpful topic. Can't wait to see you at the conference, Raghav. 

  • Lukas Sobisek
    By Lukas Sobisek  ~  1 week ago
    reply Reply

    Select a right testing tool can help us save a much time and effort. I love this topic (y) 

  • Sanyam Reddy
    By Sanyam Reddy  ~  1 week ago
    reply Reply

    I believe that this topic will be helpful for a lot of people.

    Hope I can find out the best testing tool for myself. 

  • Pateek Kumar
    By Pateek Kumar  ~  1 week ago
    reply Reply

    Choosing the right tools for my test project is always a headache.

    I'm really excited about the topic you will bring to the Conference.

    Can't wait to see it. :D

     

     

     


  • Liked Naveen Khunteta
    keyboard_arrow_down

    Naveen Khunteta - Best Practices to use Selenium in Real Time Projects. How to leverage your Test Automation, get the best 'Return ON Investment' from your Test Automation.

    45 Mins
    Talk
    Intermediate

    Best Practices to use Selenium in Real Time Projects. How to leverage your Test Automation, get the best 'Return ON Investment' from your Test Automation.

    This has been observed that, most of the test frameworks wont be able to survive due to lack of expertise, no maintenance, no best practices being followed, and finally your test automation will be dead after few months, and there is no "Return ON Investment" from this. This is the most common problem, most of the companies are struggling and finally back to square to the Manual testing.

    My proposal : HOW to leverage your test automation in terms of best practices, best ROI, and how to adopt best automation culture in your organisation.
    I strongly propose some of the important points/suggestions to achieve this in your Organisation/Team.
    1. Best Test Automation Practices:
    • Best Design Patterns (Web/Mobile/API)
    • What to Automate/Not to Automate
    • Best Design Patterns
    2. Common Automation Frameworks at Org Level:
    • How to design Generic Utilities, Libraries and different Components, which can be suitable for all the teams in the same Org.
    • Best practices to design your Tests (Automation).
      • Common Design Patterns
      • Common application level libraries
      • Common Page Libraries
      • Best Practices to use Assertions in your Tests (How and What to write for assertions). Most of the people don't write proper assertions and this is making your test unreliable and no defects found during execution.
    3. Inclusion of API/Backend libraries in your UI test automation as an external Maven/Gradle Dependencies to avoid un-necessary tasks, some of the important points to be considered here:
    • User Creation from APIs (No need to automate user creation from web/app for all the test cases)
    • API tests are stabled most of the time
    • API calls takes lesser time as compared to web, hence include API calls in your UI/App framework to save time.
    • Less flaky test

    4. Best Code Review Process (Do not merge your code into Master without proper Code Review)

    • Implement PR (PULL Request) Process
    • Peer to Peer review
    • Static Analysis using SonarQube, Cobertura, JACOCO etc..
    • Get the benefits of Best Test Automation Quality Matrices
    • Sometimes, Manual (Functional Tester) should review your code (Assertion, test steps and use cases) to get the best coverage
    5. Quality is A Team responsibility:
    • Developers, POs, Manual QEs and Automation engineers should be included to get an overview of test automation coverage.
    6. Maintenance of the Frameworks
    • After couple of months, it should not make your life miserable if you don't maintain your libraries and framework properly.
    • Do not use Hard Coded values, make it simple and Generic.
    7. Common Automation Frameworks:
    • Core/TCOE/R&D Team should provide the common automation libraries, generic methods, utilities, best reporting tools at the Org level. Common best practices should be followed at the company level.
    8. Infrastructure Setup for Test Design and Test Execution:
    • Proper Browser - OS lab setup
    • Proper Mobile Labs setup with different Devices - IOT, iOS, Android, iPad, Tablets
    • Proper CI - CD common configuration using Jenkins, Dev Ops, AWS, Docker and Cloud setup
    • Handling multiple Docker nodes using Kubernates
  • Liked Sameer Arora
    keyboard_arrow_down

    Sameer Arora - Triggering alerts on Slack along with screenshots in case of test case failure

    45 Mins
    Demonstration
    Beginner

    One of the biggest limitations with most of the frameworks in selenium is that we need to wait till the end to get the final test case report. Only then we can raise the alert that a particular functionality is broken. By then, it may be too late! In addition to this, in most of the frameworks, the HTML report generated is hosted on our company's private network and we need to connect to the VPN if we are outside the office to open the report and check the related screenshots to see which test case has failed and why.

    So, why not raise an alert as soon as the test case fails? And why not attach a screenshot along with that alert so that all the stakeholders can actually see what has failed in the application?

    In this session, we will learn a simple yet a really useful way of sending an alert along with the failed test case screenshot by integrating slack with selenium which will help us alert all the stakeholders as soon as an automated test case fails so that everyone can react to it immediately and the damage will be minimised.

  • Liked Jagmit Singh
    keyboard_arrow_down

    Jagmit Singh - Simplify Test Automation using Katalon Studio - Avoid Reinventing the Wheel

    45 Mins
    Talk
    Intermediate

    In this talk, Jagmit will explain with a demo as why to use Katalon Studio for API, Web, Mobile, and Desktop Automated Testing. Katalon Studio is built on top of the open-source automation frameworks Selenium, Appium with a specialized IDE interface. Frequently, Agile teams struggle with development, enhancement and maintenance of Custom Automation Framework. How does Katalon Studio help the end-users overcome these challenges and complexities? Katalon Studio comes with cool features e.g. pre-built keywords, integrations, multi-browser and cross-platform support. Because of Katalon Studio’s user-friendly features, manual testers with little to no programming skills can also contribute towards test automation.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Anand Bagmar - Visual Validation - The Missing Tip of the Automation Pyramid

    45 Mins
    Demonstration
    Intermediate

    The Test Automation Pyramid is not a new concept.

    The top of the pyramid is our UI / end-2-end functional tests - which simulate end-user behavior and interactions with the product-under test.

    While Automation helps validate functionality of your product, aspects of UX validations can only be seen and captured by the human eye and is hence mostly a manual activity. This is an area where AI & ML can truly help.

    With everyone wanting to be Agile, make quick releases, the look & feel / UX validation, which is a slow, and error-prone activity, quickly becomes a huge bottleneck. In addition, with any UX related issues propping up cause huge brand-value and revenue loss, may lead to social-trolling and worse - dilute your user-base.

    In this session, we will explore why Automated Visual Validation is now essential in your Automation Strategy and also look at some popular tools that can help solve this problem.