Blog

Why testing cannot be automated? Interview with Michael Bolton. Part II

Is automating research the panacea in the academic world? If you look at expert researchers, they use computerized tools all the time. But nobody talks about automating research.
There is no such thing as automated testing, any more than there is automated research or automated programming. There are some tasks within programming that can be automated, but we don’t call compiling “automated programming”.
11 September 2014
Interviews
Test automation
The article by a1qa
a1qa

In the previous post we started a discussion with a widely known software testing specialist Michael Bolton. Today we continue and cover the issues of automation and rapid software testing.

1. Michael, as one of the Rapid Software Testing course creators, can you, please, explain what rapid testing actually is? Is it a philosophy, an approach, a set of skills?

Rapid Testing is all three of those things. We describe rapid testing is a mindset and a skill set on how to do testing quickly, inexpensively, expertly, and credibly. It requires deep thinking about products, problems, models, processes, tools, and interactions between people. It is an approach that focuses on reducing waste and helping to speed up the project by investigation and exploration throughout development. It also requires the tester to develop skills in many domains: critical thinking skills, scientific thinking skills, using heuristics; emphasizing the use of lightweight, flexible tools; framing testing; applying oracles; identifying coverage and the gaps in it;  and reporting on all of those things.

The premises of rapid software testing are listed here; a framework for describing rapid software testing is here.

2. Automate or not to automate? Is automation testing the panacea in quality assurance world?

Is automating research the panacea in the academic world? If you look at expert researchers, they use computerized tools all the time. But nobody talks about automating research.
There is no such thing as automated testing, any more than there is automated research or automated programming. There are some tasks within programming that can be automated, but we don’t call compiling “automated programming”.

Instead of thinking about “automated testing”, try thinking about tool-assisted testing. If you do that, you’ll be more likely to think about how tools can help you perform all kinds of tasks within testing: generating data; visualizing data; statistical analysis; monitoring or probing the state of the system; recording; presenting data; helping with exploring high-speed, high-volume, long sequence testing; the list goes on and on.

Checking of course can be automated, but you can’t automate the processes that surround the performance of the check: modeling and identifying risk; identifying a way to check for outputs and outcomes that would expose problems; programming and encoding those checks; deciding when to run the checks; and setting up mechanisms to launch them. After the check is been performed humans make decisions about whether the check has revealed important information or might have missed something important. And after that, humans make decisions on what happens next. With the exception of the actual execution of the check, we need humans at every step. None of that stuff can be or will be performed by machinery anytime soon.

So, use tools by all means. Don’t limit your concept of what they can do for you. But beware: a tool amplifies whatever you are. If you’re a thoughtful and critical tester, tools can help sharpen your testing. But if you don’t apply tools thoughtfully and skillfully and critically — if you’re a bad tester — the tools will help you to do bad testing faster and worse than ever.

Most importantly, remember that the tester and his or her skills — not the tools, not the process model, not the documentation—are at the center of testing.

Michael thanks for sharing your experience and ideas. We`ll be glad to see you and talk to you again.

You can follow Michael on Twitter

More Posts

debated technologies
30 May 2023,
by a1qa
3 min read
a1qa tech voice: Managing director at a1qa, North America, discusses pros and cons of much-debated technologies
Nadya Knysh, Managing director at a1qa, North America, puts a spotlight on 6 current technologies, discussing their positives and negatives.
General
Interviews
Test automation
why-do-bugs-get-missed
17 April 2023,
by a1qa
4 min read
Why do bugs get missed? Learn the problems and tips to avoid them
Still, finding overlooked bugs after the app goes live? Let’s find out why this happens and how to fix it.
Quality assurance
Test automation
Mobile app testing
15 February 2023,
by a1qa
4 min read
Mobile app testing guide: win the race with five-star software
Which aspects of mobile apps to test first to produce a really high-quality product? Find the answer to this and other questions related to mobile app testing in the article.
Cybersecurity testing
Functional testing
Mobile app testing
Performance testing
Test automation
Usability testing
a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation
qa-trends-in-telecom
30 September 2022,
by a1qa
5 min read
4 telecom trends for 2023 and how to painlessly implement them with QA
It’s time to explore the telecom trends for the upcoming year. Let’s look at them together and also see the value that QA brings for their smooth deployment.
Cybersecurity testing
Migration testing
QA trends
Quality assurance
Test automation
ai-ml-test-automation-mini
15 September 2022,
by a1qa
4 min read
4 key QA activities to solve test automation challenges via AI and ML
How to address the difficulties caused by implementing test automation? Learn how to do it via applying AI and ML.
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.