Think back just five years ago. In 2014:
- The seminal DevOps book, Gene Kim’s “The Phoenix Project,” was one year old;
- Gartner predicted that 25 percent of Global 2000 enterprises would adopt DevOps to some extent by 2016;
- “Continuous Testing” just started appearing in industry publications and conferences;
- Many of today’s popular test frameworks were brand new — or not yet released;
- The term “microservices” was just entering our lexicon;
- Only 30 percent of enterprise software testing was performed fully “in house.”
Times have changed — a lot. If the way you test hasn’t already transformed dramatically, it will soon. And the pace and scope of disruption will continue to escalate throughout the foreseeable future.
On the one hand, testing is all too often the roadblock that stands between highly accelerated Dev processes and highly automated ops-driven delivery processes. But on the other hand, testing is essential for ensuring that the release doesn’t place the business at risk — undermining the very “customer experience” that digital transformation is dedicating to enhancing.
How can you achieve the optimal balance between speed and risk to deliver engaging customer experiences faster than competitors? Enter Continuous Testing…