software testing

Agile testing

Why the Future of Testing Requires Disruption

Businesses have always been tasked with meeting, or, ideally, anticipating, the evolution of consumer demands and expectations. This is nothing new. However, the acceleration of this evolution has increased to the point where businesses today face a harsh reality. You either disrupt…or you become disrupted.

Tricentis Chief Product Officer, Dr. Gerd Weishaar, makes this point in a recent webinar, “Why is Everyone Talking About the Future of Testing?” Weishaar also notes that two major trends that have been taking shape over the last 20-30 years have led to what’s become a monumental task for organizations around the world.

  1. The technical complexity of software systems has increased. For example, what used to be a simple web app is now often a highly complex system working with hundreds of web services, mobile devices, and more.
  2. While software complexity has grown, delivery and release cycles have decreased just as dramatically.

Keeping up with today’s rates of change and the delivery of innovative software that supports multiple lines of business is no small feat. Ensuring that each release of that software is consistently at a high quality and delighting customers is another challenge altogether. The need to tackle both of these challenges is the primary driver behind the disruption we’re seeing in software testing today.

Weishaar later notes that while one requirement for transforming software testing involves increasing automation rates that have been stagnant for far too long, organizations should also introduce more exploratory testing for even greater risk coverage.

software testing

After touching on some key components of next-generation continuous testing—and a quick case study on the numerous benefits from adopting this approach—Weishaar fielded a handful of questions from the audience, including:

If DevOps requires test automation, which requires test data management, service virtualization, etc., how do we find the time to automate tests and get all of these supporting practices up and running?

What are the main differences between scripted and scriptless model-based test automation solutions?

How is exploratory testing part of continuous test automation when it’s not automated and is often a one-off activity?

To learn more about why continuous testing is the future of software testing, we invite you to view our latest webinar, now available on-demand.