2018/09/15 A message to recruiters for automation testers

I put this on LinkedIn, but after doing so I felt like this deserves to be a blog post.

If you disagree with my message, please say why in the comments below.

If you agree, also please say, so I know I’m not alone.

To any recruiters who see my profile, I want you to know I am extremely passionate about different aspects of testing.

But one aspect I am not interested in is learning automation. Yes it has it’s uses, but it doesnt appeal to me.

There is so much that can be done as a tester without being able to make an automated framework. If someone can’t do automation, look at what they can do instead.

Automation doesn’t review requirements.
Automation can’t pair with another tester or developer to work out what should be tested and how.
Automation doesn’t let you explore something no-one has used before. Those explorers blaze a trail to work out if it can be automated and what they would expect to get back.
Automation has no gut instinct.

If a company only wants people for automation, I will happily challenge them on why they shouldn’t do that.

But, if a company wants someone who will fight their corner of testing, want to encourage pairing and mob testing/programming, that testing happens at the beginning and all the way through to going live, then please get in touch.


4 thoughts on “2018/09/15 A message to recruiters for automation testers

  1. I understand your POV and agree to most of your post. I don’t think though that a tester should know how to write automation framework. It doesn’t make sense because writing something like that is a profession by itself. I do think that writing scripts could be handy. Yes, you can be a great tester w/o it, but a little better with this ability.
    Automation is, as James Bach and Michael Bolton said, is checking not testing and has many flaws, some you mentioned. Small point though – the automation writes should review requirements.

    Liked by 1 person

    1. The problem is I’ve seen job adverts looking for manual testers to be trained into being automation testers, as if that’s the only future for the role. I’ve seen automation testers who exist only to create and maintain scripts, with the manual testers saying what needs to be made, or handing over their manual scripts to be followed.
      I’ve a big fan of Bach’s and Bolton’s work, and their opinion of testing vs checking.


  2. Nothing wrong with your views at all. I did a talk on how I became ‘more technical’ and I mentioned that there’s no point in learning something you’re not passionate about.

    I learned coding and automation because I find it useful in the SDLC and I thought I could add more value by learning how to do it. Is it my most valuable skill? Definitely not.

    Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s