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 2 years ago

Public Feedback

    • Jagmit Singh

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

      45 Mins

      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.

    • Naveen Khunteta

      Naveen Khunteta - Best Practices to implement the test automation framework starting from Design - To -> Infrastructure - To -> Execution.

      45 Mins

      Best Practices - How to get the best 'Return ON Investment' (ROI) 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. Test Automation Practices:
      • Design Patterns (Web/Mobile/API)
      • What to Automate/Not to Automate
      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 and 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
      • Static Code 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. 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 (use of Selenoid, GRID on Cloud)
    • Oren Rubin

      Oren Rubin - Codeless automation - the definitive guide

      Oren Rubin
      Oren Rubin
      Founder and CEO of Testim
      schedule 2 years ago
      Sold Out!
      45 Mins

      As codeless automation tools rise (again) in popularity, will record and playback disappoint us again? We'll take a deeper look into what is vs. isn’t possible from codeless solutions. We’ll then discuss some approaches to fill the gaps where codeless solutions fall short.

    • Sameer Arora

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

      Sameer Arora
      Sameer Arora
      Lead Quality Engineer
      schedule 2 years ago
      Sold Out!
      45 Mins

      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.

    • Andrew Murphy

      Andrew Murphy - Leadership Antipatterns - A guide on how to alienate and dis-empower your team

      90 Mins

      There's a huge problem in our industry, I call it "inertia-driven leadership".

      We promote our "rock star" engineers, with their excellent technical skills, into leadership positions; then we sit back and watch as they fail.

      We wonder why they fail at leadership but the answer is simple, we don't support them to improve their people skills!

      In fact, we often don't even help them realise that the role of a "senior developer" is drastically different to that of a "leader"

      What we can we do to stop inertia in our new leaders?

      How can we support them to learn the soft skills they need?

      How can we position with them that those soft skills are important to their career?

      That is what we will discuss in this session.