You may dread the termtesting in product (TiP). The mentation of possible loss of data, downtime, and a damaged reputation to governance can be daunting. But thing need not be that way. In fact, today, testing in production is apply by some of the biggest arrangement with much success. But can it become a reality for your squad?

Accident or Intentional?

Testing in production is not a all new concept. In fact, you ’ ve believably see it in action more often than you imagine. Think of an app that you ’ ve released or one that you know of that was poorly screen. You likely drop the next few workweek firefighting, and got it to be functional faster than you imagine possible. In this case, you were forced to screen in production. But, what if you could perfect the art of testing in product and use it to your advantage? What if you could spot and fix issues so lots faster than you do today? What if you could influence development from start to end? What if you could do all this without risking the repute of your team or organization? That ’ s the promise of TiP, and it ’ s worth a second glance.

Real-world Feedback

The key reason to test in production is because of the real-world feedback it yield you. Today, with the plethora of devices and OS combinations you take to essay your app against, it ’ s too expensive and complex to build a testing surround that tight resemble your product environment. Even if you can do this for an early-stage app, wait cashbox you add more lineament, draw more users, or turn your development team. If you want real-world feedback (and every app demand it) your better bet is to overcome TiP.

CI/CD Needs TiP

Testing in production is necessary for teams that embrace continuous delivery. CI/CD is different from the traditional waterfall pipeline not just because of the way it facilitates quislingism across squad, but because it breaks releases down to small, uneventful, continuous streams of updates to the app. In the senior poser, you could essay your app till it meets expectations before the next major rollout, but in a DevOps pipeline, you don ’ t have a major release to programme for. This fundamental alteration in the way releases happen has a ripple effect on testing as well. Just as releases have turn frequent and split, so should testing.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

BDD/TDD Comes First

Testing in production may sound like something that pass only after the app is released, but this is actually misleading. The conception of behavior-driven development (BDD) as Ashley Hunsberger wrote about, or test-driven development (TDD) if you will, is intact to DevOps. This means screen is no longer restricted to just QA, but is baked into Dev purpose right from the offset. In this case, quiz in production is just a legitimate extension of the modern QA process.

Docker as an Enabler

Apps utilize to be monolithic, but today, they ’ re a accumulation of microservices. A microservices architecture allows each service to be deploy and tested separately without affecting other services. This is perform with the help of Docker containers. Docker helps build redundancy so failure are always insulate to a few containers and not the total app. To keep tests small and decentralized, you necessitate to leverage lightweight, portable Docker containers.

Chaos to Confidence

To be proactive about TiP, you should consider implementing something like Netflix ’ s Chaos Monkey. Intentionally killing parts of your system and building its resiliency is the better way to ensure your system can care testing in production. This will take a different mindset, especially for developer who detest discovering bugs, but it ’ s what QA should be about — pushing the app to its breaking point to farther amend it.

Begin with a beta list

A great way to start testing in production is to have a group of beta testers opt in to test unstable releases. This gives you a lot of room to test critical part safely, and the much-needed confidence to get started. You should, nevertheless, strive to go beyond this grouping to testing in production with your entire user base. Now is the right time to test in product. Teams are ready for it, tools are available, and several methodology have been vetted. If you ’ re looking at a future of CI/CD for your team, you can ’ t ignore prove in production.

Chris Riley is a technologist who has pass 12 years helping organizations transition from traditional development practices to a modernistic set of culture, processes and tooling. In addition to being a research psychoanalyst, he is an O ’ Reilly author, regular speaker, and subject matter expert in the areas of DevOps strategy and civilization. Chris believes the big challenges faced in the tech market are not tools, but rather citizenry and provision.