3 years ago

Co-written with Seetharam Param, CEO of ReleaseIQ.io I was reminiscing with a friend and former colleague of mine recently about how we both have e xperienced product and service releases that were under tremendous pressure to deliver a new feature or capability and were already behind schedule.

We weren’t the only ones with both the scars of painful releases and the experience of well-executed release processes.

One very simple and insidious reason is that when we run automated tests in pre-production environments, we invariably have the dilemma of what to do when the tests fail.

Succinctly, developers need an aggregated view of all the sources of issues to help them to find the root cause of the problem quickly.