Group items tagged continuous_integration - Agilesparks

shared by Yuval Yeret on 19 Jan 17 - Cached

shared by Yuval Yeret on 19 Jan 17 - Cached

One of the developers had checked in some code that failed the regression tests. The application, on which the company had spent considerable time, money and effort, was now in an uncertain state. It wasn't behaving as expected. In the past, this type of bug usually wasn't discovered for months. Usually, it wasn't discovered until the System Integration Testing cycle got underway. For this project, that wasn't scheduled for another 6 months.
...

Cancel
In the past, this bug would have lingered in the code for 6 months before anyone even realized it was a problem
...

Cancel
. The light had gone off only 6 minutes after the code had been committed. Notice: not 6 months...but 6 minutes!
...

Cancel
...1 more annotation...
I told them I just saved them $12,535! They looked around to figure out how. The reason I was there was simple. Earlier that year, those same IT managers had performed a series of calculations to estimate how much it cost the department each time a bug made its way out of development, into SIT, into User Acceptance Testing, or all the way into production. For this IT shop, one bug into SIT cost them $12,605 (and you can imagine how much a bug into production would cost.)
...

Cancel