Updated: Feb 11
Our testing tool chain is quite impressive. Some are very specific, and others support a broad range of technologies and testing activities. However, when it comes to technical testing, more specifically, automated and performance testing, there are still gaps. In this post, I will outline this cleft.
Typical technical testing activities
Independent whether you are following an iterative or agile development approach, you will implement automated regression tests, performance tests, and security tests. You will start early in your development lifecycle and try to integrate also unit tests in your build process. Chances are very high that your test engineers will have four or more different testing tools in place.
Our current technical-testing platforms are still limited concerning support for different testing activities. This gap leads to high development and maintenance effort. We have many script redundancies, and in some cases, test implementation exceeds development effort.
Based on my experience, many successful organizations have automation, performance and security testing specialists in place. It would be a great productivity driver if those teams can use the same testing platform and testing scripts across their testing activities. This test asset sharing would lead to a rise in test coverage and test effort savings.
I hope that this post is a wake-up call for our testing solution providers. Start your engines and build a new technical testing platform that closes this gap.