It’s NOT the Stork: Where Tests Come From – Quid Technology

It’s NOT the Stork: Where Tests Come From

In this first post on how we test software at Quid, my aim is to tease out different layers of testing built into our development process, and to call out when, where and how tests should be added, and most importantly, who should come up with them.

The biggest problem with testing is not doing any. To quote the Google SRE (Site Reliability Engineering) team mantra, “Hope is not a strategy”. If you didn’t test your feature / service / API / function, I’ll bet you good money that it’s buggy in ways that matter. If you tested it once when you built it, but don’t have it covered by a regression suite executing in your CI (Continuous Integration) framework, I’ll bet that it’s broken by now. You could proceed to run the code in production anyway, and pay the price in escalations from the field that take up valuable engineering time, support calls, and loss of users due to dissatisfaction with quality.

The following two tabs change content below.

Eric Axelrod

President & Chief Architect at DIGR
I have helped companies bring new data driven products to market, drive efficiency out of their supply chain, execute strategic plans, and drive top line and bottom line growth by enabling every business function with actionable analytics. I can transform a business which is lacking critical insight into an agile, strategic, data driven organization.

Leave a Reply