Some thoughts on the future of test automation

As an independent consultant, keeping up with current trends in the field (in this case test automation, but this goes for all consultants regardless of the field they’re working in) is key to remaining relevant, hireable and able to land interesting projects and other gigs (writing, speaking, etc.). For me, the annual summer holiday is a great time to take a step back and reflect on what I’ve been working on the past year, and the trends I’ve seen emerge. In this post, I’d like to share some of the thoughts that have come up.

Test automation is getting closer to software development
The first observation I’ve made from the last couple of projects I’ve been working on is that test automation is moving closer to software development in two ways:

  • Test automation is regarded more and more as software development, including the use of development patterns and practices, and
  • test automation is adopted and executed more and more by developers

The first way is definitely a good thing. I’ve been saying this for some time now – and brighter persons have done so long before me – but test automation is finally starting to be seen as a proper software development task.

I believe that the second way is beneficial too (if only for the fact that developers are best at developing software, of which test automation is a form as we’ve just stated), although there are some side notes that need to be made. First of all, completely leaving test automation to developers probably isn’t a good thing – at least not yet. There’s the effects caused by developers marking their own paper, as well as the risk of losing the testers mindset. Angie Jones wrote a great blog post about this recently, which I think you should all read. I believe this means that the demand for proper test automation specialists (not being developers) will remain or even increase for the foreseeable future. Developers can work out the technical details for the test automation solution, something which they tend to like doing best in my experience, while the test automation specialists provides input, oversees that test automation remains efficient and meets business needs and helps with designing, development and implementation where necessary.

Can we please stop testing through the user interface?
I’ve elaborated on this in a recent blog post, but the amount of questions I see related to user interface-driven test automation (especially related to Selenium) keeps surprising me. Yes, I know a lot of current applications are web applications, but I refuse to believe that there aren’t more efficient ways to apply test automation to at least part of these applications other than automating all kinds of scenarios through the user interface. Again: please only use user interface-driven test automation when:

  • you’re actually testing the user interface itself, or
  • you’re performing end-to-end application tests (and these tests should make up only a small part of your overall test set)

In all other situations, please try and find more effective means of driving automated tests. This will result in faster, more stable and probably better maintainable test suites, which in turn will lead to a more positive attitude towards your efforts and test automation in general. The community thanks you.

The death of codeless test automation ‘solutions’ (finally!)
Also, my crystal ball told me that – finally – everybody starts to see that codeless test automation solutions just aren’t worth it. The points I made above only reinforce this statement. I’m seeing less and less advertising for these types of tools, and I think that’s a good thing. In my experience, these tools often do not live up to the hype past the first sales demo or two. Simply put: test automation equals software development equals writing code.

Increase of test automation scope
Finally, I think that the scope of test automation efforts is expanding beyond replicating the interaction between a user or a system and the application under test in an automated manner. Eloquently argumented by Richard Bradshaw in his presentation at the 2016 Test Automation Day, test automation is so much more than that. Automatically parsing log files generated through an exploratory testing session? That’s test automation. A script to set up or clear test data before or after a test session? That’s test automation. A tool that helps recording and sharing observations made when testing? You get the point. There’s so much to gain through smart applicatin of test tools other than simply automating predefined test scripts..

Please note that the above is not meant as a complete representation of my vision on the future of test automation, but rather as a list of a couple of thoughts I’ve had over a decent glass of wine (or two) during the holiday. Got any predictions about the recent or distant future of the test automation field yourself? Thought of anything brilliant during your own holiday? Please share in the comments!

8 thoughts on “Some thoughts on the future of test automation

  1. Bas,
    Another great post. I have always seen this work as a form of software development. We create software to drive the execution of tests (checks, whatever) against another piece of software. As such we need to understand how the other program is built and functioning so that we can write automation code to interact properly with it. That does take some understanding/background in programming.

    With Development finally (and I mean “FINALLY”) getting onboard with using tools for testing work it has helped a lot. Now they understand both the pain we endure doing the work and the benefits they can enjoy using tools like this. Yes, we are becoming more tightly knit and breaking down the wall between Dev & Test.

    And agreed on Codeless/Scriptless tools, they are a Marketing/Sales wet dream (sorry for being so blunt). Just a new version of the Record/Playback myth/misconception (although there are some good uses for R/P technology).

    Finally, “automation” does come in different shapes and forms. It can be used for other purposes like utility tools/scripts that do other work that is part of the testing process. Using a tool in this manner means you’ve gone beyond the normal borders, which is great.

  2. Pingback: Java Web Weekly, Issue 140 | Baeldung

  3. Pingback: Testing Bits – 8/28/16 – 9/3/16 | Testing Curator Blog

  4. Pingback: Five Blogs – 5 September 2016 – 5blogs

  5. Pingback: Reading Recommendations # 73 | Adventures in QA

Leave a Reply

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