From the course: Understanding Manual Testing

The argument: Automated vs. manual testing

From the course: Understanding Manual Testing

The argument: Automated vs. manual testing

- [Instructor] Before we dive any deeper into the details of manual testing, we need to address a common argument and misconception I've encountered in my career. And you are bound to hear about. I have met many test managers who've argued for automating as much of their testing as possible. They see the speed and efficacy of an automated program as superior to a manual approach. In fact, they often argue that manual testing should be abandoned all together. There is no question that automation is a valuable and important tool in performing quality testing. In a large application, manually reviewing hundreds of thousands of lines of code, and clicking the endless elements that a user face truly test the limits of human capabilities. It's clear that these tools are needed. It's why you'll see articles and videos pitting manual versus automation and learning why one is superior to the other. The confusion in this argument is there is a belief that automated solutions are designed to replace a manual approach. In the beginning, this was probably the case. Before automation existed, everything was done manually. Naturally, as automation displaced numerous manual test cases, many people probably predicted it would replace every case eventually. However, just as automation has evolved, so has manual testing. The contemporary version of manual testing explores the process through the expertise and experience of the quality engineer. This is not a versus situation. Automated testing exists as one part of a variable and complete quality solution. Manual testing serves as another. The two processes are not in competition with one another, but actually compliment one another and provide very different test results. Automation delivers excellent scalable testing at a speed modern team's demand. Manual testing provides the close scrutiny and examination that your software requires. Measuring one approach versus the other is an argument that takes away from the focus of any quality program. Between the two approaches, you give the product a complete evaluation that ensures the best possible product is delivered. And in the end, that's all that matters.

Contents