Thinking about changing your career by moving into the test automation field? This post might be just for you…
So, you decided to become a test automation engineer / SDET / test automagician / … Excellent. Test automation is an important part of the software testing field. But if you’re thinking about taking this route just because you fear that your employer is planning to cancel all manual testing effort, maybe you just need to become a better tester. Show them what value you’re adding to your company and to its products and services as a tester. Either that or leave as soon as possible, because your employer clearly doesn’t know what testing is about and you’re better off at a place that values both automation and actual testing and testers.
What I’m trying to say is that you should first and foremost ask yourself ‘why?’. Why do you want to move into test automation? Is it because you’ve seen other people work on automating checks, test data generation or any other activity related to testing and thought ‘hey, that’s interesting, I want to know more!’ or ‘Hey, that’s nice and all, but I’m sure I could do this better / faster / fancier!’? Marvelous. The test automation field eagerly awaits your arrival. However, if all you’re doing is moving towards test automation because ‘it’s a trend’, ‘I’m afraid to lose my job’ or ‘the pay is better’ (actually, I can understand that last one to some extent..) then please do the field a favor and get better at what you’re currently doing. We need motivated individuals willing to learn, teach and share, not opportunists just looking for the next fad or pay raise.
Still interested? Here’s some more things to consider before making the switch:
Test automation is a craft (not in this way, though)
Using test automation well in your project and organization requires knowledge and skills. It’s just like a real job like that: you need to be willing and able to constantly learn and improve. How can you do that? Read and listen. A lot. Read blogs (the links in my blogroll should provide a nice start), listen to podcasts, go to conferences. Also, following the 10,000 hour rule, do a lot. Tinker with tools, repeat instructions presented in tutorials and then try and expand upon what you’ve learned and maybe most importantly: have your work reviewed. Nothing better than having someone more experienced look at your code and give tips on how to improve. I’ve been in the field for 10 years now and I still do this on a daily basis. Why? Because I know it will make me better at my job.
Test automation is software development
I’ve repeated this a lot of times now (yes, repeated, someone probably much smarter than myself said it long before): test automation is software development. Please treat it like that by:
- Testing your tests. If you rely on the outcome of your automated checks when deciding to take something into production, you better make sure that your tests do what they promise, and that they fail when required.
- Applying good design practices and patterns. They’ll make your test code better maintainable, readable and transferable to others.
- Version controlling your stuff. Check in your test code in just the same way as you check in your production code. It makes it easier to share and review code and to revert any changes if necessary.
Don’t believe tool vendors and fanboys
Don’t get me wrong, I’ve got nothing against tool vendors. I even have a very good professional and personal relationship with some of them (you know who you are). I don’t take everything they say for granted, though. Even though the test automation field has long left behind the era of automation by record and playback and the miracles of codeless test automation solutions (it has, hasn’t it?), there are still tools and vendors that claim that everybody and their dog can use their solution and save millions of hours / dollars on testing. While some tools are indeed easy to use (a good UX design and / or a clear API go a long way) they’re forgetting that probably not everybody can use their solution AND do it successfully. Success for the project or organization that is, not for the tool vendors themselves.
Pretty much the same thing goes for tool fanboys. They’ll do anything to convince you to use their favourite tool, because all the alternatives suck / are too expensive / somehow insulted their family members. While they might have a point sometimes (in those cases where their favourite tool IS the right solution in your case) but make sure to investigate alternatives, or build your own tool if that’s a viable option. Try not to fall into the ‘if all you have is a hammer … ‘ trap.
Think beyond simulating user interaction
As Richard Bradshaw explained much more eloquently in his talk at this year’s Test Automation Day, test automation is much more than simulating the interaction between an end user and your application under test. A script that generates test data for testers is test automation. A routine that checks log files for exceptions during exploratory testing is test automation. In short, every tool and piece of code that is used to support or automate activities related to testing in some way, shape of form is a part of your test automation efforts. Broaden your scope.
Still thinking about moving into test automation?
Excellent. This post wasn’t meant to make you refrain from doing so. All I wanted to do (and what I’ll continue to do in the future) is create a view of the test automation field that’s a little more realistic than some of the pictures painted in other places on the Internet. Did I succeed? I don’t know, I’ll let you decide. As always, please do let me know. Leave a comment or send me an email, I’m always happy to talk to fellow test automation engineers and any of you thinking of becoming one.