Posted by IN / 2 responses

Webinar: Making the Case for Full-time Test Automation Engineers

28 June 2017

Paul Merrill“Can’t we convert our testers to test automation engineers?”

“Why can’t developers create test automation?”

“Can’t one test automation engineer work across several project teams?”

If you’ve said, thought, or heard questions like these, watch this previously recorded webinar now!

Many times decision makers in software development companies have trouble making the case for full time test automation engineers and SDETs. In this webinar we talk through the responsibilities of test automation engineers, the value they provide, and the return they create on their labor.

How are they different from testers? How are they different from software engineers? When can you use either of these to create test automation instead of hiring a full time test automation engineer?

If you’re encountering friction in creating a position for a test automation engineer, this is the best thing you could do with this hour.

This webinar originally aired on July of 2017.

Find more webinars here and sign up and to never miss another webinar with our email list.

2 responses to Webinar: Making the Case for Full-time Test Automation Engineers

  • Jim Hazen says on June 29, 2017 at 1:42 pm

    My question back is “Why do you hire software developers and have them work full time on programming the application?” The same is true of Automation Developers/Engineers (people who really do “program” the automation), it is a full time job. The problem to solve is getting other groups to understand all of the tasks that an automation developer has to do to, and the time it takes to get it done properly the first time through. Plus, they need to understand that once the initial work is done there will be maintenance and enhancement work that will need to be done. Automation in today’s reality isn’t Record/Playback (and it never was) and letting the tool go along its merry little way. It is about solving multiple problems at once and then creating a robust, reliable and maintainable solution that is reusable for the duration (or as much as possible) of the project. It is about working with other groups to come up with a solution that is usable and beneficial to those other groups. Automation Developers/Engineers are a hybrid of programmer and tester; they have to have a solid understanding of both in order to bridge the gap and create software to drive the execution of testing of other software. They build “Testware”. Also, Automation Developers/Engineers have to see the bigger picture and understand how their testware fits into that equation. This means understanding the overall environment and target platform/stack they will build/run their testware in. They need to understand how to run the testware at scale and in parallel, and how to get it to run as part of a Continous Integration/Deployment environment in todays Agile landscape.
    So, there is a lot to know and do for Automation Developers/Engineers in todays reality. The only thing missing is a giant “S” on their chests. Either that or they have to possess the Elder wand. Because after all “It’s Automation, Not Automagic!”

    Reply
    • Paul Merrill says on July 3, 2017 at 11:13 am

      Thanks for the thoughts Jim! The question now is, do I agree with you? I guess folks will have to tune in on the 13th to find out…

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *