Choosing the right set of tools and drivers for you test automation framework is one of the most important decisions you will make, but it is not an easy one.

There is a variety of open source solutions available to choose from, each built for a different reasons and purposes while sharing overlapping functionality. Even when evaluating web automation drivers in particular there are many available options including Selenium, Google’s Puppeteer, Nightwatch.js, Cypress.io, and Webdriverio. In designing TestProject, our challenge was even greater due to our mission to address the needs for organizations of all sizes, and for both test automation experts and manual QA engineers. On top of that, we need to be able to support all different technologies and platforms without unnecessary configuration and customization.

I would like to share the thoughts, experience and considerations gained from this 4 year process of building Testproject with the community of test automation experts.

 
 

Outline/Structure of the Case Study

  1. The main factors to consider while choosing the right web automation driver for your organization
    • Organization culture
    • Skill level of resources
    • Existing tools and infrastructure
  2. Review and compare the most popular web drivers (Selenium, Puppeteer, Nightmare, Cypress, Webdriverio)
    • Speed benchmark
    • APIs commands benchmark
    • Compatibility
    • Supported platforms
    • Community benchmark
  3. What are the key factors lead us to choose Selenium web driver for TestProject

Learning Outcome

What are the key factors that should be considered while building test automation framework.

Benchmark and main differences between the top 5 open source web drivers available today.

Target Audience

Test Managers, Test Leads, Test Automation Engineers

Prerequisites for Attendees

Basic knowledge of Selenium and/or Appium, understanding of test automation principles

schedule Submitted 10 months ago

Public Feedback


    • Kevin Dunne
      keyboard_arrow_down

      Kevin Dunne - How to Overcome 5 Common Obstacles to Adopting Open Source Automation

      Kevin Dunne
      Kevin Dunne
      General Manager
      TestProject
      schedule 10 months ago
      Sold Out!
      20 Mins
      Talk
      Intermediate

      Open Source testing tools have long dominated the test automation market, with millions of users leveraging the most popular frameworks such as Selenium and Appium. While these tools offer a promising array of features at a low price point, they often come with a number of new challenges that must be solved to achieve automation maturity. These challenges can surface both with teams looking to implement automation for the first time as well as teams transitioning from established legacy/closed source automation tools. In our experience with thousands of teams adopting open source for the first time, users will face challenges when it comes to:

      • Authoring: how to build the number of tests needed, especially when Agile and DevOps are increasing the rate of new feature delivery. Teams can empower non-technical testers with appropriate tools to widen the number of potential contributors.
      • Maintenance: how to structure tests in the optimal way to reduce test breakage, and limit the amount of time needed to fix broken tests. Teams can utilize a test structure which allows for easy reuse of code to eliminate maintenance time and potential breakages.
      • Collaboration: how to make sure that testers are set up to share assets and work in a way that allows teams to create value together. Teams can leverage a centralized repository of modular assets which are easy to find and tailor to their specific use case.
      • Parallelization: how and when to use the capability of running tests in parallel to reduce the time needed to execute a test suite. Teams can build their own infrastructure or leverage shared cloud infrastructure to accelerate test execution.
      • Reporting: how to assess the results of executed tests and communicate them to the other tools in the CI/CD pipeline. Teams have several options of metrics to track and means to capture and share this information with appropriate stakeholders.

      By attending this presentation, testers will be aware of these challenges they will inevitably face and will be prepared with strategies to overcome them. You do not want to miss this session!