Why Software Testing Is a Waste of Time

Testing software takes up a lot of time in the software development process, often the same time if not more than the time required for the development itself. Just like development, testing also requires continued maintenance efforts. This (rightfully so) makes a lot of people in different roles, be it managers, developers or even testers question whether or not that time effort is really justified. With more and more companies deploying every 10 minutes or even less start to wonder: why invest time in testing when you can rollback issues in a matter of seconds, in some cases even automatically?

Learn more about common pitfalls, time wasters, and what you can do to make your testing strategy more efficient in this talk!

Value for the audience:
As a full stack software engineer working as a consultant at a lot of different companies, in addition to being a Swiss Testing Board member I constantly see and hear about companies making the same mistakes in testing over and over again, most of which are easily preventable if you know about them. I would like to share my most common findings with everyone, to prevent others from making those mistakes and to help them test efficiently. I've seen companies following the test strategies I proposed being very successful and efficient which is why I also want other companies to be able to do the same.

Problems addressed:
How to make your testing strategy more efficient

How to develop for testing

When investing time into testing is worth it, and when it isn't

Talk language: English
Level: Advanced
Target group: developers, engineers, architects and QA that have written and executed an automated test before, project managers with interest in the software development process

Company:
Karakun AG

François Martin