Is software testing dying? Of course not

(Rosie) #1

Ok. It’s old news. But worthy of a long term thread.

We know software testing is not dying a death, don’t we? But can we give some reasons why or how it is not?

Here are some to get you going, can you add some to this list…?

  • Software testing is evolving, not dying
  • We are increasingly becoming more technical
  • Our roles are merging and overlapping with other roles
  • We are helping and teaching others to test their own work better

Over to you…

(Chris) #2

Software Testing is evaluating a piece of software in order to find problems so that someone can do something about it.

When a programmer compiles a program and looks for build errors or does a code review they are testing.

So we can do it well or we can do it badly, but forever it shall be done.

(Lee) #3

By working more closely with developers, having conversations instead of waiting for work to reach us, we are helping to reduce the chance of bugs being made from misunderstandings or scenarios not thought about. It then means less bugs are found when code makes it’s way into test, but because we are helping to prevent them from being made in the first place.
so, whilst it may seem less testing is happening, it is simply being done in a way to make it less obvious but more valuable.

(Alastair) #4

I don’t think I’m adding to the list as such, but my opinion is similar to Lee’s reply.

With the focus on quick delivery, testing is changing rather than dying (and is actually more important than ever).
We need to test everywhere rather than at the end.
We need to shift left AND right to ensure that we’re still delivering quality software which is performing as expected for our users.

Dan Ashby’s diagram springs to mind - from

(Vishal Dutt) #5

This is one of the talking topic these days in IT market that ‘Software testing’ is dying. Some people think this way and some are not. Hence at a moment when we are finding top leading Software testing companies are having their primary focus on their QA team. If we talk about manual testing, we can say that manual testing is losing their importance little bit in the top software testing companies in some specific situations due to the wider scope of automation testing tools these days. But, still there is a terrific demand of manual tester in industry.

As we all know if we are starting a career in software testing, then having knowledge of the automation testing tool is big plus as we will definitely get better position in coming years. If we talk about any software application or big product then it won’t be get successful unless tester can test the same. Tester helps the product or application to be refined enough so that it can be of acceptable standard for the end user.

So, the truth behind this question Is software testing dying? is that its not dying. Basically, its transforming and changing as right now every companies wants that all layers of the their application need to be tested simultaneously with each possible scenario and in context, with an end goal of creating a quality product. One of the main reason is that manual testing will never die because the automation testing could not cover all kind of test cases for all the products and application. If any company is adding the new feature in their product then they need manual tester for the better quality of it. Manual Testing is normally the first thing when any functional testing services do to gain information from the system/application developed because all kind of complex testing start with Manual Testing. So the conclusion for this is that software testing is not dying , it just changing and transforming into certain areas.

Hope this information will be helpful for you.

(James Thomas) #6

Personally I measure the health of the testing community by numberOfTestBashesPerYear - as this number keeps going up, well…

(Simon Godfrey) #7

The craft has changed, that much is true. We now see a shared responsibility when it comes to writing (automated) tests and as most testing is automated that means testers have to work harder than they might previously to show their value.

I hear “we don’t need testers as we write tests” which really means unit tests, which isn’t the whole testing picture - this is worrying.

I also know that Test Managers are very hard to come by for those companies and recruiters who’re looking for them (us). Likewise, I think finding strong and experienced testers is hard to come by as many testers have gone on to other roles by the time they get to Senior/Staff level within a business.

(James Thomas) #8

as most testing is automated

Not in my neck of the woods it isn’t - we have good BDD/Unit coverage on newer projects, but exploratory and requirements-driven testing is a key component in most of our projects.

(Robert) #9

“I hear “we don’t need testers as we write tests” which really means unit tests, which isn’t the whole testing picture…”

Too right. I recently had cause to complain to a director of my usual supermarket because they had a customer self-service terminal in-store that worked 100% fine in terms of the code but whose UI was appalling and had so obviously never been reviewed by a human being before release. I pointed out that my usual invoice for the level of report I provided them with was £250, but I’d be happy with £15 off my next shop. All I got was a weak excuse and the not-so-exciting news that the system I was complaining about was due to be torn out and replaced with a mobile app inside the next three months.

If I’d been basing a big purchasing decision on the high-level corporate response and what it told me about the company’s testing policy, I would have been taking my business elsewhere. Fortunately for them, there are other factors influencing my choice of supermarket…