Building The Blocks of Trust In Automation

schedule Jun 30th 03:00 PM - 03:45 PM place Lalit 3 people 82 Interested

Having followed best practices set from previous Selenium Conference talks, my team was able to shift from flaky tests to stable and reliable automated tests. During that time, I learned the importance of building trust in the test suite to unite the team as a whole. Once trust was established in the automated tests, it became crucial to the overall software development lifecycle. It has been an interesting journey to gain the confidence of the organization and have them believe that the automation effort has their backs.

In this talk I will cover the following topics:

  1. Strategies that I used to make the tests reliable
  2. Explaining why it was important to train the manual testers to write feature files and thus help expand the automation suite using their subject matter expertise
  3. Presenting ways to improve visibility in automation to reinforce trust

By implementing these steps in my organization, I have built trust not only within the test suite but into the team as a whole.

 
5 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

1. Organization Structure

2. Automation setup explained: Before vs After

3. Training Manual Testers to Contribute using Feature Files

4. Visibility to all: Website that greets you in the morning with Automated Test report stats

5. Statistical Data Analysis

Learning Outcome

1. How to combine manual and automation testing resources for success

2. How to get more buy-in to make automation visible in the company

3. How to build trust into the automation efforts

Target Audience

Automation Engineers, Managers, Testers

Prerequisite

1. Selenium Webdriver

2. Continuous Integration

schedule Submitted 8 months ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Ashley Hunsberger
    By Ashley Hunsberger  ~  7 months ago
    reply Reply

    The second point "Trainings for the manual testers to contribute to the automation efforts"

    seems a tad off topic from 'building trust' - and could be a talk within a talk.

    Maybe frame it for how to build trust with a team that is not traditionally developers, or learning automation for the first time themselves? If training them to use feature files - maybe go into why this important? How does this help build upon the theme of trust? 

     

    • Sneha Viswalingam
      By Sneha Viswalingam  ~  7 months ago
      reply Reply

      Thanks Ashley, for the valuable comment. Updated to reflect the new changes.


  • Andrew Krug
    Andrew Krug
    Consultant
    Lazy Coder
    schedule 8 months ago
    Sold Out!
    480 Mins
    Workshop
    Beginner

    Want to get into WebDriver, but don’t know where to start? Already using WebDriver and want to get more out of your framework? This practical, hands-on, course is designed to help automation engineers with all levels of experience. All attendees will leave with working WebDriver code on their machines and a long list of techniques on how they can successfully use the WebDriver API in their own companies.

  • Liked David Kirk
    keyboard_arrow_down

    David Kirk - Selenium Grid at Scale through Docker Swarm

    David Kirk
    David Kirk
    Sr. DevOps Engineer
    ReviewTrackers
    schedule 8 months ago
    Sold Out!
    45 Mins
    Tutorial
    Beginner

    Selenium Grid enables developers to significantly parallelize their testing pipeline. This strength can be empowered even further by leveraging the capabilities of Docker Swarm to efficiently utilize available resources and dynamically scale your testing capabilities. With the tools provided by Selenium and Docker, we can build a robust, scalable, and cost efficient browser testing platform without a significant degree of difficulty.

    In this talk, we will cover how to build a Selenium Grid through docker swarm, how to scale that grid, how to test against it, what sort of computing resource requirements should be provided, and my personal experiences implementing this system.